You’ll likely need to customize Lightning to fit your internal process, such as creating Lightning apps or sales paths. You might need to replace legacy features you’re losing with Classic, or add new features to maintain or enhance your business process.
Replacing legacy features is often the most time-consuming part of the customization process. Looking back at the gap analysis we talked about in the last chapter, you should have your list of items that need to be updated.
Work through your list of updates systematically and make sure you have an answer to any features your stakeholders might consider necessary.
You can automatically convert some legacy features to their updated counterparts. Classic actions and buttons, JavaScript buttons, and Visualforce pages can be automatically converted through the Lightning Experience Configuration Converter.
Some other features might require an AppExchange app to be transferred. Classic notes and attachments can be converted with an free AppExchange tool called Magic Mover, for example.
At this point, you’ve done all your preparation and planning. You’ve got a strategy for your roll out and have a clear idea of what a successful migration should look like. Now, it’s time to launch!