Design
Migrations
Migration plans from what your repository runs today, from one provider to another, or from one service to another, with ordered reversible steps, downtime estimates, risks and costs before and after.
Migration plans are available on Pro and above.
Three kinds of migration
| From | To | Example |
|---|---|---|
| Your current platform | A Brunel tier | Heroku → AWS Growth |
| One provider | Another provider | AWS → Scaleway |
| One service | Another service | Self-hosted Redis → managed cache |
Brunel detects the current platform from the repository: Terraform, Kubernetes, Helm, Serverless Framework, Vercel, Netlify, Heroku, Fly, Render, Railway, Platform.sh, AWS Amplify, App Runner, Elastic Beanstalk, Google App Engine or Cloudflare Workers.
What a plan contains
- Ordered steps you can reverse, each with its rollback.
- A downtime estimate and the risks for every step.
- The monthly cost before and after, computed by the deterministic pricer.
- The plan is exported as
MIGRATION.mdwith the rest of the files.
Honest limits
A plan describes the infrastructure moves. Data migration tooling, DNS cut-over timing and application changes specific to your code are listed as steps to perform, not performed by Brunel.