SALESFORCE LIGHTNING MIGRATION GUIDE

6 Simple Steps That Make It Easy

Step 1.?Preview with Migration Assistant for a good Lightning “test drive”

Salesforce provides an out-of-the-box Migration Assistant that adds all objects and data to Lightning. It gives you a step-by-step guide on how to activate Lightning Experience for your organization and your users; is a completely harmless operation; and all you need is five minutes to activate all process automation, such as workflow, sharing rules, record types, page layouts, and data. You can find Migration Assistant in the Setup.

Salesforce Migration Assistant gives you a chance to create a Preview of Lightning Experience. That means Lightning Experience is not yet available for you or your organization. Think of it like a good test drive where you can check “out of the box” Salesforce functionality and prepare for the next step before complete activation. Our practice shows that Preview is a valuable means to explore your production org in Lightning Experience, so you can see exactly how your real data and your current customizations work in the new interface. It is always good to have a try-before-you-buy option.

Step 2. Gap Analysis to examine the technical aspects

Run a Gap Analysis and examine the technical aspects. You tried it out and it looks great so far, but unfortunately, there are some gaps between Salesforce Classic and Lightning Experience. This is your chance to find out what was missed in the automatic conversion process, such as missing default Visualforce pages, custom buttons with javascript context, and a list button. Even when they are there, they look somewhat ancient. In future releases, they will cover gaps, but for now, you can use this resource to check out what is not yet done. Depending on the size of your project or entire organization, Gap Analysis can take from one week to two months. No worries though. There always exists a workaround, and you just need to find it.

Step 3.?Adoption Team – run end-user testing

Create an Adoption Team and run end-user testing. Pick a good cross-section of users in your company, e.g., users from various departments, partners, sales reps, developers, etc., to try out the system features. The users should have some experience with Lightning so that they can help you identify missing pieces and pitfalls in the converted custom or standard apps. This is the point where usability and high-tech analysis come together.

Step 4.?Close all gaps, implement all features

It’s time to close all gaps between the two editions of Salesforce according to your needs, and then implement all the new great features that Lightning offers: App Builder, Kanban List View, Sales and Service Console, new Dashboards, and even more. This step also requires a proficient development team and collaboration with the business to figure out which pages can be converted to Lightning components, and which can be pushed to the next release. Gradually you will adopt all Lightning features that help your company be more productive, close deals and cases faster, and implement sophisticated development solutions in the new platform.

Step 5.??Pilot program to spread awareness

Run a Pilot program, which not only helps to further identify deficiencies but serves as “public relations” for the rest of the company. Your workers need to like Lightning before they will easily adopt it. Many of our clients say that this hint alone made the final adoption process easier and faster.

Step 6.??Launch to User Groups for better adoption practice

The first launch to specific User Groups (with training, feedback, and support, as opposed to launching for everyone at once) may take some time. But as a reward, you will get much more than an exclusive and robust UI with hundreds of new features not available in Classic for Sales, Service, and Marketing or CPQ team. This approach will enable your technical team to develop comprehensive, safe, and reusable components or applications for your business, as well as a deeper knowledge of how each group will use the system.