Call us Today +1 630 534 0220
Salesforce Lightning came out in 2015 . It was launched with big hype at Dreamforce and applauded as The Future of Enterprise Technology. The problem was, it wasn’t really ready. There were considerable product gaps and still had some way to go before you could migrate.


Fast forward to 2020, and now it’s fair to say that Salesforce Lightning is fully formed and completely ready to go. Salesforce is not selling Classic anymore, if you buy a Salesforce licence now you go straight to Lightning. In fact Salesforce is not updating Classic either, the features released with each new platform update are all in Lightning now.
This blog is for salesforce classic software users who wish to migrate to lighting but don’t know how and when to do it. And what to expect.. This blog gives you full in-depth detail about salesforce classic to lightning migration.
Following are some points that you should consider before you start migrating from salesforce classic to lightning.
1. List Down The Goals:

As much as Salesforce encourages businesses to make the shift from Classic to Lightning, some organizations are either not ready operationally or just don’t need the functionality enough to make the shift. However, if you think Lightning functionality will expand your business offerings, empower your team, or drive efficiency in your operations now or in the near future, it’s time to outline your strategy.
We recommend starting with a clear list of goals for the Lightning migration. What do you need Salesforce Lightning to do that Classic can’t offer? What do you want to accomplish? By starting with a list of business goals and prioritizing features based on them, you can build a focused and goal-driven transition process.
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.
2. Outline Existing And New Processes:

A Transition to Lightning doesn’t give you access to new features and functionality, that’s just the additional benefit. There are potential risks too.
Many companies find difficulty 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 obstruction and even set the company back instead of moving it forward.
To avoid this, it is recommended to outline all existing and new processes and discuss them with each affected team before moving onto planning for development. If a team expresses doubt or concern with how things will work in Lightning, now is the time to discuss that.
Designing a strategic process beforehand prepares your team for a flawless launch. It also guarantees fast and efficient development during the development stage.
3. Run A Lightning Readiness Check:

It is suggested that you run a Lightning Readiness check. It can help you to pick on potential unanticipated bugs or organization inconsistencies that you may have missed during the planning.
4. Sandbox Testing:

Now that you have your well-defined plan,So It is recommended to use a sandbox testing environment to isolate and test your changes without affecting other developers’ work. This allows you to understand how the updated code would affect all users.
It 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 eliminating bugs before going live.


5. Evaluate The Goals:

Before moving on, backtrack 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 goals are not achieved, take a step back and evaluate where you change direction.It is time consuming exercise but if you don’t refocus on your goals now, you may never be able to correct the course.
6. Introduce Lightning To Power Users:

Before rolling out lightning in organization, it is necessary to test it on power users. Start rolling out the lightning one at a time, this will let you know if there is any issue in lightning migration.Your productivity will not be affected and it will help you understand what actually everybody needs from the new user interface.
Start collecting reports from the power users, make changes, and launch out the updated lightning. Follow the process again, and again this will help you to migrate while maintaining the productivity of the company. If by mistake, you launch it to all the users together, then you may face the problem of causality and discomfort among its users.
7. Documentation:

Next, before launching your Lightning migration, make sure that you have the necessary documentation for the steps with which you can undergo the task very smoothly.
Write down all the process and workflow that you have gone through while performing the task and start building detailed documents on it. These details will help other developers and users to make any necessary changes or to make an update in the migration process.
8. Launch:

After analysis and training when you think all the users of the team are ready to accept the lightning over the Classic then start the process of migration. Also, it is mandatory to keep the contact details of the Salesforce Expert with you so that when there is any case of emergency you can immediately call them and they can take quick action to help you.
This is it. All these small tips and steps will help you to go through the Salesforce Lightning Transition.If you’re looking for more direction in your migration to Lightning or need help understanding how to customize the features you need, contact our team.

Do You Need more information ?

For any further information / query regarding Technology, please email us at
OR call us on +1 630 861 8263, Alternately you can request for information by filling up Contact Us
facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>