Salesforce Release Freeze: Protect Your Go-Live Without Blocking the Business
A release freeze feels bureaucratic, until you skip it and a hotfix nukes go-live weekend. Here is the pragmatic freeze policy we apply on every Salesforce launch, with the exception process that keeps the business moving.
Release freezes feel bureaucratic, until the Friday before go-live, when a "quick change" from marketing takes down the lead capture Flow. A well-designed freeze is not about slowing the business down; it is about making the last two weeks predictable. Here is the pragmatic Salesforce release-freeze policy we apply on every launch, with the exception process that keeps urgent work moving without wrecking the launch.
What a Release Freeze Really Means
A freeze restricts what can be deployed to production during a defined window, typically the 7–14 days before and 3–7 days after a major go-live. It does not mean "no work." It means:
- No new features to production.
- No metadata changes without change-board approval.
- Only critical bug fixes and security patches ship.
- Sandbox refreshes are on hold.
- Data loads are batched, scheduled, and reviewed.
Why Freezes Fail (and Get a Bad Name)
Most freezes fail because they were announced too late, had no exception process, or were enforced by a single person who could be pressured. Result: everyone treats them as suggestions and the launch gets a hotfix at midnight.
The Freeze Playbook That Actually Works
- Announce four weeks out. Publish the freeze dates, the scope, and the exception process. Send it to sales ops, marketing, IT, and every admin with deploy access.
- Name a change-board of three. One from delivery, one from the business, one from IT security. Any exception needs two of three approvals.
- Publish the exception form. Ten fields max: what, why urgent, blast radius, rollback plan, tested where.
- Enforce with tooling. Use Gearset, Copado or Salesforce DevOps Center to lock deploys during the freeze window. Manual enforcement always leaks.
- Communicate every day. A 3-line daily update to the exec team: what shipped, what got refused, what is coming next.
What Should Ship Anyway
A freeze does not mean paralysis. These always ship, even mid-freeze:
- Security patches with a documented CVE or Salesforce advisory.
- Bug fixes that block business (login broken, quotes cannot generate).
- Legal or compliance changes with a deadline (a new consent field for GDPR).
- Data corrections that would compound if delayed.
Freeze Timing by Launch Type
| Launch type | Pre-freeze | Post-freeze |
|---|---|---|
| New Salesforce org / greenfield | 14 days | 7 days |
| Major new cloud (Service, Marketing, Data Cloud) | 10 days | 5 days |
| Major process rebuild (CPQ, quoting, forecasting) | 7 days | 3 days |
| New integration (ERP, marketing automation) | 5 days | 3 days |
| Salesforce major release (Spring/Summer/Winter) | 3 days | 2 days |
What the Freeze Enables Post-Launch
The best kept secret of a good freeze: it turns launch weekend from firefighting into observation. Because nothing changed for two weeks, any issue after go-live is traceable to the release itself, not to "well, marketing pushed a Flow yesterday." Root-cause analysis becomes surgical, not archaeological.
Regional Notes
- Europe: freeze windows should account for public holidays (France in August, Germany in December). See France, Germany, Belgium, Luxembourg, Switzerland.
- US & Canada: quarter-end and Black Friday create their own de-facto freezes. Sync with sales ops before locking. See US, Canada.
Frequently Asked Questions
How long should a Salesforce release freeze be?
7–14 days pre-launch, 3–7 days post-launch. Anything longer creates pent-up demand that snaps back the day the freeze ends.
What tools enforce a freeze?
Gearset, Copado, Salto or Salesforce DevOps Center all support deploy locks. Manual enforcement always leaks.
Can we freeze the whole org, or just the launched clouds?
Whole-org freezes are safer but face more pushback. Cloud-scoped freezes work if you can genuinely isolate changes.
Who owns the exception decision?
A change-board of three (delivery + business + IT security), majority rules. Never a single decision-maker under pressure.
Get a Freeze Policy Template
Our Salesforce launch playbook includes a fully-defensible freeze policy, exception form and change-board charter. Book a 30-minute call to get it configured for your next launch.
If this sounds like your CRM, let's look at it together.
Thirty minutes, no deck, no pitch. You leave with a diagnosis either way.