The short version
- Per the published release calendar, Spring ’27 sandbox preview opens around January 9, 2027, with production release weekends on January 16, February 6, and February 20, 2027. Your exact date depends on your instance; Salesforce Trust is the authority.
- Release notes should land in mid-December 2026 if Salesforce follows its recent pattern (Winter ’27 notes published about three weeks before sandbox preview). That is an inference from the pattern, not a published date.
- The sandbox decision comes first: to test on Spring ’27 early, your sandbox must be on a preview instance before the preview window opens. Plan refreshes in December, not January.
- Headline features are unknowable until the notes drop; the safe expectation is continued Agentforce cadence on top of the platform changes. We will update this page when the notes publish.
- Winter ’27 set a precedent worth remembering for this cycle: defaults can change underneath you (Agentforce auto-enablement), so read the "changed defaults" sections of the notes first.
The Dates, First
Here is the Spring ’27 calendar as published, which is the thing most people searching for this page actually need:
- Sandbox preview: around January 9, 2027. Sandboxes on preview instances move to Spring ’27 then.
- Production release weekends: January 16, February 6, and February 20, 2027. Your org takes the release on one of the three, by instance.
- Your authoritative date: Salesforce Trust, search your instance, open the Maintenance tab. The calendar above is the published schedule; Trust is the contract.
Release notes have no announced date yet. The recent pattern, Winter ’27 notes published roughly three weeks before its sandbox preview, points to mid-December 2026. That is an inference from the pattern, flagged as such; this page gets updated the day the notes are live.
The December Decision That Makes January Easy
The one piece of Spring ’27 work that cannot wait for the release notes is the sandbox plan. Each cycle, sandbox instances split into preview and non-preview groups, and whether yours previews is determined by where it sits when the window opens. If regression testing on Spring ’27 matters to your team, December is when you refresh or create the sandboxes you want on preview instances; January 9 is too late to wish you had.
The checklist is short: pick which sandboxes should preview, check their instances against the preview list Salesforce publishes with the calendar, schedule refreshes for early December, and freeze risky sandbox work until they are back. Teams on our managed services get this handled as part of release readiness, three times a year, without thinking about it.
What We Know About the Contents (Honestly: Little)
Headline features are unknowable until the notes drop, and we will not pad this page with guesses dressed as predictions. Two things are worth saying now. First, the safe structural expectation is continued Agentforce cadence layered on the platform release, because that has been true of every release since the brand appeared. Second, Winter ’27 set a precedent that changes how you should read the notes: defaults can change underneath you. The Agentforce auto-enablement arrived as a changed default, not a feature you opted into, so when the Spring ’27 notes land, read the changed-defaults and release-update sections before the shiny-features sections.
When the notes publish in December, this page gets its update: the headline features, the changed defaults, and what is actually worth testing in the January preview window. If release weekends are the thing your team never has bandwidth for, that is literally a line item in our managed services, and a free call prices it.