Lightning Migration is not a maybe. It’s a must.


By Bailey Bintz

Whether you’re a Salesforce user who knows a lot or a little about the platform’s technical framework, you’ve likely at least heard of the Lightning Experience migration. If you’re hazy on the details of this update, you’re not alone. Migrating to Lightning Experience affects different orgs in different ways, and that can make it hard to tell which seemingly urgent directions from Salesforce actually pertain to you. 

If you’re still unsure whether or not you need to plan for a Lightning Experience migration, I can simplify things for you right now. You do. I’m also here to help you better understand the what, why, when and how associated with this major Salesforce update. 

Let’s start with the “what” & the “why.”

Salesforce Lightning Experience is a completely re-imagined Salesforce platform that introduces a ton of UX and functionality enhancements. It is the framework on which all future Salesforce innovation will be built. Most users will find immediate benefits in the updated user interface. The Classic experience offered a two-column layout with the list of related items at the bottom of the page, which leads to long pages and lots of scrolling. The Lightning Experience is based on a simpler three-column layout with more refined tabs that make customer information readily accessible. Think less clicks to achieve the same goal. And less clicks to achieve the same goal equals greater operational efficiency. 

These are great near-term benefits that every Lightning Experience adopter will have access to upon migration, but a big “why” associated with this migration is that new Salesforce features and updates–from UX to workflows and reporting capabilities–will only be added to Lightning Experience, not Salesforce Classic. 

This brings us to the “when.”

As of Q1 2020, Salesforce has begun activating Lightning Experience for all orgs on a rolling basis. While no org is required to actually turn on Lightning Experience this week, this month, or this even this year, Salesforce will increasingly focus their product development and support resources entirely on services that benefit Lightning Experience users. To use an analogy, you’re free to keep chopping down trees with an axe, but in this day and age, you’re going to see far better results with a chainsaw. 

Now that we all agree, let’s talk about “how.”

First, do yourself a favor and run the Lightning Readiness Report in your Salesforce org (check out the instructions here). Once your report is pulled, you’ll have a high-level estimation around your projected productivity boost after converting to the Lightning Experience. On top of that, you’ll be able to anticipate the effort necessary to convert the following sensitive components: 

  • Visualforce pages
  • Custom buttons and links
  • AppExchange and managed packages
  • Users & user profiles

It’s important to note that if you leverage custom Salesforce code or if you installed Salesforce AppExchange apps to further tailor your Salesforce org, both of these are examined in the Lightning Readiness Report to ensure these functions will work the same at the time of launching your Lightning Experience.

Running the Readiness Report is a great place to start, but from Canpango’s experience, the Lightning Readiness Report only shows roughly 30 percent of what needs to be converted and migrated into the Lightning Experience. 

The switch from Classic to Lightning is a great time to re-examine day-to-day processes, interdepartmental communication and your organization’s operations with one goal in mind—to define which parts of the machine are well-oiled and which parts warrant a little bit of process re-engineering.

Additionally, this might also be the time you ask yourself:

  • Is it a good time to add user groups to Salesforce?
  • Is it a good time to take a look at other functions that could be brought into the platform?
  • Is it a good time to incorporate marketing automation?
  • Is it a good time to take a look at building a dedicated customer login portal, a customer service module, or integration to your ERP or billing program within Salesforce?

From my experience with helping clients through their Lightning migration journey, we’ll typically work together to:

  1. First and foremost, get a non-disclosure agreement in place.
  2. Have a brief conversation about your Salesforce org use cases.
  3. Have one of our delivery experts take a peek under the hood of your org to get a better feel for the unique approach that makes the most sense for your migration.  

At Canpango, our ultimate goal is to put together a project plan that delivers your updated interface with increased productivity and re-engineered processes that facilitate engagement and keep your sales, services and marketing teams engaged and driving positive business outcomes.

Are you looking to take your Salesforce Classic Edition to the next level with an upgrade to Lightning? You can learn more about those services on our Lightning migration page or by contacting us here.

ABOUT THE AUTHOR

Bailey Bintz is an Account Executive at Canpango. Having worked in a sales capacity for Salesforce itself, Bailey leverages her vast understanding of the CRM along with her seasoned set of relationship-building skills to help clients across a span of industries identify Salesforce solutions that meet their unique business needs.

Featured Posts

The Fix

Stay in the know with insights and updates delivered directly to your inbox.