Salesforce migration without the six-month freeze
A Salesforce migration need not freeze the roadmap. Move one capability at a time, dual-run each slice and map integrations early so delivery carries on.
By Arpan Jain, Chief Executive OfficerUpdated November 8, 2026Salesforce, Migration, Enterprise Commerce, Delivery
On most platform migrations, the platform is a smaller cost than the wait. The roadmap sits frozen for two quarters “until we’re on the new system”, and the business loses everything it could have shipped in that time.
Most teams accept the freeze as the price of moving, but it usually comes from the plan. When the migration is one atomic cutover, nothing can change until it lands. Split it into steps that can each be reversed and the roadmap can keep moving.
Why the freeze happens
A big-bang migration puts everything on a single date. Data, integrations, customizations, permissions and the way people work all have to be right at once. Because that date carries so much risk, teams stop changing the old system months ahead so the target holds still. The freeze comes from that single-date shape, so a plan with a different shape avoids most of it.
Sequence by capability
The usual instinct is to move the data model first and the features after it. That stretches out the period in which neither system can do the whole job.
Moving one capability at a time lets each slice go live on its own and pay for itself. Order management might move first, then service, then commerce. Each is a genuine cutover with a genuine rollback, and the business keeps releasing in between.
The price is a stretch of dual-running. Teams push back on it because it feels untidy, yet running two systems side by side for a while costs far less than a roadmap that stands still for half a year.
Decide what not to bring
A migration is a chance to stop carrying things. Most orgs are about to move customizations built around a constraint that has since disappeared, along with reports nobody has opened in two years.
Classify everything before it moves: carry, rebuild or retire. If no named owner can explain why something exists, it is a candidate for retirement. Done honestly, this pass takes real scope off the plan, and anything you take off can no longer run late.
Integrations set the critical path
Data moves in a handful of planned loads, while integrations have to keep running through every state in between.
List every inbound and outbound integration before you settle the cutover order. For each one, decide whether it points at the old system, the new one or both while its slice is dual-running. Integrations found halfway through are the usual cause of an unplanned freeze, because nobody knows they exist until something downstream breaks.
Rehearse each slice’s data loads and integration switches in a Full sandbox before production. Salesforce lets you refresh a Full sandbox only once every 29 days, so put those refreshes in the plan early.
Keep a delivery team on the roadmap
When one group of engineers owns both the migration and the roadmap, the migration wins every week and roadmap work stops. Dedicated capacity fixes that.
A separate delivery team, embedded with yours or working from a dedicated Global Capability Center, keeps migration pressure off product capacity. During a replatforming, protecting the roadmap from a temporary program is a stronger case for extended teams than cost.
When Cube27 set up an operations center for a commerce and technology partner, the partner kept its own people on technology and product while the center took on operations and platform integrations. Attrition there stayed under 10%. On a migration, that kind of retention means the person who mapped your integration edge cases in month one is still on the team at cutover.
A working sequence
- Inventory everything and classify it: carry, rebuild or retire
- Map every integration and set its state for each cutover
- Slice by capability, then order the slices by risk and dependency
- Dual-run each slice with a rollback agreed in advance
- Switch off the old path only when the new one has carried a complete business cycle, month-end close included
A big-bang cutover looks shorter on a project plan. This sequence usually finishes sooner in practice, because the rest of the organization keeps working while it runs.
Cube27 runs Salesforce migrations alongside dedicated delivery teams through Salesforce & enterprise platforms. Talk to a Solutions Architect about your migration.