Lightning migration walkthrough

Let’s get over the pitfalls of Lightning migration together.

Sorry, your browser does not support inline SVG.

The long-anticipated conversion to a new user interface is finally here. The inevitability of migration till 2020 has been recently announced by Salesforce, and now many companies have a lot to worry about.

The main pain point is the necessity to spend extra time, money and other resources to switch UIs. So, each and every Salesforce user is worried whether the transition period can be smoothened and quickened as much as possible.

To make your life easier, we’ll go over the pros and cons of both UI versions, discover main user pains, outline migration steps, recommend tools for better switching, and so on.

Subscribe
to our newsletter

Classic vs Lightning: advantages and disadvantages of different UIs.

Everything forward will be Lightning, as Salesforce executives claim. It offers tons of benefits for businesses and will surely be embraced by every employee in every company, sooner or later. Let’s consider the most prominent advantages and disadvantages of Lightning Experience User Interface.

Lightning UI pros:

  • It’s faster, quicker to customize (with easy drag and drop configuration) and easier to maintain; though it requires extra time to get adjusted to.
  • It is more flexible and dynamic as compared to Classic UI, with better visualization due to Smarter Views.
  • Sales Path efficiently helps define key stages for a Lead to go through and fields per stage a sales rep needs to complete.
  • The new practical Kanban view offers insights into opportunities that help manage them easily.
  • Modern design and enhanced functionality for Reports, Charts and Dashboards.

Lightning UI cons:

  • Teams will spend more time on migration. It’s an arduous process and can take up to several months or even a year.
  • Slowdown in users’ adoption as a result of their long coexistence with Classic.
  • Some applications from the AppExchange might not be supported in the new edition right from the start. You need to check everything minutely before the migration.

In fact, both Classic and Lightning versions lack some great features. For example, sales and support reps heavily use the Classic UI’s feature that allows them to assign tasks in Lightning to multiple users. This one is not available in Lightning yet.

On the flip side, users will miss some Lightning features, like Sales Path, Assistant, Kanban, Einstein Lead Scoring, in Classic UI, and so on.

Lightning migration pitfalls.

While changing UIs, users can naturally experience major technical issues. The main task of the Salesforce admin team in a company is to identify gaps and help users eliminate them. As for pain points, here are some of them:

User Adoption

Unfortunately, lightning doesn’t allow for record sharing. The way out can be switching to Classic, finishing the task, and returning to Lightning (or using a special component from Salesforce AppExchange). Not the best way, but at least there is one for now.

Low operation speed

The new interface is loaded with data and functions, leading to low operation speed. This one will definitely irritate many users. You’ll also need better hardware for Lightning’s virtual machines.

JavaScript buttons

Lightning also doesn’t support Custom JavaScript buttons. The way out can be an alternative build of quick actions, triggers or workflow rules.

On-page search

Ctrl + F doesn’t work as an on-page search. The possibility to find something in a new system is vital, but it’s absent from Lightning.

Visualforce

You should review Visualforce pages, sort them out be relevance, and migrate to a new Sales Force Lightning Component. You should also redesign all pages with the Lightning design system.

Event attendees

You can’t add event attendess in Lightning.

URLs

Lightnig also doesn’t allow users also can’t auto-populate using URL.

Task status

When you transfer a completed task, their status changes and requires manual processing to be corrected.

As you can see, there are no off-the-shelf solutions for these issues right now. Let’s hope Salesforce developers will introduce the needed improvements as soon as possible.

A hassle-free way to migrate to Salesforce Lightning Experience.

As migration is inevitable, you main challenge is to assure a smooth transition. Below we offer a set of tips from our inhouse specialists on how to migrate to Lightning with minimum losses.

Implementation workflow:

  1. Outline your transition goals
  2. Map out workflows
  3. Discuss and prioritize functionality
    and potential integrations
  4. Run a Lightning readiness check
  5. Work in a Sandbox
  6. Test your goals
  7. Roll out Lightning to power users
  8. Create detailed documentation
  9. Introduce Lightning and do the training
  10. Launch

It’s vital to define a plan in the first place. It will help you reduce hiccups while swapping user interfaces midstream. Plus, you have to think about adequate training for your team in advance. You can employ versatile sessions, webinars, strategic meetings, face-to-face trainings and coaching sessions.

Sample Plan:

  • Educate your company on Lightning benefits
  • Conduct a gap analysis of non-supported features
  • Decide which users move to Lightning first (test group)
  • Develop an internal marketing strategy to educate future users
  • Create a training plan

Change on the horizon.

From now on, Salesforce intends to build new features only for Lightning. There are already 200 things that you can do with it. Unlocking new opportunities of Lightning Experience, as compared to Classic UI, can become the final straw that breaks the camel’s back. The reason is the apprehension of some companies’ stakeholders to migrate because of the extended learning curve, the need to prove ROI, etc.

Still, everyone needs to remember that such changes are never easy, and that the migration is imment. Here’s to hoping it will go as smooth as possible for the all companies.