From our experience in helping clients migrate from Salesforce Classic (Aloha experience) to Salesforce Lightning Experience, we have found that the change can require significant business process evaluation and adjustments to user workflows. It is not just a change in the way Salesforce looks, but also a core change in the way users interact with CRM.
The following questions can help you (or us) determine how much time is needed to accommodate for requirements gathering and business process mapping and reengineering:
- Who are all the business groups involved for each Salesforce instance that will move to Lightning Experience? Do you have Business Analysts for each of these groups that understands and knows the business processes and user workflows in each Salesforce instance? Training and workflows for these groups will impact your project efforts and timelines.
- Do you already have business processes well documented and have process flows?
- Do you have sufficient Salesforce-specific Business System Analyst resources to handle business process discussions and reengineering of business process to work with the new user experience workflow changes? This will require knowledge of the differences between Lightning and Classic versions. Those changes will need to be sufficiently translated into technical requirements for adjusting the system. The Lightning system design and limitations will also influence business process changes.
- Will you want to migrate multiple Salesforce Orgs or business groups from Classic to Lightning in parallel or serially? If the latter, what order would you want to implement the changes in the different Orgs? Are you considering a pilot rollout for each or a “big bang” rollout to all users?
- What is the timeframe for each org (or all if at once) to be migrated to Lightning?
- With a change to Lightning UI, some users find it very difficult to adjust to the change. Even the basic navigation of Salesforce will change with Lightning. Do you expect any of the three different business segments to be resistant to change? Do you have a plan for managing, communicating, and enforcing compliance to the change?
- Do you have a training organization that will be handling training materials and training of the users? Do you need those trainers trained in how to use Lightning?
- Accessibility is not supported by Lightning. Will you need customizations for Accessibility or will you wait to migrate these type of users if you have any?
Every aspect has to be evaluated on an individual basis, as every organization will have varying degrees of readiness. There isn’t a one-size-fits-all approach to a Lightning migration. These questions give our Salesforce clients a sense of what the process will entail, and how to prepare their teams.
Have questions for us? Leave a comment below, or reach out to us anytime here.
