Salesforce Lightning Consulting Services
Faster Lightning pages, and users who stop clicking back to Classic.
A Plan for Orgs Still on Classic and Orgs Already in Lightning
Your org may still hold Classic-era buttons, pages, packages and automation that nobody has reviewed for Lightning Experience. Moving them without a plan breaks daily work, slows pages and leaves users on their old habits. Salesforce Lightning consulting services give you that plan before the work starts and keep it current after launch.
If your org has not moved yet, our readiness checks and rollout paths come first, and they produce a dated plan for each user group. If users already work in Lightning but avoid it or wait on slow pages, the optimization and adoption work applies instead.
We handle both cases as advisory work with written deliverables, so your admins and developers can act on every finding. The sections below show what we deliver, which Salesforce dates affect your timing, how we scope an engagement and who works on it.
What Salesforce Lightning Consulting Services Include
The work has four parts. We inspect your Classic-era customizations, plan your Salesforce Classic to Lightning migration, design your pages in Lightning Experience and measure how many users stay on those pages after launch. The first two parts produce the inventory and the dated plan, and the last two measure and improve the result after every launch, so timing, risk and sequence drive the work.
98.1%
of orgs covered by Lightning Experience, says Salesforce
Jan 10, 2025
Salesforce retired its Lightning readiness apps
No date
announced by Salesforce for retiring Classic
3 a year
Salesforce releases, so Lightning changes land every few months and reviews repeat
VALiNTRY360 keeps advice and build as separate engagements. Build work, such as Lightning Web Components code, goes to our Salesforce Lightning development services team, and you can use either engagement alone. Many clients start with the assessment alone and decide on any build work later, once the written plan names exactly which Classic-era items need code.
Lightning Advisory Services We Deliver
Each service below can be ordered alone or in sequence, and each ends with a written deliverable.
Lightning readiness assessment.
We inspect buttons, pages, packages and automation in Classic, then list what breaks, what moves and what stays, with an owner for each item.
Salesforce Classic to Lightning migration planning.
We turn the assessment into a phased plan with user groups, dates, owners and a Classic switch-off point for each group.
Rollout path and sequencing.
We compare big bang, phased and new org paths, then choose the one that fits your user groups, your risk level and Salesforce’s three releases each year.
Salesforce Lightning customization review.
We check custom buttons, links, page layouts and Visualforce pages, then mark each one keep, rebuild or retire before building.
Lightning App Builder page design.
We design record, app and home pages with components and visibility rules matched to each role’s daily work, then hand them to your admins.
Automation retirement planning.
We map every Workflow Rule and Process Builder automation, then plan its move into Salesforce Flow automation in a safe order by object and by team.
Lightning Experience optimization.
We read page load data, find the slowest record pages, then cut or defer the heavy components that delay your users on every page they open.
Salesforce Lightning user adoption planning.
We set a usage baseline, name champions, then track each group until Lightning is the only experience you run in your org, group by group.
Most orgs begin with the first two services and add the rest as the plan firms up. Our Salesforce Lightning consulting services order the rest by what the assessment finds, so an org heavy in Visualforce adds the customization review next, and an org with slow pages adds optimization before adoption planning.
What Salesforce Has Retired or Changed, and What Still Works
We compiled this table from Salesforce’s Active and Past Product and Feature Retirements pages and its documentation, as of October 9, 2026. Every date comes from Salesforce, so you can check each one, and the table works as the starting list for a Lightning readiness assessment.
Item
Salesforce date
Status today
What it means for your org
Transition Assistant, Configuration Converter, Readiness Check
Retired January 10, 2025
Unusable on Spring ’25 orgs and later
Salesforce named no replacement, so a Lightning readiness assessment is now a manual review led by a consultant.
Optimizer app and Scale Center Insights
Optimizer retired June 1, 2026
Insights generally available since Spring ’26
Lightning Experience optimization now starts from Insights data and Experienced Page Time, on Enterprise, Professional, Unlimited and Signature.
Workflow Rules and Process Builder
End of support December 31, 2025
Past end of support as of today
Plan each automation’s move to Flow, since Salesforce no longer supports them, and test each in a sandbox before it reaches users.
Classic Knowledge data model
End of support March 1, 2026
Past end of support, with Lightning Knowledge as the path
Move to Lightning Knowledge in one direction only, after a test in a full-copy sandbox, and list every article type before you start.
Salesforce for Outlook and Lightning Sync
November 1, 2026 and April 1, 2027
Both on the Active retirements list
List who still uses each tool, starting with Salesforce for Outlook, which retires first, and plan replacements now.
Lightning Web Security and Locker
Default for orgs created in Winter ’23 and later
Generally available for all orgs since Summer ’23
Orgs on Locker get a sandbox test of Lightning Web Security before any production change, with each custom component retested.
SLDS 2 and the Cosmos theme
Introduced in Spring ’25
Opt in through the Cosmos theme, with no SLDS 1 end date
Components with component-level styling hooks stay on SLDS 1 for now, says Salesforce, so check yours first, before you turn the theme on.
Salesforce Classic user interface
No retirement date on the Active list
Available to users who hold the Lightning Experience permission
Users can still switch back to Classic, so you can plan the move without a forced deadline.
Aura components and Visualforce
No retirement notice on Salesforce’s lists
Salesforce recommends low-code tools and LWC over Visualforce
Working pages stay in place, and you rank rebuilds by user impact, with Aura moves optional.
Before each review, VALiNTRY360 checks these dates against Salesforce’s lists again, because Salesforce can shorten notice on a retirement. Any change goes into your next review, so the list you hold stays current.
Lightning Readiness Assessment Checklist
Each check below targets a Classic-era item that behaves differently in Lightning Experience or breaks outright. Our Salesforce Lightning consulting services run all ten before any Salesforce Classic to Lightning migration gets a date, because the retired Salesforce apps no longer scan your org for you, and no tool names the owner of each fix.
Check custom buttons and links with a JavaScript content source, which Lightning Experience does not support, and list each one.
Check profiles and permission sets for the Lightning Experience User permission, then list the users who still need it before cutover.
Check Visualforce pages, since the Lightning header and sidebar cannot be hidden and some list overrides become unreachable.
Check Classic apps still waiting for an upgrade to Lightning apps, because users cannot personalize navigation until then.
Check AppExchange packages without Lightning Ready certification, since their styling and function may fall short of Classic.
Check Classic Knowledge, because its change to Lightning Knowledge is one-way, and test the move in a full-copy sandbox.
Check Service Console use, where Salesforce’s own footnote says the Lightning console lacks full parity with the Classic console.
Check Shared Activities, which cannot be turned off once enabled, before anyone switches the feature on for your users.
Check hard-coded and instance URLs wherever your team has saved them, then replace each with a My Domain link before cutover.
Check heavy record pages that slow page time, then cut load with Lightning App Builder rules, a Lightning Experience optimization step.
Our Salesforce Health Check Services can run the first pass as a Mini-Scan. VALiNTRY360 then turns the findings into a dated plan, with a keep, rebuild or retire decision and a named owner for every item found.
Rollout Paths for a Salesforce Classic to Lightning Migration
Salesforce’s rollout guidance describes three paths for a Salesforce Classic to Lightning migration. Big bang suits lower-complexity orgs or a firm deadline, phased rollout by team is the most common choice for complex orgs, and a new org is the least common, kept for major business change. Salesforce also frames the work in three phases, shown below.
Discover
Learn the benefits and run your Lightning readiness assessment.
Plan the rollout, set each group’s schedule and align stakeholders.
Roll Out
Start change management and switch on Lightning-only features.
Adjust customizations, then launch to the first user group.
Optimize
Track adoption and iterate on feedback from each group.
Turn Classic off once usage data shows every group is settled.
Our Salesforce Lightning consulting services choose the path from your user groups, your volume of customization and your integrations. A new org also means moving records, which our Salesforce data migration team handles.
A champion in each group tests the default Lightning setup first, which gives Salesforce Lightning user adoption an early lead. A phased path lets each group move on its own date, so a problem found in one group does not hold up the others.
Salesforce Lightning Customization Through Lightning App Builder
Configure before you code. Lightning App Builder lets an admin shape pages without development, so most Salesforce Lightning customization starts there. Our consultant maps every page to a role before anyone builds it, because record pages then follow the user’s role, device and the data in the record.
• Page types.
Lightning App Builder creates App Pages, Home Pages and Record Pages from regions and templates. Home Pages exist in Lightning Experience only, so Classic users never see them, and each page type needs its own design decision.
• Dynamic Forms.
Fields and sections show or hide by record data, user details or device type. That cuts the page layouts you maintain for each object, so each role sees only the fields its work needs and admins edit one page instead of many.
• Dynamic Actions.
Introduced in Summer ’20, they give each action its own visibility rule, such as by profile or record data. Buttons then appear only for the users who need them, so a busy page shows each role its own actions.
• Console apps.
Console apps give service teams a three-column layout, multi-record view and split view lists. Agents work several records in one place, so we test service workflows with real users early and compare each one with the Classic console before launch.
Where configuration runs out, our Salesforce Lightning consulting services hand a documented brief to the Salesforce customization team, with every page decision already recorded for the developers.
How We Rank Classic-Era Customizations for Keep, Rebuild or Retire
Our Salesforce Lightning customization review ranks every Classic-era component by user impact before anything moves. Each gets a verdict of keep, rebuild or retire, with the reason written down for your team. Your Visualforce pages and Aura components get the same verdict, using the notes in the table above.
YOU HAVE
WE ADVISE
JavaScript buttons and links
Rebuild each as a Quick Action, a Flow or a Lightning component action, and start with the buttons your users click most often.
Page layouts for every profile
Merge them into fewer layouts and let Dynamic Forms handle the role differences, then retire any layout that no profile uses.
Apex classes and triggers
In our practice most stay in place, since they run on the platform, and only code that builds Classic-style URLs needs review.
Custom apps built for Classic
Upgrade each to a Lightning app, then design its navigation around the tasks that role performs each day in the org.
Packages with JavaScript buttons
Ask the vendor for a Lightning Ready version, and plan a replacement when none exists, before the Classic switch-off date.
Where a verdict says rebuild, our Salesforce Lightning consulting services set the order of work and name an owner for each rebuild, so nothing starts without a clear target and a test plan. Anything that stays in place gets a note on what to retest after each Salesforce release.
Lightning Experience Optimization and Salesforce Lightning User Adoption
Launch is the midpoint of the work and not the end, and Salesforce ships three releases a year, so both measures need regular checks. Lightning Experience optimization measures how fast pages load, and Salesforce Lightning user adoption measures who keeps using them.
Optimization
1.Measure Experienced Page Time first. Salesforce defines it as the time to download and display a whole page, and network, device, browser and setup all affect it.
2.Read Insights in Scale Center, which reports page time at the 75th percentile, separates first and later loads and flags pages with high component counts for review.
3.Trim load with dynamic visibility first, then lazy loading through tabs, Quick Actions and the utility bar, which create components when opened, so heavy parts load on demand.
Adoption
1.Set a usage baseline in the discover phase, then compare it with results in the optimize phase, so every group shows its own change over time.
2.Name a champion in each group and collect feedback from every group before you widen the rollout to the next set of users in the plan and the calendar.
3.Hide the option to switch back to Classic, then make Lightning Experience the org’s only experience once each group has settled in and usage holds.
Our Salesforce Lightning consulting services report both sets of numbers side by side, so slow pages and low usage get fixed in one plan. Lightning Experience optimization helps most when adoption data points to the pages people avoid.
Is Your Lightning Org Slow or Underused? Start With a Scan
Our Mini-Scan reviews your Lightning pages, code and automation, then ranks fixes by impact. Send us your org details and we will plan the scan with you.
Lightning Consultant vs. Developer vs. In-House Admin
These three roles work together, and each answers a different question. A consultant’s output, such as our Salesforce Growth & Efficiency Roadmap, tells developers and admins what to build and in which order. VALiNTRY360 supplies that direction alongside the people you already have.
Compare
• Consultant
• Developer
• In-house admin
Main question
Should we move, and in what order should we go?
What can we build, and how will it perform?
How do we keep the org running well each day?
Strongest at
Salesforce Lightning user adoption across groups
Custom components, integrations and tests
Users, permissions, reports and small changes
Typical output
Assessment findings, rollout plan, page designs
Working code, tests and release packages
Page tweaks in Lightning App Builder, reports
Where it stops
Code builds, tests and daily record upkeep
Ranking which work matters most to the business
Large plans that need extra hands or time
Best time to start
Before a move, or when adoption starts to stall
Once the plan names what needs custom code
Every day, from before launch to well after
Bring in the role that matches the next decision: a consultant for direction, a developer for code-level Salesforce Lightning customization and an admin for upkeep. Our Salesforce Lightning consulting services work beside your admin, and your developers can take our plan as their brief for the first sprint.
What Shapes the Cost of a Lightning Engagement
Salesforce publishes no consulting price ranges, so we scope each engagement from six drivers. The same drivers appear in Salesforce’s own guides, and they set the size of any Salesforce Classic to Lightning migration.
•Number of user groups and rollout phases, each with a plan
•Custom code and JavaScript buttons that need rebuilding
•Visualforce and Aura components that need a clear verdict
•AppExchange packages and integrations that must keep working
•Classic Knowledge, Service Console setup and data volume
•Training and change management across every user group
To scope an engagement we ask for four inputs: your edition, your number of user groups, your list of integrations and any open Classic-only customizations.
Our Salesforce Lightning consulting services scale from a Health Check Mini-Scan and its 90-Day Optimization Roadmap deliverable, through a scoped project, to ongoing support after launch. VALiNTRY360 sets the path with you once the drivers are known.
Salesforce Lightning customization and Salesforce Lightning user adoption work can sit inside any of the three. Ongoing support covers Lightning Experience optimization, release updates and adoption numbers, each reported in writing to your team.
Configuration-First Customization in Practice at Highmark Health
The Highmark Health project was a Sales Cloud implementation with custom Lightning Components, so its published figures describe that build alone. It shows how we apply configuration-first Salesforce Lightning customization when standard layouts run out.
CHALLENGE
Reviewing ideas at Highmark Health meant many steps, approvals and financial calculations across ideas from 35,000 employees, and every change to the review process needed a developer to build and test it.
APPROACH
VALiNTRY360 built on standard Sales Cloud objects, mapped each initiative to a Campaign and each idea to an Opportunity, and added custom Lightning Components for review flows that standard layouts could not hold.
OUTCOME
More than 300 executive-level users work in the platform, ideas from 35,000 employees sit in one database, and leadership gets a 360-degree view of every project status and financial projection, all in one place.
The lesson for your org is the order of work: configure first, then add code where standard layouts run out. Highmark’s reported result was lower complexity and an easier path to supporting the system, which is what configuration-first work aims for. Our Salesforce Lightning consulting services apply that order to your org, and the full Highmark Health case study shows the build in detail.
What Clients Say About Working With Us
Two clients describe how VALiNTRY360 weighs configuring against changing process, and how it teaches a team to carry the work on alone, both parts of every Salesforce Lightning customization we advise on.
Nathan Louque
Director of Global Sales Operation, Aviat Networks
“They ask the ‘why’ behind some of the requests we’ve made and help us to understand where to customize Salesforce and where to adjust our process.”
Lisa Hubbard
VP Sales and Marketing, The Vernon Company
“They really listen to your needs and take the time to help you learn and also gives you the foundation for continuous learning.”
Demetria Giles
@drosewritings
Playing around with @reflectnotes. I’m back logging key thoughts, details and soundbites from episodes, books, meetings, articles, etc from the past week. So far, it’s a knowledge worker’s dream come true.
Fabrizio Rinaldi
@linuz90
I’m keeping @reflectnotes open *all* the time, and I’m using both for simple journaling, and long form writing. It’s rare to see a single app work so well for both.
Jeremy McPeak
@jwmcpeak
I just received an invite to @reflectnotes, and holy crap! It is well thought out, and I can see this being my note- taking platform going forward. Well done! I’m looking forward to seeing how the app progresses.
Jonathan Simcoe
@jdsimcoe
All righty. I have to give a massive shout-out to @maccaw for pioneering @reflectnotes. It has already matured to a point where it is a daily driver for me. The speed, focus, and attention to detail (especially perfect bits of structured data) is superb.
More client results sit in our client case studies, each with the figures that client published, so you can read the detail behind these quotes.
Certified Professionals Working for You on Every Engagement
VALiNTRY360 staffs each engagement with a U.S.-based team that holds Salesforce certifications, and your scope sets the mix of roles. Our Salesforce Lightning consulting services team includes the four roles below.
Lightning consultant
Leads the assessment and rollout plan, then runs Salesforce Lightning user adoption reviews with each user group after launch.
Salesforce administrator
Builds pages in Lightning App Builder and keeps permissions, fields and reports in order for every role, so users find what they need.
Salesforce developer
Builds the Lightning Web Components and Apex that configuration cannot cover, and writes the tests that run before each release.
Delivery lead
Keeps dates, owners and stakeholders in step from kickoff until Classic is switched off for the last user group, and flags risk early.
You can meet the team behind the work on our About Us page, and ask which roles would join your project when you book a call.
Talk to a Lightning Consultant on Our Certified U.S. Team
Tell us where your org stands and what you want to change. A consultant will map your next step and name the people from our team who would join you.
A Salesforce Partner Since 2018
VALiNTRY360 is a Salesforce consulting partner based in Winter Park, Florida, and a Salesforce partner since 2018. We deliver implementation, customization and managed services, and our Salesforce Lightning consulting services sit inside that wider practice. Our consultants work across Sales Cloud, Service Cloud, Health Cloud, Marketing Cloud, Account Engagement and Experience Cloud projects.
To see the wider practice behind this work, explore VALiNTRY360’s full range of Salesforce consulting services.
Salesforce Lightning Consulting Services
FAQ by VALiNTRY 360
Salesforce Lightning is the current Salesforce user experience and component platform. It adds tools Classic lacks, such as Lightning App Builder pages, Dynamic Forms and Lightning Web Components, and pages built there also run in the Salesforce mobile app. The gap matters most where a customization in your org depends on Classic behavior.
New Salesforce capability ships in Lightning, so Classic falls further behind with each release. A Salesforce Classic to Lightning migration also retires workarounds such as JavaScript buttons, which Lightning Experience does not support, and moves your pages onto Dynamic Forms and Dynamic Actions, which let one page serve several roles in your org.
Salesforce has announced no retirement date for Classic, and it is absent from Salesforce's Active retirements list, updated September 16, 2026. Users with the Lightning Experience permission can still switch, and admins can turn Classic off. Check that list each release, because Salesforce posts new retirement notices there.
A Lightning consultant decides what to move, in what order and with whom. Through our Salesforce Lightning consulting services, the consultant inspects your org, writes the rollout plan, designs pages with your admins and tracks adoption. Developers then build whatever configuration cannot cover, working from the consultant's written brief.
Bring in a consultant before a move, when adoption stalls, or when pages load slowly and nobody owns the fix. Your admin keeps the org running each day, and a developer builds what the plan calls for. The consultant sets the direction and sequence for both, so effort goes to the highest-impact work first and nothing waits on a missing decision.
Run a Lightning readiness assessment. Salesforce retired its Transition Assistant, Configuration Converter and Readiness Check apps on January 10, 2025, so the review is now manual. It lists custom buttons, Visualforce pages, packages, Knowledge setup and automation, then marks each as keep, rebuild or retire with a named owner.
Salesforce frames a Salesforce Classic to Lightning migration in three phases: discover, roll out and optimize. You check readiness and plan, then adjust customizations and launch with change management, and finally track adoption before turning Classic off. Each phase ends with written findings, so the next group moves with fewer surprises.
The timeline depends on user groups, customization volume, integrations, packages and training. Salesforce publishes no standard duration, so any fixed number would be a guess. A Lightning readiness assessment produces the dated plan for your org, with a go-live date for each user group and a named owner for each step, all drawn from your own org.
Salesforce publishes no consulting price ranges, so cost follows scope. The main drivers are user groups, custom code, Visualforce and Aura components, packages, integrations, data volume and training. A Health Check Mini-Scan gives the smallest first step, and a scoped plan follows from its findings, with no figure guessed in advance.
JavaScript buttons and links stop working, because Lightning Experience does not support a JavaScript content source. Visualforce pages can behave differently, and AppExchange packages without Lightning Ready certification can look off. Workflow Rules and Process Builder automations should move to Flow, since support ended on December 31, 2025.
Salesforce's guidance says phased rollouts by team suit complex orgs, while big bang suits lower-complexity orgs or a firm milestone. Users can switch back to Classic during rollout, so launch need not wait for perfection. The pick follows from how your user groups differ in size, tools and tolerance for change, and we write the reason into your plan.
Set a usage baseline before launch, name a champion in each group, collect feedback and compare results after rollout. Then hide the option to switch back to Classic and make Lightning Experience the org's only experience. That sequence, group by group, is the core of Salesforce Lightning user adoption work, and each step has an owner.
Start with configuration: Lightning App Builder, Dynamic Forms and Flow. Salesforce says to choose Lightning Web Components over Aura unless a feature is unsupported. In our practice, Apex handles logic Flow cannot express, and Lightning Web Components handle interface needs that standard components cannot meet, while everything else stays in configuration.
Starter editions run Lightning Experience only, and in Essentials only System Administrators can switch to Classic. Personal, Contact Manager, Database.com and Chatter.com editions are unsupported in Lightning Experience, so check your edition in the Lightning readiness assessment before any plan gets dates or any user hears a launch date.
Track Experienced Page Time at the 75th percentile in Scale Center Insights as a Lightning Experience optimization baseline, plus usage by group and two or three process measures you already track. Salesforce publishes no productivity figure for this move that we could confirm for 2025 or 2026, so your own numbers are the benchmark.