Four Steps to Planning Your Lightning Experience Migration
One of the most common questions we receive is “Why Switch to Lightning When Classic Works Just Fine?”
Well to be clear, your Salesforce investment will not be affected by staying in Classic. Your data, objects, custom fields and business processes will still function. However, with few exceptions, Salesforce is not investing in new capabilities for Classic.
If you want to take advantage of Salesforce’s continuing investment in innovation, now is the time to switch to Lightning. While some organizations will choose to stay in Salesforce Classic for the time being, making the switch to Lightning Experience (LEX) comes with a slew of benefits, including:
- Better functionality, including more out-of-the-box features like SalesPath and Lightning Dialer.
- A boost in ROI from increased user productivity, service efficiency, and a boost in sales performance with improved UX.
- Existing data migration, which means your data, objects, and fields already live in LEX allowing for a seamless transition.
- Better customization of page layouts is available with LEX and organizations like yours are already claiming increased user productivity.
A major step to staying competitive is by continually adapting to newer, more advanced tools that can enable your organization to work more efficiently. Below we will discuss the four steps we take to help our clients switch to LEX to take advantage of these new innovations. If you would like help assessing the level of effort to make the switch using our 4 step program, email your questions to firstname.lastname@example.org.
Four Steps to Successfully Planning the Switch to LEX:
Step 1. Assessing Lightning Readiness
Before getting the organization all worked up with the challenges ahead, take an internal team and really assess what the road ahead looks like. In our previous blog we took an in-depth look at 3 key questions to ask before thinking about migrating to LEX.
One of the main steps in assessing your readiness is running your “Lightning Readiness Check” to review what is and is not ready for LEX. You can find out how to run your Lightning Readiness Check here. This will provide an entire inventory of features and functionality gaps of your Salesforce instance. If you do not have an experienced admin to decipher this report, send it to a Vertiba LEX expert for a free assessment at email@example.com.
Step 2. Planning for the Change
According to Gartner Group, “59% of all CRM projects fail because of a lack of senior management involvement and Change Management.” Management’s active involvement is what makes Change Management work. Often times when a new program is brought in, IT is seen as demanding change.
With leadership buy-in and accountability drivers, a leader LEADS the change and drive accountability in the project. When this happens, suddenly the game changes.
Now assemble your team of champions, set a communication strategy and establish target dates against everything. As you start to move into testing and a deployment strategy, this is a great time to bring in some experts.
Step 3. Building and Testing
Now that the leadership team is on board and has expressed interest in switching to Salesforce’s Lightning Experience, be sure to utilize the Sandbox for all configuration and development changes. By using the Lightning Readiness Reports, your development team can make the necessary changes.
You will want to ensure that your Lightning Record Pages are configured with consistency and intuitive style. From one object to the next, consistency in layouts can greatly benefit the User Experience and ease the process of transitioning from Classic.
Assure that all custom buttons, links and VisualForce pages are Lightning-compatible. Using the Readiness Report, you can comb through these different components in the Lightning Interface within Sandbox and see what pages, buttons or links may be broken and need attention. It can be helpful to prioritize this list of components to ensure that the most important items are given the proper attention.
Best practice would be to build and test in iterative steps. That way both configuration changes and testing can be made in small batches, allowing for realistic expectations for both the Build and Testing processes.
Once your consultant has finished configuration and development, you should walk through the changes and confirm that all functionality meets your expectations. This is a good time to ask follow-up questions and make sure you understand minor changes in processes between Lightning and Classic interfaces.
Step 4. Training and Deploying
Send your admin to training events to learn the new platform tools. This helps an agency implement the new tool quickly and effectively. Put together a small group of key users who can start using the new interface, and provide feedback on usability, navigation, functionality, etc. of their day-to-day process on the new interface.
Capturing key user feedback and responses, making necessary changes and adjustments to your new interface will be key at this stage before rolling out changes to the larger user group. These key users can also become internal advocates of the Lightning Experience, and add to the organization’s transition from Classic to Lightning.
Expect questions to come up relating to the new interface. It can be helpful to provide user documentation on Lightning Navigation and using some of the new components that we built in step 3.
Once you’ve developed an implementation plan, the execution can happen as quickly as one month for a single group of users using Professional Edition and up to 18 months for a group of sales users who manage a lot of custom code. If you would like help assessing the level of effort to make the switch using our 4 step program, email your questions to firstname.lastname@example.org.