Short answer
Moving from Salesforce Classic to Lightning Experience replaces the older interface with Lightning pages, components and modern features, and is required to use Agentforce, dynamic forms and most new Salesforce capabilities.
Why firms make this move
Some long-running orgs still have users or customizations tied to Classic, such as JavaScript buttons, Visualforce pages and old page layouts. A Lightning transition replaces these, redesigns pages around how people work, and retrains users.
What moves
- Page layouts as Lightning record pages
- JavaScript buttons as quick actions or flows
- Visualforce pages reviewed or rebuilt as Lightning components
- Reports and dashboards checked in Lightning
How the data maps
| From | To |
|---|---|
| JavaScript button | Quick action or screen flow |
| Visualforce page | Lightning web component or flow |
| Page layout | Lightning record page with dynamic forms |
What to watch out for
- Unsupported custom buttons
- Visualforce that does not render well
- User resistance without training
How Vantage Point runs the migration
- Readiness check
- Redesign key pages
- Rebuild incompatible customizations
- Pilot, train and switch
Typical timeline
Typically 3 to 8 weeks.
Frequently asked questions
Can we use Agentforce in Classic?
No. Agentforce and most new Salesforce features require Lightning Experience.
Do we need to rebuild Visualforce pages?
Some work in Lightning as is; others should be rebuilt for usability and support.