Migration strategy, historical data scope and go-live cutover
Key Takeaway
Match the migration strategy to the company's readiness for change, and decide each data category by whether future business events or reporting depend on it.
A migration strategy decides how much of a legacy system's configuration and data moves into the new Salesforce solution, how much gets redesigned, and how the business switches over at go-live. Every choice trades speed and low disruption against a cleaner design and fuller use of new capabilities. Cutover planning then turns the strategy into a go-live with clear checks, support, and a defined way to roll back.
Migration strategies
Migration strategies sit on a scale from copying the old system as-is to building fresh. For example, a move from Salesforce CPQ to Revenue Management can follow one of four strategies. Each one strikes a different balance between speed, business disruption, and access to the new product's capabilities. Choosing early shapes the scope of the data migration effort.
Full Migration and Reimagine are the two ends of the scale. Partial Migration and Full Rationalization sit between them.
| What it does | What you get | What it costs | |
|---|---|---|---|
| Full Migration (lift and shift) | Moves existing configuration and data with minimal redesign, aiming for functional parity as fast as possible | The fastest path with the least business disruption | Unlocks only some new capabilities, and replicating old logic can introduce technical debt |
| Partial Migration | Reimplements the high-value areas, moves the rest unchanged, and rationalizes it in later phases | Manageable risk | Hidden cost: migrated legacy data and rationalized data must be reconciled with each other |
| Full Rationalization | Redesigns the catalog and pricing | The full value of the new product | The most upfront design investment and the broadest impact on current business processes |
| Reimagine (greenfield) | Redesigns business processes first, configures the new system for the future-state design, and migrates no legacy data | Maximum design freedom | Significant reimplementation, user retraining, and two systems running in parallel during the transition |
With Reimagine, the legacy data becomes a historical reference. That data stays accessible in the old system during a wind-down period.