Salesforce introduced Lightning couple of years ago and have been steadily making improvements with each release.
Around Summer 2019 Salesforce started to send out messages to clients about pro-actively migration existing Orgs over to the new Lightning interface.
During the last few years we have helped several UK companies migrate from Salesforce Classic to Lightning both for Professional and Enterprise editions. Although we don’t expect Salesforce to remove Classic for some time yet, they do have a vested interest in getting all their customers over to the new Interface. To that end, all new developments are only on the new Lightning platform and when logged in to Salesforce, you will be experiencing pop-up screens with various messages about new Lightning features.
Before you contemplate a Salesforce Classic to Lightning migration, you can run some tests using the tools that Salesforce provides you. This is called a Lightning Readiness Test. Once started, the tool will go and check any customisations in your Org and will also look for items that may be challenging to migrate. It will then send you a report of the highlighted areas. The report is useful, though can raise as many questions as it answers, for example, it may report on issues with an installed Managed Package that utilises old Classic technology. However, it does not take into account that the object is no longer used!
We find the Readiness report useful, but it is not a replacement for detailing your current processes and mapping those against how that would work (or not0 in Salesforce Lightning. However, we have always found a solution to any problems and we believe that Salesforce Lightning will offer multiple benefits over the Classic interface.
However, we believe the biggest issue is not the technical changeover, but the change to your Users. If you automatically switch over to Lightning from Classic, you invariably will receive negative feedback from you Users. That is because Lightning is very different and common items are often in very different places. For some strange reason, Salesforce doesn’t automatically add a lot of the common features to the record pages. Items such as ‘Log a call’ and ‘Close Case’ can sometimes be missing and have to be added back in! When things like this happen, Users get frustrated and start to lose faith in the system. That is why it’s important to seek the help of someone who has experience with this type of migration.
We recommend that you setup a Salesforce Sandbox and change that over to Lightning, Then run your common processes through the system from start to end. This will give you a clear idea of what needs fixing before deploying to your live Users. Once you have a list of the items and have fixed them in the Sandbox, you can then move to making Lightning available for Systems Administrator in your Production environment whilst your work through the setup. Only then should you start to migrate Users over to Lightning.
How Can We Help You
We would be happy to have an informal chat with you about your requirements and to offer advice or see if we can be of assistance to you. Please complete our simple form and we will contact you as soon as possible.
Help & Advice
Project recovery
Support & Training
Integration to a 3rd party system
Get in touch
The post How to migrate Salesforce Classic to Lightning appeared first on Zon Projects.
The Post How to migrate Salesforce Classic to Lightning was first published here: https://ift.tt/2AZM8io
No comments:
Post a Comment