Salesforce Lightning Experience is now the normal operating environment for most Salesforce organizations, but Salesforce Classic has not disappeared completely. Salesforce\u2019s 2026 help documentation still explains how eligible users can switch between Lightning Experience and Classic, while some editions and organizations are Lightning-only.<\/p>\n
That changes the migration question. In 2026, most teams are not deciding whether Lightning is the future. They are deciding whether any remaining Classic access still solves a real business requirement.<\/p>\n
Salesforce describes Lightning Experience as the current generation of the platform and states that new innovation is available there. That alone is a strong reason to design new workflows, automation, pages, and user experiences for Lightning rather than extending Classic.<\/p>\n
If a team is investing in new development while keeping users in Classic by default, it should be able to explain the specific constraint that justifies that choice.<\/p>\n
It is inaccurate to say Salesforce Classic was globally shut down. Current Salesforce help still documents the switcher, and administrators can allow or restrict access depending on edition and permissions.<\/p>\n
That means migration planning should be evidence-based. Inventory the users who still enter Classic and identify exactly which workflow, page, package, or habit sends them there.<\/p>\n
Salesforce retired Lightning Adoption apps\u2014including the Transition Assistant, Configuration Converter, and Readiness Check\u2014in January 2025. Salesforce cited 98.1% Lightning adoption across orgs when explaining the retirement.<\/p>\n
For organizations still completing the transition, the work is therefore less about a dedicated migration program and more about normal platform governance: dependency discovery, testing, user enablement, and removal of old access where it is no longer required.<\/p>\n
If a single Visualforce page, package, custom button, or administrative workflow is the only reason users switch interfaces, treat that dependency as a modernization backlog item. Measure how often it is used and whether a Lightning-compatible replacement exists.<\/p>\n
Flow, Lightning pages, component visibility, dynamic experiences, and modern platform capabilities are easier to design coherently when Lightning is the default environment. A mixed-interface operating model can make training and support more complex.<\/p>\n
If every procedure needs \u201cClassic\u201d and \u201cLightning\u201d instructions, the organization is paying an ongoing operating cost for the old interface. That cost appears in training, screenshots, testing, help-desk scripts, and user confusion.<\/p>\n
Interface differences can make troubleshooting harder. Standardizing the experience reduces the number of variables support teams need to consider when a page, permission, automation, or navigation flow behaves differently.<\/p>\n