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
What should move, what it will cost to run, and in what order — before anybody commits.
From $399
Typically $399–$899, fixed in writing before anything starts.
What moves it up
Some of this you can check yourself, right now, for free: Self-Managed VPS vs Managed AWS →
Migrations are quoted from what the application looks like and go wrong because of what it depends on. The dependency nobody mapped is the one that fails at cutover: a shared file mount two services both use, a scheduled job on a machine nobody counted as part of the system, an integration that only accepts traffic from one fixed IP address. And the running cost gets estimated from instance sizes, which is the smallest part of the bill — data transfer, storage IOPS and inter-zone traffic are what make the first invoice a surprise.
An inventory taken from the running systems rather than from the documentationnetstat or ss on every host, to find the connections nobody drew on the diagramA twelve-month cost model including transfer, IOPS and cross-zone traffic, not just computeLicence terms checked for anything that changes price or validity when it moves to a cloudThen it says that, and it is the most valuable outcome this can produce. Some workloads are cheaper and more reliable where they are, and finding that out for a few hundred dollars beats finding it out halfway through a migration.
No. The plan is written to be handed to anyone, including your own team or another contractor, and it does not depend on me to execute. If you do use me, the assessment fee comes off the migration.
Close on compute and storage, less certain on data transfer, which depends on traffic patterns nobody can fully predict in advance. Every assumption is written down so you can argue with the ones that look wrong rather than trusting a single number.
That is the usual case — on-premises servers, a colocation rack, another cloud, or a mix. The discovery work is the same: find what is actually running and what it talks to, which is rarely what the documentation says.
Moved onto AWS with the cutover rehearsed, the DNS planned, and the old host still standing.
From $459 2–5 days
Where the money is going, what can be cut without touching reliability, and what it is worth.
From $249 2–3 days
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.
Sunday to Thursday, 09:00–18:00 EET. Outside that I will still look, but I will not promise a time.
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.
You pay Amazon directly and you keep control of the account. Nothing here resells your infrastructure or sits between you and your own billing.
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.