Classic to Lightning Journey Part-3

In the last two blogs, We have discussed the pre-requisite for enabling Lightning Experience, gap analysis of Lightning Experience compared to Classic view and things to do to check readiness report of Lightning Experience.

Now, its time to discuss the readiness report, its significance and action it recommends.

What is in this report?

Rolling out Lightning Experience to your users requires thoughtful planning. To get started, this report gives you a sweeping view of where you stand with Lightning Experience. Salesforce includes guidance on which users are most prepared to help you test the new interface and recommendations on how to tweak some key features and customizations that need your attention. For some users, Salesforce offer estimates about how your rollout might go. That way, you’re prepared to answer hard-hitting questions about the business value of moving to Lightning Experience.

What Does the Lightning Experience Readiness Check Evaluate?

  • The impact Lightning Experience has on your users’ productivity.
  • The level of effort it might take for you to roll out Lightning Experience.

Here’s what the Readiness Check evaluates for you.

  • User profiles
  • Tabs and objects:
    • Documents
    • Territory Management
    • Enterprise Territory Management
  • Sales Cloud related lists:
    • Account Contact Roles
    • Account Partners
    • Campaign Influence
    • Opportunity Partners
  • Custom buttons and links:
    • JavaScript
    • URLs that link to other pages in Salesforce
  • Actions and buttons
  • Visualforce pages
  • Home page and sidebar components
  • Email templates
  • Mail merge
  • Lookup fields
  • Activities
  • Cases
  • Report and dashboard folder sharing
  • Third-party computer-telephony integration (CTI)
  • Salesforce Console (Sales and Service)
  • Omni-Channel
  • Live Agent
  • Salesforce Knowledge
  • SOS
  • Entitlements
  • Solutions
  • AppExchange packages
  • Hard-coded URLs and My Domain
  • S-controls
  • Sharing buttons
  • Web browsers

Readiness Check requires metadata to evaluate features. Therefore, the report sometimes only evaluates a feature for a specific area. For example, Salesforce cover Sales Cloud related lists, but not all lists in general. Salesforce covers email templates but not mass email. In other cases, Salesforce doesn’t cover a feature at all, such as customizable navigation, Ideas, macros, custom keyboard shortcuts, recycle bin, reports, and dashboards. Salesforce recommends that you manually review features and customizations not covered by the Readiness Check before rolling out Lightning Experience to your users. Use the Lightning Experience Preview tool to step through features that aren’t evaluated with a “Lightning Experience Champion” (a Salesforce super user). And, Salesforce is always adding new features to the Readiness Check, so check the Release Notes for future additions.

The very first thing mentioned in the report is Why Move to Lightning Experience?  Salesforce has conducted a survey to identify the impact lightning has on business which says:-



Note:- Results can vary by company and business objective. To calculate your own company’s business impact from making the move to Lightning Experience, run the Lightning Experience Business Assessment.

The next thing report tells you is the estimate rollout effort. Offcourse, You already has done the gap analysis and you have the readiness report which is enough to estimate your rollout effort. The Lightning Experience readiness report tells you about estimated hours spent on Salesforce development, configuration, and administration along with estimated hours spent on change management, user testing, and user training.

The rollout effort numbers will be purely based on numbers of Custom buttons and links – URLs, Visualforce pages, AppExchange packages and third-party Computer-Telephony Integration (CTI), Sidebar components, Salesforce Console and other features available in your Org.effort.PNG The reports also discuss how you can use it. Let’s say you are not able to figure out what do with a problem, You can contact to Lightning Experience specialist from Salesforce. Recently, Salesforce has started identifying the Lightning Champion who has successfully rolled out Lightning Experience at least once, know the ropes of change management, like to get hands-on with Lightning Experience and show others how to do the same, want to present, share, and be a mentor, up for a yearlong commitment to the program, completed the Lightning Experience Rollout Specialist Superbadge.

The next thing reports tell about the users who are eligible for  Lightning rollout. The report will help to identify the users who can be enrolled in Lightning Experience and the features you need to review which they use regularly. Once You had reviewed the features, they are the quick win for you.

user ready.png

The Reports also provide a high-level plan where features have been categorized into four categories. They are:-

  1. Ready
  2. Requires some review
  3. Requires your attention
  4. Requires a thoughtful rollout

The features under Ready column are Lightning compatible and good to go. You may need to have some review before marking them as Lightning ready. They may work or may not in Lightning. The one who falls under requires your attention needs some modification in order to become Lightning Compatible. You have to worry about requires thoughtful rollout features. They are either not going to be available in Lightning or may not work completely. You can see in the below image:-


Till now, We have got the rollout effort estimate and high-level plan to review the features to make it Lightning ready. Its time for action but you need to know what actions you will be going to take in order to make it Lightning Compatible.

Always, remember the fact that until unless all the users in your Org rolled out to Lightning, You have to make the change in your features in such a way it should work in both Classic and Lightning. There will be the case when you make a change and it would stop working in Lightning.

In the next blog, I will write about the Lightning Migration Transition Assistant features.

Leave a Reply