One of the best investments you can make in your Lightning Experience rollout is to have a clear plan. A plan helps you do things in the right order, identify key resources, communicate with everyone, and have a clear end date in mind.
Depending on the size of your organization, you could be working with a Change Management department or have a project manager assigned to the rollout. Or perhaps you’re the one charged with organizing and executing the rollout from start to finish. However the work gets divvied up, use the Lightning Experience Rollout module to help define your overall rollout strategy.
At this point, you’ve evaluated the benefits of Lightning Experience and are ready to deploy to some or all of your users. Next, we’ll walk you through the technical steps to prepare for and enable Lightning Experience for your users.
Let’s dive into the details.
If you haven’t already, consider enabling and setting up several supporting features before turning on Lightning Experience. These features ensure that the new user interface is optimized to help your sales reps sell faster and help your service reps support customers faster.
- Related Files
- Leverage the rich features and flexibility of Salesforce Files from standard Salesforce objects and your custom objects. Add the new Files related list to page layouts so that users can upload files to records, see files associated with records, and quickly page through files in the modern, visually rich preview player.
- Help your users stay organized with our enhanced note-taking tool. It’s a breeze to create rich-text notes and quickly relate them to specific records. When you turn on Notes, remember to add the new Notes related list to page layouts so that your users can create and read notes directly from their records.
- Help your users adopt your company’s processes to work more efficiently or close more deals. Set up a process based on an object’s status or stage. Add guidance for success at each step in the process.
- Duplicate Management
- Create duplicate rules to alert users if they’re about to create a duplicate record. Craft your duplicate rules to control whether and when users can create duplicate records in Salesforce.
- Lead Conversion
- Keep the sales process moving by letting your sales reps convert qualified leads to contacts. At the time of conversion, sales reps select an account for the newly created contact, or create an account if it’s not yet in Salesforce. Reps can also create an opportunity on the spot. Add the Convert button to the Lead page layout.
- Give your reps instant access to relevant, timely news about their accounts, contacts, leads, and opportunities. This feature is available only in English, so if your org uses a different primary language, you might not want this option.
- Social Accounts, Contacts, and Leads
- Keep the team up to date by letting reps link their accounts, contacts, and leads to matching Twitter profiles. Users can see Twitter user profiles and people in common in Salesforce and quickly access tweets.
- Shared Activities
- Represent activity relationships more accurately by letting your sales reps relate multiple contacts to individual events and tasks. Shared Activities is forever. After the feature’s enabled, it can’t be disabled.
- My Domain
- Create a subdomain with the Salesforce My Domain feature. A My Domain subdomain helps you manage login and authentication. You must set up a My Domain subdomain to use Lightning components in Lightning component tabs, Lightning pages, the Lightning App Builder, and standalone apps. To set up a subdomain, see My Domain in Salesforce Help.
We review some of these features in more depth later on.
You can enable some of these recommended features from the Lightning Experience Migration Assistant, which you can find in Salesforce Classic Setup. Just look for the Lightning Experience Migration Assistant tile at the top of the Setup menu.
Next up, make sure that the right users can access Lightning Experience when it’s turned on. You can fine-tune access with permission sets and custom profiles. Meaning you can do a phased rollout, starting with a small pilot group or a specific team of users who can benefit from the new interface. Or go for it and set your entire organization loose. You can also control who immediately switches to the new interface, who stays in Salesforce Classic until they switch themselves, and who can’t switch back to the classic interface. The power is yours.
Users require the Lightning Experience User permission to access Lightning Experience. By default, this permission is automatically enabled for all users with a standard Salesforce profile. Custom profiles don’t automatically include the permission.
So first things first, do you have users with standard profiles who you don’t want accessing Lightning Experience yet? Move these users to custom profiles that don’t include the Lightning Experience User permission.
For users assigned to custom profiles, decide who gets Lightning Experience access now and who you’ll set up later. Consider these options.
- Want to test Lightning Experience with a small group of custom profile users but you don’t want to turn it on for everyone assigned to these profiles? Create a permission set that includes the Lightning Experience User permission. Then apply the permission set to each pilot user. When you turn on Lightning Experience, only pilot users see the new interface.
- Interested in rolling out Lightning Experience to everyone
assigned to specific custom profiles? Or ready to enable all your custom profile users?
Adding the Lightning Experience User permission to profiles is the fastest way to
mass-enable the new user
If you’re a Data Loader ninja, you can save time by updating many profiles at once. But remember, with great power comes great responsibility. Take care you don’t inadvertently enable or disable other features.
If you’re limiting Lightning Experience to a subset of your users, try to keep all members of a functional team on the same experience. If you have team members who often share links and work closely together, include them all in your pilot. See Considerations for Switching Between Lightning Experience and Salesforce Classic for more details.
Decide Who Immediately Switches to Lightning Experience and Who Can’t Switch Back to Salesforce Classic
You obviously want the users you’ve set up for Lightning Experience to start working in the new interface sooner than later. There are several options you can use to encourage adoption of Lightning Experience. Choose what’s right for each user.
- By default, Lightning Experience-enabled users stay in Salesforce Classic and automatically get the Switcher, so they can switch themselves when they’re ready. This may be the best option if you want to enable Lightning Experience now but your team isn’t fully trained yet or it’s not a good time to introduce a major change.
- You can set it up so the users who are trained and ready to go immediately get Lightning Experience as their default experience. These users also get the Switcher, so they can return to Salesforce Classic as needed. See Switch Users to Lightning Experience.
- When you’re ready for users to dive into Lightning Experience without looking back, you can move them to the new interface without the option to switch back to Salesforce Classic. See Make Lightning Experience the Only Experience.
With the right users set up for Lightning Experience, you’re ready to go live. Fortunately, it’s easy to turn on Lightning Experience using the Lightning Experience Migration Assistant.
From Setup in Salesforce Classic, click Get Started in the Migration Assistant tile at the top of the menu.
On the Turn It On tab in the Migration Assistant, click the button to switch it to Enabled.
That’s it! The users you’ve enabled and set up to immediately switch to the new interface automatically start enjoying Lightning Experience when their current session refreshes or when they log in. The users you’ve enabled but opted to leave in Salesforce Classic now have access to the Switcher and can switch to Lightning Experience whenever they want.
Ideally, Lightning Experience meets the needs of everyone in your org. But just in case someone needs access to a feature or tool back in the classic interface, we provide the Switcher. By default, users enabled for Lightning Experience automatically get the Switcher. Which they can use to...wait for it...switch between Lightning Experience and Salesforce Classic whenever they need.
The Switcher is smart. Whenever you switch, it remembers that user experience as your default preference. So if you switch to Salesforce Classic, the classic interface becomes your default preference. If you switch back to Lightning Experience, the new interface becomes your default preference. And so on and so on.
How do you get to the Switcher?
In Salesforce Classic, click the name in the upper-right corner, then select Switch to Lightning Experience.
In the Lightning Experience header, click the profile picture and select Switch to Salesforce Classic.
A Few Switcher Gotchas
Switching between Lightning Experience and Salesforce Classic affects the underlying URL routing logic and can lead to some unexpected results when links are resolved. There can be snags with bookmarks and sharing links in emails or Chatter posts—especially if only a subset of your users is enabled for Lightning Experience.
If a user clicks a link to something that’s not supported in Lightning Experience, Salesforce switches to Salesforce Classic in a new tab while the original Lightning Experience window stays open.
Users who aren’t enabled for Lightning Experience can’t access Lightning Experience links, including links posted to Chatter or emailed from a Lightning Experience user.