Migrating to Salesforce Lightning Experience from Classic

Advantages of migrating to salesforce lightning experience from Classic:

Swift application development, better portal development through Lightning Bolt, mobile first sync capacity, and Lightning for Visualforce offers advantages at multiple levels –

  1. 70% faster time to market thanks to quicker application development
  2. 37% increase in customer revenue growth
  3. 44% boost in sales productivity

 

When moving to Salesforce Lightning Experience

 

What is not impacted:

  1. Data (Still there!)
  2. Business logic (Workflow Rules, Process Builders, Validation Rules, etc. – still there!)
  3. Security (Role Hierarchy, OWDs, etc. – still there!)

 

What is impacted:

  1. User Interface (Lightning Experience has up to 25 tabs, 3-Column layouts, Paths, Components, etc. – time to reimagine working in Salesforce!)
  2. Business Processes (Go back to your requirements – with Lightning would you solve a problem differently?)
  3. 3rd Party AppExchange Apps (Take inventory and see if your existing Apps are “Lightning Ready”)
  4. Custom Code (“Technical Debt” will have to be addressed if it doesn’t perform well in Lightning)
  5. User Training (Yes, all users will have to be retrained)
  6. Analytics (You’re no longer limited to three-column dashboards and there is a new Lightning Report Builder)

 

How to Migrate to Lightning in Salesforce

Step One – Outline Goals for Transition: By outlining goals and conducting a high-level investigation, you’ll prepare yourself with a better understanding of how your system would evolve with an upgrade. You’ll understand the potential challenges, workflows, and processes to evaluate when the time comes.

Step Two – Map Out Workflows: Many companies struggle during and after a Lightning migration because their internal processes make a parallel shift as well. If they don’t prepare and train all affected teams, it can create roadblocks and even set the company back instead of moving it forward. Mapping out a strategic process beforehand prepares your team for a flawless launch. It also ensures fast and efficient development during the development stage.

Step Three – Discuss and Prioritize Functionality and Potential Integrations: Start with the key Lightning functionality you’re pursuing first and then prioritize features from there. Keep in mind how everything will tie together and if certain developers and admins will need to tackle pieces together or separately. Schedule their time to the week, if not the day, to avoid overlaps in needs and consequent roadblocks. Outline, step by step, how and when features will be built and customized. If you’re planning on integrating Lightning with outside systems, pause for discovery on how this will affect the platform and your team’s use cases. Ensure a streamlined and secure integration that protects your company and its data while enhancing your capabilities.

Step Four-Run a Lightning Readiness Check: We recommend you run a Lightning Readiness check. It can pick up on potential unforeseen bugs or org incompatibilities you may have missed and helps your team build an even more robust Lightning migration plan.

Step Five – Work in a Sandbox: Now that you have your well-defined plan, it’s time to get started! I recommend using a sandbox to isolate and test your changes without affecting the work of other developers. This allows you to understand how the updated code would affect all users.

The sandbox testing environment also allows key stakeholders and Super Users to test out new functionality and provide critical feedback before an official launch. Using a sandbox greatly increases your opportunity for eliminate bugs before going live.

Step Six – Test Your Goals: Before moving on, double back with all of your key stakeholders to ensure the new Lightning features you’ve prepared and built will accomplish the goals you outlined in step one. If they don’t, take a step back and evaluate where you veered off a path. It may feel like you’ve invested too much time to take a step back at this point, but trust me, if you don’t refocus on your goals now, you may never be able to correct course.

Step Seven – Roll Out Lightning to Power Users:  Once you feel ready to launch, start with all changes to Power Users only. Each user account can roll out to the new functionality individually. This isolates major unforeseen issues in a Lightning migration. It also ensures that the new functionality lines up with what each user group actually needs.

Collect feedback from these Power Users. Implement any required changes and release the updated functionality to production.

Step Eight – Write Detailed Documentation: Next, before launch your Lightning migration, you need to ensure you have a reference document to ensure the new functionality release goes smoothly. Don’t let productivity come to a screeching halt just because users can’t figure out how to do something or how to find a critical piece of information.

Using the outlined workflows and processes, use cases, and goals detailed in steps one and two, build a comprehensive documentation guide. This informs other developers, admins, and even users of how to edit, update, and use the Lightning functionality as intended, in a way that relates to your organization’s goals.

Step Nine – Introduce Lightning and Training: Use the documentation described above to train all users on the new Lightning functionality before rolling out the changes as live to the entire organization. Your Power Users can train other users on how to leverage the new functionality properly and how to find the information they need.

Once admins learn the new system, they can make tweaks on their own. This promotes independent management of the org and opens up opportunities for adoption of new Lightning features in the future.

Step Ten – Launch! Once your team feels confident everyone understands how to use the new Lightning system up to its highest potential and once they have access to knowledgeable resources should they have questions, it’s time to go live!

If you have engaged in custom development to make this transition, we recommend keeping a core team of developers available for the week or two following launch. After this initiation period, though, it’s time for your trained administrators to take over management of the Salesforce Lightning system.

Leave a comment