Our organization is finally moving away from Salesforce Classic, but I’m overwhelmed by the transition. As a Salesforce Admin, what are the most critical steps to ensure that custom buttons and JavaScript links don't break during the migration? I want to make sure the user adoption stays high while maintaining data integrity across our new Lightning pages and components.
3 answers
The most important first step is running the Lightning Experience Readiness Check. This tool provides a detailed report on what will work and what needs manual intervention. Focus heavily on converting your JavaScript buttons into Lightning Actions or Flow, as JavaScript isn't supported the same way. Additionally, use the App Builder to create intuitive layouts that actually take advantage of the new UI features. Don't just clone Classic; redesign the experience to provide better visibility into key metrics for your sales teams to ensure they actually enjoy using the new system.
Have you considered using the Lightning Transition Assistant to track your progress, or are you doing this manually? I’ve found that specific user groups react differently to the new interface, so I'm curious if you've identified "champions" within your departments to help lead the change?
Focus on User Training and Documentation. Even the best technical setup will fail if the users don't know how to navigate the new workspace or find their favorite filtered lists.
I completely agree, Amanda. Detailed documentation or even short Loom videos explaining the new navigation bar can save the Admin team hours of troubleshooting repetitive questions later.
Yes, Mark, identifying champions is vital. I recommend selecting one power user from each department. Give them early access to a sandbox environment so they can provide feedback on the Lightning Record Pages before you go live. This builds a sense of ownership and reduces the overall friction during the deployment phase for the rest of the staff.