Salesforce Classic is on borrowed time. Migrating to Lightning Experience isn't optional — it's a competitive necessity. But rushing in without a solid salesforce lightning migration checklist is how orgs lose data, break workflows, and frustrate their teams. RASPSYS has run this process dozens of times. Here's the exact checklist we use.
1. Org Assessment & Readiness Audit
Before a single setting is changed, RASPSYS conducts a full org health check. This means running Salesforce's built-in Lightning Experience Readiness Report and going beyond it — cataloguing every custom component, Visualforce page, S-Control, and API integration that could break in Lightning.
Pay close attention to browser-based JavaScript overrides and inline-editing patterns that behave differently in the Lightning DOM. These are the silent killers of a migration gone wrong.
- Run the Lightning Experience Readiness Check in Setup
- Catalogue all Visualforce pages and Classic-only features
- Identify active API integrations and their Lightning compatibility
- Map all custom buttons, links, and JavaScript actions
- Flag any third-party AppExchange packages needing Lightning versions
Get a free org readiness assessment from RASPSYS →
2. Feature Parity & Customisation Review
Not everything in Classic translates one-to-one into Lightning. Some features have better Lightning equivalents. Others require a full rebuild. RASPSYS maps every Classic customisation to its Lightning counterpart — and flags the gaps before they become production incidents.
This step protects your revenue-critical workflows. Neglect it, and your sales team will spend their first week in Lightning hunting for functionality that simply isn't there yet.
- Convert Visualforce pages to Lightning Web Components where needed
- Rebuild Classic dashboards as Lightning dashboards
- Audit list views, related lists, and record detail layouts
- Review Workflow Rules and migrate to Flow where applicable
- Validate email templates and merge fields for Lightning compatibility
See how RASPSYS rebuilds Classic customisations for Lightning →
Let RASPSYS Handle Your Entire Lightning Migration
From org assessment to post-go-live support, RASPSYS delivers end-to-end Salesforce Lightning migrations with zero disruption to your business. Teams in the UK, US, UAE, Canada, and Australia trust us to get it right the first time.
3. User Readiness & Change Management
Technology is only half the challenge. The bigger risk is adoption. Users who aren't prepared for Lightning's new interface will revert to Classic the moment they hit friction — and that sets your migration back by months.
RASPSYS builds a structured change management plan into every migration engagement. This includes role-based training, early champion identification, and a feedback loop to surface issues before they become complaints.
- Identify power users and Lightning champions in each department
- Create role-based training paths using Trailhead and in-house guides
- Set up a feedback channel for the first 30 days post-launch
- Communicate the migration timeline across all stakeholders early
- Plan a phased rollout by team or profile — not a hard cutover for all
Explore RASPSYS change management support for Lightning →
4. Testing & Sandbox Validation
No Lightning migration should ever go live without thorough sandbox testing. RASPSYS runs a full regression suite in a full sandbox environment that mirrors production — every integration, every automation, every user profile tested against real scenarios.
User Acceptance Testing (UAT) is non-negotiable. Get sign-off from department leads before you cut over. One missed edge case in a CPQ flow or approval process can cost you days of firefighting post-launch.
- Refresh a full sandbox copy from production before testing begins
- Test all Flows, Process Builders, and Apex triggers end-to-end
- Validate all third-party integrations in the Lightning context
- Run UAT with real users from each affected team
- Document and resolve all critical and high-priority defects before go-live
- Obtain formal sign-off from department leads before cutover
Learn how RASPSYS manages Lightning sandbox testing →
5. Go-Live Preparation & Cutover Plan
Go-live day is not the finish line — it's the starting pistol. A well-structured cutover plan defines exactly who does what, in what order, and what the rollback procedure looks like if something goes wrong. RASPSYS builds a detailed runbook for every migration we deliver.
Schedule your cutover during a low-traffic window. Have a dedicated RASPSYS engineer on standby for the first 48 hours. Monitor user adoption metrics and system logs in real time — and keep Classic temporarily accessible as a safety net while confidence builds.
- Define a cutover runbook with step-by-step owner assignments
- Schedule go-live during a weekend or low-traffic period
- Keep Classic temporarily accessible via profile permissions during transition
- Set up real-time monitoring for errors, login failures, and integration alerts
- Plan a hypercare support period of at least 2 weeks post-launch
If any item on this checklist feels uncertain, that uncertainty is a risk. RASPSYS eliminates the guesswork — we own the entire process so your team can stay focused on business as usual.
Get RASPSYS to plan and execute your Lightning go-live →
Ready to Move to Lightning? RASPSYS Will Take It From Here.
RASPSYS delivers complete, risk-managed Salesforce Lightning migrations for businesses across the UK, US, UAE, Canada, and Australia. Don't let a complex migration stall your growth — book your free consultation today and get a clear plan in 48 hours.