The most comprehensive Lighting migration walkthrough
Let us navigate through pitfalls of Lightning migration!
How to switch from Salesforce Classic to Lightning Experience as effectively as possible
The long-anticipated conversion to a new user interface is finally here. The inevitability of migration till 2020 has been recently announced by Salesforce, and now many companies have a lot to worry about. The main pain point is the necessity to spend extra time, money and other resources to switch UIs. So, each and every Salesforce user is worried whether the transition period can be smoothened and quickened as much as possible. To make our readers’ life easier, we’ll determine pros and cons of both UI versions, discover main user pains, outline migration steps, recommend tools for better switching, and so on.
Classic vs Lightning: advantages and disadvantages of different UIs
Everything forward will be Lightning, as Salesforce executives claim. It offers tons of benefits for businesses and will surely be embraced by every employee in every company, sooner or later. Let’s consider the most prominent advantages and disadvantages of Lightning Experience User Interface.
Lightning UI Pros:
It is faster, quicker to customize (with easy drag and drop configuration) and easier to maintain though it requires extra time to get adjusted to.
It is more flexible and dynamic as compared to Classic UI, with better visualization due to Smarter Views.
Sales Path efficiently helps define key stages for a Lead to go through, and fields per stage to be completed by a sales rep.
The new practical Kanban view offers insights into opportunities that help manage them in an easy way.
Modern design and enhanced functionality represent source of pride of renewed Reports, Charts and Dashboards.
Lightning UI Cons:
The necessity to spend more time on migration. It’s an arduous process and can take up to several months or even a year getting up to speed, all in all.
Slowdown in users’ adoption as a result of their long coexistence with Classic.
Some applications from the AppExchange might not be supported in the new edition. It’s recommended you check everything minutely before the migration.
Actually, both Classic and Lightning versions lack some great features. For example, sales and support reps heavily use such a Classic UI feature as the ability to assign tasks in Lightning to multiple users, which it’s not available in Lightning now. On the flip side, users will miss some Lightning features – Sales Path, Assistant, Kanban, Einstein Lead Scoring – in Classic UI, and so on.
Lightning Migration Pitfalls:
While changing UIs, users can naturally experience severe technical roadblocks. The main task of the Salesforce admin team in the company is to identify gaps and help users eliminate them. As for pain points, we can briefly mention some of them:
The most burning issue is the increased amount of time consumed by the potential training for a new UI. As an option for enterprises, we recommend resorting to self-training too: to give employees enough time and freedom to explore new interface themselves.
There are problems with record sharing, as Lightning has no such option. The way out (not very efficient, unfortunately) can be to switch to Classic, finish the task and return to Lightning (or employ a special component on Salesforce AppExchange).
The new interface is rather loaded with data and functions, causing low speed of operation and setting off a nervous response among sales reps. There are other connected pains: limits for number of fields and controls for a page layout (you can’t add endlessly, like in the previous UI). Besides, the proper functioning of Lightning Experience at virtual machines requires better hardware.
Ctrl + F doesn’t work as an on-page search. The possibility to find smth in a new system is vital, unfortunately, now the option is unavailable.
Visualforce pages must be reviewed, sorted out by relevance and migrated to a new Salesforce Lightning Component. You must redesign all pages with Lightning design system.
Adding event attendees feature is missing in Lightning.
Auto populate using URL hack is not supported in Lightning.
While transferring the completed tasks, their status changes and requires manual processing to be corrected.
As for the solutions to the above pains, there are no off-the-shelf answers for all of them right now. Let's hope Salesforce developers will introduce required improvements as soon as possible.
How to migrate to Salesforce Lightning Experience hassle-free
The migration is inevitable now. The main challenge is to assure smooth transition period for your company. Below we offer a set of tips from our inhouse specialists on how to migrate to Salesforce Lightning with minimum losses.
Discuss and Prioritize Functionality
and Potential Integrations
Run a Lightning
Work in a
Roll Out Lightning
to Power Users
It’s vital to define enablement plan in the first place. It helps you significantly reduce hiccups while swapping user interfaces midstream. Plus, you have to think about adequate training for your team in advance. You can employ versatile sessions, webinars, strategic meetings, face-to-face trainings and coaching sessions.
Educate your company on Lightning benefits
Conduct a gap analysis of non-supported features
Decide which users move to Lightning first (test group)
Develop an internal marketing strategy to educate future users
Create a training plan
From now on, Salesforce intends to build new features only for Lightning Experience. There are already 200 things that you can do on Lightning. Unlocking new opportunities of Lightning Experience, as compared with Classic UI, can become the final straw that breaks the camel’s back. The reason is the apprehension of some companies’ stakeholders to migrate because of the extended learning curve, the need to prove ROI etc.