Modern projects do not use Lightning Bolt. The work is either evaluating a legacy install or replacing it with current tools.
- Identify any Lightning Bolt installs
Setup, Installed Packages, look for packages with Lightning Bolt in the name or description. Note the version and the install date.
- Assess current usage
Verify the bolt-installed components are still in use. Many bolts were installed for a quick proof-of-concept and never fully adopted.
- Pick the modern replacement
Experience Cloud Templates for community sites, Industries Cloud (Financial Services, Health, etc.) for vertical solutions, custom build for unique requirements.
- Plan the migration
Map each bolt-provided component to a modern equivalent. Account for data migration, user re-training, and integration updates.
- Execute and uninstall
Roll out the modern replacement, validate functionality, uninstall the legacy bolt package. Audit downstream dependencies before uninstalling.
- Update documentation
Remove Lightning Bolt references from internal admin documentation. New admins should not have to learn a retired brand.
- Lightning Bolt packages no longer receive updates. Long-running orgs with bolt installs are accumulating tech debt.
- Custom code or data referencing bolt-provided objects may break on uninstall. Audit dependencies before pulling the trigger.
- The brand is effectively retired. Salesforce''s strategic direction is Experience Cloud Templates and Industries Cloud, not Lightning Bolt.
- Documentation drift is severe. Treat older articles about Lightning Bolt as historical context only.