Phased, pilot and big bang rollout approaches at go-live
Key Takeaway
Fit the rollout to how the business is divided. A representative pilot proves a shared configuration before everyone moves. Regions or legal entities with distinct pricing, tax, or fulfillment requirements each go live as their own cohort.
A rollout approach decides who starts using a new Salesforce solution at go-live, and in what order. Big bang moves every affected user at once. Pilot-first moves a representative group first. A phased (staggered) rollout moves users in stages. A cohort-based rollout takes each defined cohort of the business through its own go-live. No single approach is always correct, because the right one depends on the company's size, complexity, risk tolerance, and migration strategy.
Big bang rollout
In a big bang rollout, all in-scope capabilities go live at the same time for all affected users, in a single maintenance window. No two systems run side by side at any point.
When a big bang succeeds, it gives the cleanest result. There is one system and one data model, and there is no doubt about where to create records.
Rollback planning is critical for a big bang. Define and test the rollback procedure before committing to the cutover. Run multiple dry-run cutovers in a sandbox so the team can practice the sequence before the production go-live.