<!-- Migration plan · from Chapter 30 of The Product 360 Handbook -->

# Migration plan · [From offering] to [successor] · [Date]

**Owner:** [PM]   **Engineering lead:** [name]   **Customer success lead:** [name]

## Segments
| Segment | Accounts | ARR | Migration complexity (L/M/H) | Approach (self-serve / assisted / white-glove) | Wave |
|---|---|---|---|---|---|
| | | | | | |

## Feature parity map
| Old capability | New equivalent | Gap | Workaround or plan | Accounts relying on it |
|---|---|---|---|---|
| | | | | |

## Tooling
- Configuration or rule import:
- Data migration and export:
- Parallel run: [how long, what customers compare, how to revert]

## Success criteria per account
[e.g., parallel run complete, key metric within x% of old system, customer sign-off]

## Incentives
[Credits, price lock, free services, and their deadlines]

## Support staffing curve
| Period | Expected migrations | Support and services capacity needed |
|---|---|---|
| | | |

## Tracking
| Account | ARR | Wave | Status (not started / parallel run / migrated / blocked) | Blocker | Owner | Next step |
|---|---|---|---|---|---|---|
| | | | | | | |

## After migration
Check-ins at [30 and 60] days. Watch: [usage, satisfaction, key outcome metric].

## Escalation path
Blocker owner → [PM] → [decision owner], with a response time of [n] business days.
