How do you migrate a Salesforce instance from Classic to Lightning when half the AE team has 5 years of muscle memory in Classic?

Question

Pulse RevOps · The Machine · Accepted Answer

**Quick take:** Run a 12-week migration with a 4-week parallel-mode period, a named-rep "champion" model, and a hard cutover date that the CRO personally enforces. The Classic loyalists aren't being irrational — they're protecting their pipeline. Build a transition that proves Lightning is FASTER for the three tasks they do most, and they'll come along.

## The Detail

I've watched three of these migrations go sideways. Every time, the failure mode was the same: an admin enabled Lightning Experience, sent a "we're moving!" Slack post, set the org default to Lightning, and then watched 18 reps revert to Classic within 48 hours because they couldn't find the Activity Timeline or the inline edit was 200ms slower than they remembered.

The migration isn't a technical event. It's a behavior-change campaign with a software backstop.

## The 12-Week Plan

**Weeks 1-2 — Discovery and Readiness Assessment.** Run the **Salesforce Lightning Experience Readiness Check** (built-in report). It enumerates VisualForce pages, JavaScript buttons, hard-coded URLs, S-Controls, and unsupported features. Triage: keep, convert, retire. Identify the 5-10 "muscle memory" workflows AEs do daily (log a call, edit opportunity stage, mass-update tasks, run a list view, send an email template). These are what you optimize for in Lightning.

**Weeks 3-4 — Convert and rebuild.** Move VisualForce to Lightning Web Components where it matters. Rebuild list views in Lightning. Configure the **Utility Bar** with the four tools reps use most (call logging, recently viewed, dialer, notes). Set up **Path** on Opportunity so stage guidance is visible. Use **Kanban** for pipeline view. Build a Lightning App per persona (Sales, Service, Manager).

**Weeks 5-6 — Pick champions.** Two AEs per region. Pay them a $1,500 spiff to use Lightning exclusively for two weeks and document every gripe, gap, and "Classic was faster" moment. Their job is to be the loudest voice in week 9-10. Sales managers and the CRO must use Lightning during this period too — no exceptions.

**Weeks 7-8 — Parallel mode.** Everyone can switch between Classic and Lightning via the user menu. Build a dashboard tracking % of user sessions on Lightning vs Classic. The number you want by end of week 8 is 60%+.

**Weeks 9-10 — Training and "speed wins" demos.** Two 45-minute live sessions per region. Don't do generic "here's what's new in Lightning" — do "here are the 7 things you do every day, and here's how they're now 30% faster." Record everything. Pavilion's enablement content emphasizes this: train on tasks, not features.

**Weeks 11-12 — Cutover.** Use the **Switch Users to Lightning Experience** permission management. Set Lightning as the default. Disable the "Switch to Salesforce Classic" link via custom permission for everyone except admins. Run a war room for 5 business days post-cutover with a dedicated Slack channel for issues.

## The Cutover Sequence

```mermaid
flowchart LR
    A[Week 1: Readiness Check] --> B[Week 3: VF -> LWC Conversion]
    B --> C[Week 5: Pick 2 AE Champions/Region]
    C --> D[Week 7: Enable Parallel Mode]
    D --> E[Week 9: Speed-Win Training]
    E --> F{Week 11: 75% on Lightning?}
    F -->|Yes| G[Hard Cutover Day]
    F -->|No| H[Add 2-Week Extension + Fixes]
    H --> F
    G --> I[5-Day War Room]
    I --> J[Retire Classic Permission]
```

## Vendors and Tools

- **Salesforce Lightning Migration Assistant** — built-in, run it weekly.
- **Salto** or **Gearset** for source-controlled rollouts of new Lightning components.
- **WalkMe** or **Whatfix** for in-app guidance overlays during the parallel-mode period. WalkMe lists at $9-$15 per user per month and is worth it if you have 75+ users; below that, build native Lightning Path guidance.
- **Gong** call reviews to spot reps who are getting stuck (you'll hear "let me pull this up" pauses get longer for reps who haven't adapted).

## Handling the Classic Loyalists

The five-year veterans typically split into three buckets:

| Persona | Real Concern | What Works |
|---|---|---|
| The Speed Junkie | "Lightning page loads slower" | Show p95 page-load benchmarks; tune slow components; move them to a sparse Lightning App layout |
| The Customizer | "I have 18 personal list views I lose" | Migrate every list view manually; have RevOps sit with them for 90 minutes |
| The Skeptic | "Last time we migrated tools, it broke things" | Make them a champion; pay the spiff; give them admin-of-the-day visibility |

Don't argue with the Speed Junkie about whether Lightning is faster in absolute terms. They're right that the initial load is heavier — Salesforce documents this. Optimize the page layout, remove unused components, and the perceived speed catches up to Classic within two weeks of use.

## Hard Truths

The CRO has to use Lightning personally — visibly — from week 5 onward. If they slip back to Classic for "this one report," half the org will too. Hard cutover dates work; soft cutovers don't. Bridge Gr

Persona	Real Concern	What Works
The Speed Junkie	"Lightning page loads slower"	Show p95 page-load benchmarks; tune slow components; move them to a sparse Lightning App layout
The Customizer	"I have 18 personal list views I lose"	Migrate every list view manually; have RevOps sit with them for 90 minutes
The Skeptic	"Last time we migrated tools, it broke things"	Make them a champion; pay the spiff; give them admin-of-the-day visibility

How do you migrate a Salesforce instance from Classic to Lightning when half the AE team has 5 years of muscle memory in Classic?

The Detail

The 12-Week Plan

The Cutover Sequence

Vendors and Tools

Handling the Classic Loyalists

Hard Truths

Sources

What does the score mean?