Services / Cloud & Database Migration
Move to AWS or a new database without losing data or weekends.
Migrations fail when they're done in one big jump. We plan a phased move with a tested rollback at every step, so your users keep working while it happens.
On-prem → AWS · MySQL → PostgreSQL · Heroku/Firebase → AWS
✓ phase 1 copy data, keep in sync✓ phase 2 10% of traffic to AWS✓ phase 3 50% of traffic, compare errors● phase 4 100% on AWS· rollback tested at every phase· old system off after 2 stable weeks
Sound familiar?
Signs you need this
Servers in a data centre or on a single VPS you're afraid to touch
Heroku, Render or Firebase costs or limits are hurting
You're moving from MySQL to PostgreSQL
A previous migration attempt stalled halfway
The change
Before and after
| Before | After |
|---|---|
| A risky weekend 'big bang' move | Small phases you can undo |
| Unknown dependencies break things | Every dependency mapped before the move |
| Data checked by spot tests | Every table checked row by row |
What you get
Deliverables
Target design
Where every part of the system will live on AWS, with costs estimated.
Migration plan
Order of moves, downtime windows (ideally none) and a rollback for each step.
Schema conversion
Database schema and data types converted and tested.
Data migration
Data copied, kept in sync during the move and checked row by row.
Phased cutover
Traffic moved over in stages with monitoring at each stage.
Decommission
Old systems switched off only when the new ones are proven.
How it runs
Four steps
- AssessInventory of what runs where and what depends on what.
- PlanWritten plan with dates, risks and rollbacks.
- RehearseFull dry run on a copy of production.
- MovePhased cutover, then the old system is retired.
What we need from you
- Access to the current system and a copy of production data
- A list of who uses the system and when it's quiet
- A decision-maker for go/no-go at each phase
Proof
Done before, in production
- Led on-premise to AWS and MySQL to PostgreSQL migrations on a platform used in thousands of workshops worldwide
- Designed secure cross-region data and file transfer from the EU to China under local data rules
From our lead engineer's roles at larger companies. See Work.
Fit and price
A good fit if
- You know what you want to move and why
- You can give us access to a copy of production data
Not a fit if
- Mainframe or very old legacy systems
- Moves to clouds other than AWS
Price Assessment can start as the Cloud Cost & Health Audit (€990). Migration is quoted after it.
FAQ
Will there be downtime?
We plan for none. Where a short window is unavoidable, you choose when.
What if something goes wrong?
Every step has a tested rollback. We don't switch off the old system until the new one has run in production.
How long does it take?
Small apps take 2–3 weeks. Larger systems are planned in phases after the assessment.
Also useful
Tell us what you're building.
20 minutes, no pitch deck needed. You leave with a clear next step, even if it isn't us.