Key takeaways
- Salesforce delivers three major releases a year, named Spring, Summer and Winter, to every org automatically.
- Sandboxes can be upgraded early in a preview window, giving you time to test before production upgrades.
- Release Updates in Setup list changes that Salesforce will enforce on a schedule; review them every release.
- A short, repeatable routine turns releases from a risk into a source of free improvements.
One of Salesforce’s great strengths is that every customer gets new features automatically, three times a year. The flip side is that changes arrive whether you are ready or not. Most releases are smooth, but occasionally a change affects automation, integrations or user experience. A simple routine prevents surprises.
How the release cycle works
| Stage | What happens |
|---|---|
| Release notes and pre-release | Salesforce publishes release notes and opens pre-release orgs a few weeks before sandboxes upgrade |
| Sandbox preview | Sandboxes on preview instances upgrade several weeks before production |
| Production upgrade | Production orgs upgrade on scheduled weekends, by instance |
Check the Salesforce Trust site for your instance’s maintenance schedule, and the release readiness pages for preview dates. Whether a sandbox gets the preview depends on which instance it is on when the preview starts, so plan sandbox refreshes with this in mind.
A release routine that works
- Read the highlights. Skim the release notes for the clouds and features you use; note what could affect you and what could help.
- Check Release Updates. In Setup, review updates with upcoming enforcement dates, test them in a sandbox and activate them on your own schedule.
- Test in a preview sandbox. Run through key processes: lead to opportunity, case handling, approvals, integrations and important reports.
- Check custom code and integrations. Run Apex tests and confirm integrations still authenticate and sync.
- Plan quick wins. Pick a few new features that solve real user problems and schedule them.
- Tell users. Share a short note on visible changes and new features after the upgrade.
Release Updates deserve special attention
Release Updates, formerly called critical updates, are changes Salesforce will enforce by a specific release, often for security or platform reasons. Each one shows its enforcement date and a description. Activating them yourself in a sandbox first, then in production, is far better than having them enforced unexpectedly.
What to test every release
| Area | What to check |
|---|---|
| Automation | Key flows and triggers run as expected with realistic data |
| Integrations | Authentication, API calls and scheduled syncs succeed |
| User interface | Custom components, page layouts and Experience Cloud pages render correctly |
| Reports and dashboards | Critical reports return expected results |
| Security | Sharing and permissions behave as before |
Turning releases into value
Each release includes dozens of improvements, many requiring only a setting change. Teams that review releases regularly adopt useful features years earlier than those that do not, without paying for anything extra. Assign someone to own the release routine, and keep a running list of candidate features to adopt.
We include release reviews in our administration and support plans, so clients get the benefits without the surprises.
A one-page release plan
| When | Task | Owner |
|---|---|---|
| Release notes published | Skim highlights and list items that affect us | Salesforce admin |
| Before sandbox preview | Refresh a sandbox so it lands on the preview | Admin |
| Preview window | Regression test key processes and integrations | Admin and key users |
| Before production upgrade | Activate tested release updates; prepare user note | Admin |
| After upgrade | Smoke test, share changes and schedule quick wins | Admin and team leads |
Keeping the plan on one page, with owners and dates, makes it easy to repeat three times a year without it becoming a project.
Frequently asked questions
Can we delay a Salesforce release?
No. Releases are applied to all orgs on Salesforce’s schedule. You can prepare by testing in preview sandboxes and activating release updates early.
What are Release Updates?
Changes Salesforce will enforce by a stated date. Setup lists each one with details, so you can test and activate it before enforcement.
How do we get a sandbox on the preview?
Sandboxes on preview instances upgrade early. The release readiness guidance for each release explains which refresh dates place a sandbox on preview.
