Salesforce releases three major platform updates per year – Spring, Summer, and Winter – plus occasional interim “patch” releases for critical fixes. Each release brings new features, changes to existing functionality, API version updates, and sometimes breaking changes that require admin action before the release window. Understanding how the release cadence works, how to prepare for each release, and how to stay current is a core Salesforce administrator competency. This guide explains the release process, how to use Sandboxes and the Salesforce Preview environment to test before production updates, and the most reliable ways to stay informed about what is changing.
That makes release planning part of the platform’s operating discipline.
Salesforce annual releases matter because each new release can change features, admin settings, and user workflows. Teams that rely on Salesforce need a way to prepare for those updates rather than discovering them after the rollout.
Salesforce’s Three-Release Annual Cadence
Salesforce delivers three major releases per year, roughly scheduled as:
- Spring Release: typically January–February. Generally available to most orgs by late February.
- Summer Release: typically May–June. Generally available by early June.
- Winter Release: typically September–October. Generally available by early October.
Each release is named with the season and year – e.g., Spring ’26, Summer ’26, Winter ’27. The naming uses the fiscal year in which the release occurs, which can be confusing: Winter ’27 is released in late 2026 (Salesforce’s fiscal year starts in February, so Winter ’27 is the first release of FY2027).
How Updates Reach Your Org
Salesforce manages the update deployment – customers do not “install” updates. Salesforce rolls out each release to different server instances in waves:
- Preview Sandboxes: developer sandboxes are updated first – typically 4–6 weeks before production goes live. This is the window admins use to test their org against the new release.
- Non-preview Sandboxes: most sandboxes update approximately 2–3 weeks before production.
- Production orgs: updated over several weekends in the release window. Salesforce sends email notification of the scheduled maintenance window for each production org.
The specific maintenance weekend for a given production org is visible in Setup → Company Information. Salesforce typically provides 2–3 weeks advance notice of the exact maintenance date.
Release Notes: What to Read and How
Each Salesforce release includes comprehensive release notes – the complete list of everything that changed. Release notes are available at help.salesforce.com as soon as the preview sandbox period begins. The notes are extensive (hundreds of pages), but admins do not need to read all of them. The most efficient approach:
- Use the “What’s New” summary: each set of release notes includes a high-level summary of the most significant changes. Start here.
- Filter by product area: Salesforce release notes are filterable by product (Sales Cloud, Service Cloud, Flow, Reports and Dashboards, etc.). Focus on the areas most relevant to your org.
- Look for “Requires Your Action” items: Salesforce flags changes that require admin intervention before or immediately after the release – these are the highest priority to review.
- Check “Critical Updates”: these are changes that Salesforce is making that could break existing behaviour – typically available as optional opt-in updates for a release or two before becoming mandatory.
Critical Updates and Auto-Activation
A Critical Update is a Salesforce change that may break existing functionality – a change to how formulas evaluate, a security policy change, an API behaviour change. Salesforce typically introduces Critical Updates as opt-in first (admin can enable or disable them in Setup → Critical Updates), then makes them mandatory in a future release. The Critical Updates screen (Setup → Critical Updates) shows all pending updates, their activation status, and the date they will be auto-activated.
The admin practice here: review Critical Updates at the beginning of every preview sandbox window, activate them in sandbox, test for any broken behaviour, then optionally activate in production before the auto-activation date – controlling the timing rather than having it forced on you.
Testing Releases in Sandbox: The Pre-Release Org
Beyond the preview sandbox period (where developer sandboxes receive the release 4–6 weeks before production), Salesforce also offers a Pre-Release Org – a completely separate, temporary org that runs the upcoming release before it is even available to preview sandboxes. Pre-Release Orgs are available through the Salesforce Pre-Release Programme, open to anyone who signs up at the pre-release programme URL (publicised in the Salesforce community before each release).
The Pre-Release Org is a developer org populated with Salesforce’s demo data – not the admin’s production data. Its value is exploring new features 6–8 weeks before the production update, providing feedback to Salesforce, and planning org-specific configuration changes well in advance.
Staying Current Between Releases
The Salesforce release cadence means something is always changing. Resources to stay current:
- Salesforce Release Notes: published at the beginning of each preview sandbox period. Bookmark and review at the start of each release cycle.
- Salesforce Ben (salesforceben.com): independent Salesforce news and feature summaries – publishes accessible summaries of each release that are faster to read than the full release notes
- Trailhead Release Notes Trail: Salesforce publishes a Trailhead learning module for every major release summarising key changes – accessible via the Trailhead platform
- Salesforce Help Status Page: status.salesforce.com – tracks known issues and scheduled maintenance
- Admin.salesforce.com blog: Salesforce’s official admin blog publishes release highlights targeted specifically at administrators
- Salesforce Community Groups: local Salesforce User Groups and the Admin Community (Success Community) are active before each release with peer discussion of feature impacts
- Salesforce Trailblazer Community (Dreamforce and TrailheaDX): annual conferences where upcoming features are previewed – keynotes are streamed live and recorded
The Pre-Release Checklist for Admins
A simple pre-release checklist for each Salesforce release:
- Review the “What’s New” summary in the release notes (30 minutes)
- Check Critical Updates – activate all in sandbox, note the auto-activation dates for production
- Identify any changes that affect your org’s current configuration (check reports, flows, validation rules, integrations if API version changes apply)
- Communicate relevant feature changes to end users – highlight new features they can use, warn about any UI changes
- Update your release notes documentation (most orgs maintain a change log of what release changes were relevant)
Is Salesforce easy to learn for beginners?
Salesforce has a learning curve, but its official free training platform Salesforce Trailhead provides structured paths from beginner to advanced. Most users handle day-to-day tasks within 2-4 weeks. Admin and developer skills take 3-6 months to develop proficiently.
What are the biggest Salesforce mistakes to avoid?
The most common mistakes are over-customizing before you understand your process, skipping user training, importing dirty data without cleansing it first, and not establishing naming conventions. Avoid those four and your implementation will be far more successful.
How often does Salesforce release new features?
Salesforce releases major updates three times per year in Spring, Summer, and Winter releases. Features are previewed in sandbox environments 4-6 weeks before each release so admins can test before go-live.
Does Salesforce offer customer support?
Yes. Support is available via chat, email, and phone depending on your plan tier. Enterprise plans include dedicated customer success managers. The Salesforce Trailblazer Community also provides extensive peer and official support.
Can Salesforce integrate with other business tools?
Yes. Salesforce AppExchange offers 7,000+ apps. Common integrations include Slack, DocuSign, Zoom, and ERP systems via MuleSoft.
The best release process is the one that turns change into a checklist. If the team waits until after the release, it becomes harder to control the impact.
Common Problems and Fixes
Problem: Getting Your Team to Consistently Use Salesforce
Adoption gaps occur when teams revert to old habits after initial training. Fix: Identify the 2-3 daily workflows where Salesforce adds the most value for your specific role. Focus training on those workflows first. Use Salesforce in-app guidance to provide contextual help at the moment of need, rather than relying solely on one-time classroom sessions.
Problem: CRM Data Quality Degrading Over Time
CRM data decays at approximately 30% per year as contacts change roles and companies. Fix: Schedule a quarterly data quality audit. Use Salesforce deduplication tools to merge duplicate records. Establish data entry standards enforced through validation rules. Consider a data enrichment tool like Clearbit or ZoomInfo to update stale records automatically.
Problem: Salesforce Reports Not Matching Actual Business Results
Reports are only as accurate as the data entered. Discrepancies between CRM reports and actual revenue point to data entry gaps. Fix: Audit closed-won records against actual invoices monthly. Make CRM data the source of truth for commission calculations so reps have a direct incentive to enter accurate data.