AWS Migration Readiness Assessment
What should move, what it will cost to run, and in what order — before anybody commits.
From $399 3–5 days
Cross-Cloud / Datacenter Migration
Off another cloud or out of a rack, in stages, with each stage independently reversible.
Price and scope
From $849
Typically $849–$2,799, fixed in writing before anything starts.
What moves it up
- Physical servers, where the copy is bounded by a network link rather than by an API
- A staged cutover, which means running in two places and keeping them consistent
- Egress charges at the source, which are a real line item and occasionally the largest one
Some of this you can check yourself, right now, for free: Self-Managed VPS vs Managed AWS →
What actually goes wrong
A cross-cloud move looks like a big version of a server migration and behaves like a different problem, because the parts that do not travel are the managed services. The load balancer, the object store, the queue, the managed database and the identity system all have an AWS equivalent that is close enough to plan with and different enough to break something at cutover. And the schedule is usually built from how long the data takes to copy, when the binding constraint is how long the two environments have to stay consistent while it copies — which is a completely different number, and the one that decides whether a staged cutover is even possible.
How I find it
A service-by-service mapping from source to AWS, with the behavioural differences written down, not just the namesThe actual transfer measured over the real link, rather than calculated from the link's ratingThe source provider's egress pricing, checked and included in the cost of movingEvery hardcoded endpoint, region and credential found before anything is repointed
What you get
- A staged plan where each stage is independently reversible, not one cutover with a single decision point
- The AWS equivalents built and verified while the source is still serving production
- A data synchronisation approach that keeps both sides consistent for the duration of the overlap
- Cutover and rollback runbooks per stage, each rehearsed before the stage is scheduled
- The source environment left intact until you decide otherwise, which is what makes rollback real
Questions
Can we move in stages, or does it have to be one weekend?
Stages, almost always, and it is worth the extra complexity. One weekend means one decision point and one rollback for everything at once. Stages mean a bad outcome affects one component, and you learn from each before committing the next.
How much will the other provider charge us to leave?
Egress is the line to check, and on a large data set it can be substantial. Some providers have reduced or removed exit fees under regulatory pressure — it is checked against your account and your volume rather than assumed either way, and it goes in the estimate.
What about the managed services we depend on there?
Each gets mapped to an AWS equivalent with the differences documented — not just "S3 is like their object store", but what changes about consistency, permissions and limits. That mapping is where cross-cloud migrations actually fail, so it is done first rather than during.
Can you move us out of a physical datacenter?
Yes. It is the same method with a harder constraint: the transfer is bounded by the link you have, and for a large data set that can mean AWS Snowball rather than the network. The plan says which, with the arithmetic, before anything is scheduled.
If this is not quite it
Website / Application Migration to AWS
Moved onto AWS with the cutover rehearsed, the DNS planned, and the old host still standing.
From $459 2–5 days
Want this done?
Tell me what you are running and I will come back with a fixed price and a date. If it turns out you do not need this, I will say that instead.
Prefer to talk? Book a free call ↗ · Or hire me on Upwork ↗ · Typical reply within one business day.
Before you enquire
When I answer
Sunday to Thursday, 09:00–18:00 EET. Outside that I will still look, but I will not promise a time.
No 24/7 desk, and I will not pretend otherwise
One person, one time zone. If round-the-clock cover is what you need, you need a team, and I will say so rather than sell you a plan that cannot deliver it.
Your AWS bill stays yours
You pay Amazon directly and you keep control of the account. Nothing here resells your infrastructure or sits between you and your own billing.
A price that starts with "from" is a starting price
Every service page lists exactly what pushes a quote above it, before you ask. You get a fixed number in writing before any work begins.