Migration Plan
Plan a safe technical migration (schema, data store, hosting platform, service or API version, framework, or vendor) as a staged parallel-change plan.
Sample result
How it works
What Migration Plan does
Covers an inventory of what moves and who depends on it, a compatibility matrix for old and new code against old and new data, a data preservation plan with reconciliation checks, backfill duration math, phases with entry and exit gates, a cutover and point-of-no-return decision, a rollback per phase, and a cleanup step.
Use it when
Someone asks how to migrate a database, move to a new platform or provider, change a schema without downtime, version or retire an API, plan a cutover, or write a rollback plan.
Use something else for
An audit of existing code health, for the target design itself, for infrastructure definitions, or for live incident handling.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Migration plan, compatibility matrix, rollback plan and cutover runbook
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Migration Plan
Updated Oct 20, 2026.
What does Migration Plan do?
Plan a safe technical migration (schema, data store, hosting platform, service or API version, framework, or vendor) as a staged parallel-change plan. Covers an inventory of what moves and who depends on it, a compatibility matrix for old and new code against old and new data, a data preservation plan with reconciliation checks, backfill duration math, phases with entry and exit gates, a cutover and point-of-no-return decision, a rollback per phase, and a cleanup step. Use when someone asks how to migrate a database, move to a new platform or provider, change a schema without downtime, version or retire an API, plan a cutover, or write a rollback plan. Do not use for an audit of existing code health (use codebase-audit), for the target design itself (use technical-architecture), for infrastructure definitions (use iac-setup), or for live incident handling (use coordinate-production-incident).
Who is Migration Plan for?
It is designed for engineering leads, platform engineers, database owners, technical project managers and release managers.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Migration Plan produce?
Migration plan, compatibility matrix, rollback plan and cutover runbook. Results come back with their sources and any open questions for you to check before anything is used.
How much does Migration Plan cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt90y3006n…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Migration Plan fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.