To AWS without the horror stories.
From data center, VMware or "accidental AWS" to a Well-Architected foundation in 8–16 weeks. Fixed price. Staged, wave-planned cutover. Rollback plan in writing before anything moves. Security and cost guardrails built in from day one, not bolted on after.
Why migrations go wrong
- Lift-and-shift-and-regret. Everything moves as-is, the bill triples, and "we'll optimize later" never comes. The 7R decision — what to rehost, replatform, retire — has to happen before the move. (Our 7R framework guide is the reference we use.)
- No landing zone. Workloads land in one flat account with admin-for-everyone IAM — the security and cost chaos is designed in from week one.
- Big-bang cutover. One weekend, one giant switch, no rollback. When DNS, data sync and the one legacy dependency disagree, there's no way back.
How we migrate
1 · Readiness Assessment (2 weeks)
Inventory and dependency mapping, 7R disposition per workload, target architecture, TCO model comparing current vs AWS run-rate, wave plan and fixed project quote. €7,500 — credited if the project proceeds.
2 · Landing zone (2–3 weeks)
Multi-account structure (Control Tower), IAM and SSO, networking, logging and guardrails — all in Terraform, all in your repos. Security baseline and cost tagging from the first commit.
3 · Waves & cutover (4–10 weeks)
Workloads move in planned waves, lowest-risk first. Each wave: replicate, test against production traffic patterns, cut over in a defined window, verify, then decommission. Every wave has a written rollback.
4 · Hypercare (30 days)
The team that moved you watches the estate: performance tuning, cost check against the TCO model, runbooks handed over. Most clients keep the team on as Managed Services — first 3 months at 20% off.
Pricing
| Engagement | Price | Timeline |
|---|---|---|
| Migration Readiness Assessment | €7,500 fixed (credited if project proceeds) | 2 weeks |
| Migration project — landing zone + waves + hypercare | €25,000–150,000 fixed by wave count, staged 30/40/30 | 8–16 weeks |
| Post-migration operations | Managed Services from €3,000/mo — 20% off first 3 months | Ongoing |
Fixed means fixed: scope changes are priced as written change orders, never as surprise invoices.
Frequently asked questions
How much does an AWS migration cost?
Projects run €25K–150K depending on workload count and complexity — the readiness assessment produces the exact fixed quote, plus the TCO model showing what your AWS run-rate will be. As a rule of thumb, mid-market migrations pay back within 12–24 months against hardware refresh and licensing costs.
How much downtime should we expect?
Per-workload cutover windows are defined in the wave plan — typically minutes to low hours per workload, scheduled to your business calendar. Zero-downtime patterns (replication-based cutover, blue-green DNS) are used where the workload justifies them.
What's our team's role during the migration?
Your engineers own application knowledge and acceptance testing; we own AWS architecture, IaC, replication and cutover mechanics. Weekly wave reviews together. Your team ends the project knowing the new estate — everything is in Terraform in your repos, documented.
What if a wave fails?
Every wave has a written rollback executed against a criteria checklist — if verification fails inside the window, we roll back, diagnose, and re-plan the wave. That's why we migrate in waves and refuse big-bang cutovers: a failed wave is a delay, not an outage.
VMware exit — can you handle it?
Yes; post-Broadcom licensing changes made VMware estates one of our most common migration sources. The assessment maps hosts and VMs to the right AWS disposition — from EC2 rehost to replatforming onto managed services where the economics are better.