6 things to know about migrating to Salesforce Lightning
Salesforce Lightning has become a distinct and separate platform from its earlier iterations.
There’s no doubt that development for mobile and custom applications are far more user-friendly than they once were, yet there remain critical considerations to factor in as you make the transition.
So let’s dive right in shall we
- Your team will need to learn and adapt to a new user interface
Salesforce Lightning will feel like a whole new platform at first and getting used to the new interface will take some time. The learning curve won’t be steep for seasoned pros but there will be a learning curve nonetheless. While your users get accustomed to the new interface, there is a risk you might experience some data loss. Training up before the full migration would be an excellent idea to mitigate any data hiccups. We also recommend you lock down admin and user access to minimize accidentally deleting or corrupting data.
- The recycle bin is gone
Until Salesforce adds the recycle bin late this year [which should be soon], when records are deleted your team won’t be able to view or restore them unless you have a backup and recovery tool in place. Just be aware and make sure your data is backed up on a daily basis.
- Salesforce files replace the documents tab
In Salesforce Classic has a documents tab. In Lightning, that tab is replaced with Salesforce files. Realizing these documents are important, your team will need to upload them again as Salesforce files.
Important note: An ounce of prevention is worth a pound of cure. To safeguard your operations during the transition, set up a data protection mechanism to include monitoring, backup and recovery of all your Salesforce documents and files. This will save you from a world of hurt if anything goes awry.
- Migrate your Visualforce pages carefully being mindful of the complexities
Depending on your specific setup, migrating Visualforce pages to Lightning can be complex. Our recommendation is to migrate each page individually to sidestep any major issues. As you transition each page, it might become necessary to develop customizations to ensure any essential functionality is still available and that your html is intact. This means testing individually and methodically as well. QA each page as you go. It may seem laborious, but we assure you it will be worth it to safeguard UX.
Also ensure that all of the data, cases related to Knowledge articles, and attachments were moved and mapped correctly.
Last but not least, make sure that all permissions have come across properly.
- Any custom code might need fixing
The URLs in Salesforce Classic are generally straightforward although some Orgs could have custom code that will need to be repaired. In Lightning Experience, these URLs may not work anymore, which would obviously impact certain custom workflows or customizations. Before making the transition to Lightning, make sure you’ve considered any custom code that needs to be updated.
- Minimize Business Risk During Your Salesforce Lightning Transition
Before you transition to Salesforce Lightning Experience, secure your business with a solid data protection foundation. Business risk is high during this transformative initiative, which means it’s critical to have a comprehensive data, metadata, and attachment backup and recovery strategy in place beforehand.
With Vidushi Infotech, you can innovate confidently on the Salesforce platform with peace of mind that your data is safe and sound. To learn more about how to implement or migrate to Salesforce Lightening Experience, contact Sharon Herrnstein, Chief Marketing Officer at firstname.lastname@example.org
Source: Salesforce Lightening Experience