Salesforce Classic to Lightning migration means moving your org from the older tab-based Classic UI to Lightning Experience — Salesforce's modern, component-driven platform. It's not just a cosmetic change. Since 2020, Salesforce has shipped every new feature — Agentforce, Einstein Copilot, Dynamic Forms, the redesigned Setup — exclusively to Lightning. Classic? It gets security patches and nothing else.
Here's the bottom line: over 80% of Salesforce customers already run Lightning as their primary interface. The remaining 20% face a widening gap every quarter. If your team still opens Classic each morning, this guide walks you through the exact steps, timelines, and costs to make the switch without disrupting your daily operations.
Salesforce Lightning Experience (LEX) is the modern, component-based interface that replaced Salesforce Classic as the default CRM experience. Launched in 2015, Lightning was built from the ground up to be faster, more visual, and easier to customize than Classic.
What makes it different under the hood? Lightning runs on the Lightning Component Framework — think of it as a library of reusable UI building blocks. Your admin picks components from a palette, drops them onto a page canvas, arranges them, and hits save. No Apex. No Visualforce. That's how the Lightning App Builder works, and it's why teams can redesign record pages in an afternoon instead of a sprint.
And here's what really matters: Lightning is the only platform where Salesforce ships new capabilities. Agentforce AI agents, Einstein Copilot, Dynamic Forms, the redesigned Flow Builder, interactive dashboards — none of these exist in Classic. If you're still on Classic, you're locked out of every innovation Salesforce has released since 2020.
Before diving into migration, it helps to understand exactly what changes. Here's a side-by-side comparison:
| Feature | Salesforce Classic | Salesforce Lightning |
|---|---|---|
| User Interface | Text-heavy, tab-based navigation | Modern, app-based with visual cards and components |
| Page Customization | Limited layout editor, requires code for complex changes | Drag-and-drop Lightning App Builder, Dynamic Forms |
| AI Capabilities | None | Einstein Copilot, Agentforce, predictive lead scoring |
| Mobile Experience | Basic, not optimized | Responsive, mobile-first design |
| Dashboards | Static, limited to 3 columns | Interactive, real-time filters, up to 12 components |
| Automation | Workflow Rules, Process Builder (retiring) | Flow Builder with screen flows, auto-launched flows, and orchestrations |
| New Feature Updates | No new features since 2020 | Three major releases per year (Spring, Summer, Winter) |
| Kanban Views | Not available | Built-in for opportunities and custom objects |
| Path & Guidance | Not available | Visual sales path with coaching tips per stage |
| Component Framework | Visualforce (legacy) | Lightning Web Components (LWC) — faster, standards-based |
The gap between these two experiences widens with every Salesforce release. In our experience working across 75+ Salesforce projects, organizations that delay migration end up spending more on custom workarounds to replicate features that come built-in with Lightning.
You might wonder: if Classic still works, why rush? Here are five concrete reasons that make 2026 a critical year to move:
1. Salesforce Classic receives zero new features. Every enhancement — from Agentforce to the redesigned Setup experience — is Lightning-only. The feature gap is no longer small; it's a chasm that grows three times a year with each seasonal release.
2. Process Builder and Workflow Rules are being retired. Salesforce is actively sunsetting Classic-era automation tools in favor of Flow Builder. Organizations still running Workflow Rules will need to migrate those automations regardless — doing it alongside a Lightning migration makes more sense than doing it twice.
3. AI capabilities require Lightning. Einstein Copilot, Agentforce autonomous agents, and predictive analytics all need Lightning Experience. If your 2026 roadmap includes any AI initiatives on Salesforce, Classic is a dead end.
4. User productivity jumps measurably. Salesforce's own research shows Lightning users are 25% more productive than Classic users, and sales reps save an average of 5-10 hours per week. We've seen similar results across our Salesforce consulting engagements — one manufacturing client cut their quote generation time by 40% after migrating to Lightning.
5. Security and compliance updates favor Lightning. Salesforce Trust Layer, enhanced field-level security, and modern authentication flows are designed for Lightning. Classic orgs may face compliance gaps as regulations tighten.
Before you touch anything, run the Lightning Experience Readiness Check directly inside your Salesforce org. This is a free, built-in tool that Salesforce provides to assess your org's migration readiness.
Here's how to access it:
The readiness report covers several areas. It evaluates your Visualforce pages and flags which ones need updates for Lightning compatibility. It checks your custom JavaScript buttons — these won't work in Lightning and need to be replaced with Quick Actions or Lightning Web Components. It reviews your AppExchange packages and tells you which ones already support Lightning and which don't.
What the readiness check won't tell you is how your users actually work day-to-day. That's why we recommend pairing it with user workflow interviews. Sit down with 2-3 power users from each department and map out their top 10 daily tasks. This gives you a realistic picture of what needs to work flawlessly on day one.
Here's the step-by-step process we've refined across dozens of Salesforce implementation projects:
Start with a thorough inventory of your Salesforce org. Document everything that's currently in use:
This inventory becomes your migration blueprint. Tag each item as "Lightning-ready," "needs modification," or "needs replacement." In our experience, roughly 70-80% of a typical org's configuration works as-is in Lightning. It's the remaining 20-30% that needs focused attention.
With your audit complete, create a phased migration plan. Decide between two approaches:
Big Bang — Migrate everyone at once. Works well for smaller orgs (under 100 users) with minimal customizations. Simpler to manage but higher risk if something goes wrong.
Phased Rollout — Migrate department by department. Better for larger orgs or those with heavy customizations. Lets you learn from each phase and fix issues before the next group moves over. This is the approach we typically recommend.
Your roadmap should include clear milestones, assigned owners for each task, a sandbox testing schedule, user training dates, and a rollback plan (more on that later).
Never migrate directly in production. Always start in a full-copy sandbox that mirrors your live org.
In the sandbox, rebuild or update the items you tagged as "needs modification." Replace JavaScript buttons with Lightning Quick Actions. Convert Visualforce pages to Lightning Web Components where needed. Migrate Workflow Rules and Process Builders to Flow Builder — Salesforce's Migrate to Flow tool can automate much of this.
Build out your Lightning page layouts using the Lightning App Builder. This is where you can go beyond just replicating Classic — design pages that actually make your users' jobs easier. Add related lists, path components, and Einstein insights directly on record pages.
Bring in your power users — the ones you interviewed during the readiness assessment. Have them test their top 10 daily workflows in the sandbox. Key areas to validate:
Document every issue, categorize by severity, and fix critical items before moving forward. Don't skip this step. What works in theory often breaks in practice when real users follow their actual workflows.
Training makes or breaks adoption. As Salesforce community experts consistently emphasize, we've seen technically flawless migrations fail because users weren't prepared for the new interface.
Structure your training by role. Sales reps need to know where their pipeline views and activity timelines moved. Managers need dashboard and reporting training. Admins need Lightning App Builder and Flow Builder deep-dives.
Practical tips that actually work: record short (2-3 minute) screen-capture videos showing how to do the 5 most common tasks in Lightning. Pin these in your company's Slack channel or intranet. Assign "Lightning Champions" in each team — people who get early access and become the go-to resource for their peers.
If you're doing a phased rollout, start with a pilot group of 10-20 users who are tech-comfortable and patient with bugs. Enable Lightning Experience for this group through their profiles in Setup.
During the pilot period (1-2 weeks), closely monitor:
Fix the issues the pilot group surfaces, then roll out to the next department. Repeat until all users are on Lightning.
For a big bang approach, pick a weekend or low-activity period. Enable Lightning for all users at once, and have your admin team on standby for the first 48 hours.
Migration isn't a one-time event — it's the start of an optimization cycle. After the initial rollout:
The honest answer: it depends on your org's complexity. But here are realistic ranges based on what we've seen across our Salesforce professional services engagements:
| Org Size | Customization Level | Estimated Timeline |
|---|---|---|
| Small (under 50 users) | Minimal — mostly standard objects | 4-6 weeks |
| Medium (50-200 users) | Moderate — some custom objects, a few integrations | 8-12 weeks |
| Large (200-1,000 users) | Heavy — many custom objects, multiple integrations, Visualforce pages | 3-6 months |
| Enterprise (1,000+ users) | Complex — multi-org, global teams, dozens of integrations | 6-12 months |
These timelines include planning, testing, training, and phased rollout. The biggest variable isn't technical complexity — it's change management. Getting 500 users comfortable with a new interface takes longer than converting 50 Visualforce pages.
Migration costs vary widely, but here's a framework to estimate yours:
Internal migration (small to medium orgs): If you have a skilled Salesforce admin or a small internal team, a straightforward migration might cost only the time investment — roughly 100-300 hours of admin and developer time. For a mid-size org, that translates to $15,000-$50,000 in internal labor costs.
Partner-assisted migration (medium to large orgs): Working with a certified Salesforce partner typically costs between $50,000 and $200,000 depending on org complexity, number of integrations, and the level of customization involved.
Enterprise migration: Large-scale migrations with multiple orgs, global teams, and complex integrations can run $200,000 to $500,000+ when accounting for consulting, development, training, and change management.
Hidden costs to budget for: AppExchange package upgrades (some vendors charge for Lightning-compatible versions), extended sandbox licenses for testing, and productivity dip during the first 2-4 weeks as users adjust.
After helping organizations across manufacturing, BFSI, real estate, and healthcare navigate this transition, here are the challenges we see most often:
JavaScript buttons breaking in Lightning. Classic relied heavily on JavaScript buttons for custom actions. Lightning doesn't support them. The fix: replace them with Quick Actions, Lightning Web Components, or Flow-triggered actions. Start cataloging your JS buttons early — this is usually the most time-consuming migration task.
Visualforce pages not rendering correctly. Most Visualforce pages work in Lightning using the built-in iframe wrapper, but the styling often looks off. For critical pages, consider rebuilding them as Lightning Web Components. For lower-priority pages, the Visualforce wrapper is a fine interim solution.
User resistance to change. This is the #1 challenge, and it's not technical. People are comfortable with Classic because they've used it for years. Combat this with early communication (explain the "why"), role-specific training, and visible executive sponsorship. When your VP of Sales uses Lightning in their pipeline review meeting, it sends a stronger message than any training session.
Third-party integrations failing. Check every integration before migration. Some older AppExchange packages need updates for Lightning compatibility. Contact vendors early — some offer free Lightning-ready upgrades, while others require a paid update. For custom Salesforce integrations, verify that API callouts and connected apps still function in the Lightning context.
Reports and dashboards looking different. Lightning dashboards are more powerful but work differently. Classic dashboard components don't always translate perfectly. Plan to rebuild your top 10-15 dashboards natively in Lightning — the interactive filters and dynamic components make them far more useful anyway.
Don't declare victory on day one. Use this checklist over the first 30-60 days after migration:
If users are switching back to Classic frequently, that's a signal. Find out why. Usually it's one or two specific tasks that feel harder in Lightning — fix those, and adoption follows.
This depends on three factors:
Your internal Salesforce expertise. If you have a certified Salesforce admin and a developer who know your org inside-out, a straightforward migration is manageable in-house. If your admin is a one-person team juggling daily support requests, they likely don't have the bandwidth for a migration project.
Your org's complexity. The more custom objects, Visualforce pages, integrations, and user roles you have, the stronger the case for bringing in a partner. A partner has done this dozens of times and knows exactly where the landmines are.
Your timeline. If leadership wants migration done in 8 weeks and your org has 500 users with 30 integrations, you need external help. Period.
A good Salesforce partner doesn't just handle the technical migration — they bring change management expertise, training programs, and post-migration support. At Minuscule Technologies, our approach to Lightning migration includes a full org audit, phased rollout planning, custom LWC development for complex pages, user training, and 90-day post-migration support. With 160+ Salesforce experts and experience across industries like automotive, BFSI, and real estate, we've refined a process that minimizes disruption and maximizes adoption.
Salesforce hasn't announced an official end-of-life date for Classic. However, Classic has received no new features since 2020, and Salesforce auto-enables Lightning for all new orgs. The practical reality is that Classic is in maintenance mode — it works, but it's falling further behind with every release.
Yes. Salesforce lets users toggle between Classic and Lightning during the transition period. This is useful for the rollout phase, but don't treat it as a permanent solution. The goal should be full Lightning adoption within 30-60 days of enabling it for each user group.
No. Your data — records, attachments, files, and custom fields — stays exactly where it is. Migration affects the user interface and how you interact with your data, not the data itself. That said, page layouts, dashboards, and some automations may need reconfiguration.
Most Visualforce pages work in Lightning through an iframe container. They won't look native, but they'll function. For customer-facing pages or heavily-used internal pages, consider migrating them to Lightning Web Components for a better experience.
Make Classic less convenient and Lightning more valuable. Remove the option to switch back to Classic after the transition period. Add Lightning-exclusive features to their daily workflows — things like the activity timeline, path guidance, and Kanban views that genuinely save time. Celebrate teams with high Lightning adoption rates.
Based on Salesforce's published data: 25% productivity increase, 5-10 hours saved per rep per week, and access to AI features that can improve lead conversion by up to 30%. In practice, the ROI depends on how well you customize Lightning for your specific workflows. A well-executed migration pays for itself within 6-12 months through productivity gains alone.
Salesforce Classic to Lightning migration is no longer a "nice to have" — it's a business-critical initiative. Every quarter you wait, the feature gap widens, the technical debt grows, and the eventual migration becomes more complex.
Here's how to start today:
If you need a Salesforce engineering partner to guide your migration, Minuscule Technologies brings deep migration experience across industries. We've helped organizations of all sizes — from 50-user teams to Nasdaq-listed enterprises — make the move to Lightning without disrupting daily operations. Book a free consultation to get a tailored migration assessment for your org.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
