Let’s Talk About
Your Salesforce Project

How healthy is your Salesforce?

See 10 signs your Salesforce needs a health check

The Ultimate Guide To Successful Salesforce Lightning Migration

Download Now

Featured

7 challenges of Salesforce Lightning migration you must know and address

admin | May 15, 2019 | 4 min read

The Lightning framework is one of the most significant upgrades from Salesforce. It has paved the way for organizations to improve employee and customer experiences, increase productivity, and reduce the development time to allow businesses to respond to business demands quickly.

When it comes to migrating to Salesforce Lightning from Classic, it is not a question of “if,” but it is about “when” and “how soon”.

No more releases and feature development is happening in Classic. Starting January 2020, Salesforce has turned on Lightning Experience for all orgs on a rolling basis aiming to have everyone on Lightning.

As per the study – Total Economic Impact of Salesforce Lightning by Forrester, Lightning Migration delivers 341% ROI along with the improved user-experience, end-user productivity, and efficiency savings.

While switching to Salesforce Lightning is a no brainer, for a successful and seamless migration that makes users adopt the new interface quickly and gets you to value faster, there are several important aspects you need to be aware of and address before you take on the migration project.

For a successful and seamless migration that makes users adopt the new interface quickly and gets you to value faster, there are several important aspects you need to be aware of.

Common challenges faced during Lightning migration

Here are the 7 most common challenges faced during Salesforce migration that you should avoid.

1. A mistake of thinking switch to Lightning is easy

With a massive push from Salesforce about Lightning and the ease of switching from Classic has left many customers thinking that their interaction with the system is going to be lightning-fast. That is undoubtedly the case for the out-of-the-box features and functionalities. If your org has too many customizations, this may not be true.

The Lightning framework has moved much of the user interactions to happen in the front end without having to hit the server. This is the reason why it works well for out of the box features. When customizations come into the picture, you need to understand which customizations need to go away, which ones need to be there and how they will be handled in Lightning, and most importantly, what will be the impact on users and your processes.

2. Classic is excessively customized

If your Salesforce instance has several custom user interfaces built on Classic, migrating these custom components to Lightning without adequate impact analysis can lead to user issues. Analyze whether these classic components are necessary and the impact of migrating them as several customizations in Classic work won’t work properly in Lightning.

3. Migrate or rebuild?

There are two approaches to migrating custom UI ( custom pages and components) to Lightning. The first and the easier approach is to make the classic custom UI Lightning compatible so that it renders the same way as it did in Classic with minor differences. This ensures user experience remains unaltered, but it does not leverage the power and benefits of Lightning.

The second approach is to rebuild the functionality using a new UII by leveraging the power of Lightning. This is surely the recommended approach for the long term, but it is going to be more time consuming and expensive to do. Make sure you get expert advice to make correct choices.

4. Overuse of features to mitigate the high cost of migration

Lightning migration can be expensive depending on the extent of customization done in classic. But that is no reason to overindulge in hundreds of features that are entirely unnecessary or suboptimal for your business. This will reduce user satisfaction and performance.

5. Existing performance issues slowing down Lightning

When your org is complex and has a lot of data, it is important to ensure that your org is designed and maintained in line with best practices. Lightning interfaces can suffer from slow speed, responsiveness, and overall poorer outcome than expected. Performance issues have a direct impact on the experience and productivity of users.

6. Time-consuming migration timelines

When your org is complex and has a lot of data, it is important to ensure that your org is designed and maintained in line with best practices. Lightning interfaces can suffer from slow speed, responsiveness, and overall poorer outcome than expected. Performance issues have a direct impact on the experience and productivity of users.

7. Don’t overwhelm your users with features of lightning

Remember your users are already used to and comfortable with classic and not everyone can manage change easily. Plan your rollouts in a phased manner with smaller user groups, provide adequate training on using the new interface, and ensure you have the bandwidth to support users till they become comfortable.

We have put together a comprehensive Salesforce Lightning migration guide with everything from outcomes of successful migration and Do’s and Don’ts of Lighting migration to best practices and the checklist for success.

Download this free guide to ensure successful Lightning migration.