Salesforce Lightning was launched a little over three years ago. Packed with robust features that improve productivity, help sell faster and more effectively, and make more consequential decisions, Lightning is definitely the direction to move your CRM into for the future.
Although there is no real deadline put to the migration, it is quite obvious that Classic is not going to see anything “new and exciting” happening on its platform. With new Salesforce users being put on Lightning automatically, it will be fair to say that those who have migrated and those coming in new are likely to have the best of the resources from the Salesforce UI.
This blog is for ‘Classic-ers’ who wish to make that big move to Lightning, but are unsure of how and when to do it, and what to expect. So read on to know what you should be doing before you migrate:
Step 1: Assess your needs
The first thing you must do is to evaluate if Salesforce Classic is meeting the needs of your organization. Has it simplified the workflows and processes for your teams? Has it maintained the levels of productivity, or facilitated productivity enhancements? And the most important question to ask is whether your organization and its people are resistant to change.
If you have answered all the above questions with a well-thought “yes”, then perhaps there is still time before you get on with migration. However, Classic isn’t getting any upgrades or add-ons, and what you are getting now is probably all you will be ever getting. This in itself can become a compelling reason to consider a switch.
On the other hand, if your CRM is failing to meet your growing needs, is complicating your workflows and processes, and affecting your day-to-day critical operations, then it is time to collect all the adequate information you need for a gap analysis of Classic and Lightning.
Step 2: Execute a gap analysis
In this stage, you must figure out what features of Classic your organization needs and what are the new features from Lightning that will change the way your teams, systems and processes function. Your gap analysis should be able to answer these questions clearly:
- What are the new Lightning features that Classic does not support?
- Can your organization continue to up its sales game without these new features?
- How much will your organizational goals evolve over the years and will Classic be able to match up to the evolving needs?
Step 3: Test, test, test
If your gap analysis tells you that your organization would do better on Lightning, then it’s time to test drive the Lightning UI. You could do this by putting a specific user or group on Lightning for a few days, and then collate their thoughts/ feedback for analysis. Next, put a new group to test Lightning and gauge their opinions. Do a comparative study between two or more groups of users, give them a taste of what Lightning is like, and from these combined calculations, figure if Lightning will do its magic for your organization or not.
Step 4: Go for the Lightning Experience Readiness Check
If the basic trial of Lightning does not ruffle any serious feathers among your teams, and in fact shows positive signs, you could rightfully move to the Lightning Experience Readiness Check. This tool is a convenient way to decipher if your organization is ‘ready’ or ‘almost there’ to take the Lightning plunge. The Readiness Check tool is designed to offer a simple and easy to understand readiness report, with straightforward labels such as “The Good Stuff”, “Needs Some Attention”, and “Which Users Are Ready” that give users a quick idea of what their challenges are and what really works for them.
What’s great about the Readiness Check is that if it reveals that your organization is not ready for the Lightning Experience, it recommends apt steps to fix the issues. You can work on amending the problems right away; and once the issues have been addressed, you can run the check over again to confirm if you are ready to take on the Lightning Experience.
Step 5: Getting people on board
For most pioneers of change, this is the biggest challenge. When users of a much-loved and well-accepted UI are pushed to new waters, the levels of uncertainty and discomfort are high, and can be a huge hurdle to transformation. Your first step here would be to get the executive leadership and stakeholders on board to plan and allocate resources for the migration.
Next, pull together your power team of Lightning users to give your migration mission an impetus. Use their experience and positive results during the test period, in combination with the Lightning Readiness Report, to build a strong case for migration. Work toward “showing” what Lightning can do to sell your case. Work at gradually enlarging your troupe of power users, till you get all users on board. In the meantime, continue to educate, train and offer support, without which it would be impossible to accept change, predict roadblocks, and create a sense of familiarity and comfort with the new UI.
Step 6: Roll out
When you feel your team is confident with the Lightning Experience, go ahead and hit “Launch”! Keep a Salesforce consultant by your side to respond to any sudden SOS calls.
If you are looking for professional assistance for your Salesforce migration, write to firstname.lastname@example.org.