Database Migration to Amazon RDS
PostgreSQL or MySQL onto RDS, with the cutover rehearsed and a way back.
From $549 3–7 days
Website / Application Migration to AWS
Moved onto AWS with the cutover rehearsed, the DNS planned, and the old host still standing.
Price and scope
From $459
Typically $459–$1,299, fixed in writing before anything starts.
What moves it up
- No downtime allowed, so the move has to run both sides in parallel
- A stack nobody documented, where the first job is finding out what it runs on
- Background jobs, scheduled tasks or outbound mail that live outside the application
Some of this you can check yourself, right now, for free: Website Health Check →
What actually goes wrong
The site comes up on the new server and looks perfect, so the DNS gets pointed and everybody goes home. What surfaces over the following week is everything that was never part of the website: the cron job that emailed the weekly report, the upload directory that lived outside the document root, an absolute path baked into a config file, and mail that worked because the old host ran a local sendmail nobody knew was there. None of it shows up in a browser, and all of it was working the day before.
How I find it
crontab -l for every user on the source box, not just the one you log in asA byte-count and file-count comparison of the document root and every directory outside itdig +trace on the live domain, and every TTL lowered before the window rather than during itThe application exercised end to end against the new host by hosts-file override, before any DNS moves
What you get
- The application running on AWS, reachable and verified before anything public changes
- An inventory of everything found outside the web root — jobs, uploads, mail, certificates
- A cutover plan with the TTL schedule, the order of operations and the point of no return marked
- The old environment left running and untouched, so rollback is real rather than theoretical
- A written record of what changed, for whoever maintains it next
Questions
How long will my site be down?
For most moves, nothing more than the DNS propagation you plan for — the new environment is built and verified in parallel while the old one keeps serving. Where a database has to stop taking writes, that window is measured during the rehearsal and agreed with you before the real cutover is booked.
What if something breaks after we switch?
We point DNS back. The old environment stays up and untouched for as long as you want it, which is the entire reason rollback works — it is only real while the thing you are rolling back to still exists. Nothing is decommissioned as part of this engagement.
Will my email keep working?
It is checked explicitly, because this is where migrations most often quietly fail. If mail currently leaves through the server being replaced, that has to be rebuilt somewhere — and if your MX records point elsewhere entirely, we confirm the move does not disturb them.
Do you migrate the database as part of this?
A straightforward one, yes. If it is going onto RDS, changing major version, or big enough that the copy no longer fits in the window, that is its own engagement with its own rehearsal — and I will say so when I scope this rather than discovering it mid-cutover.
If this is not quite it
Route 53 DNS Migration
A zone moved with every record accounted for, and the TTLs lowered before the change rather than after.
From $199 1–2 days
EC2 Server Setup & Hardening
A server built the way you would build it on day 400, not day one.
From $199 1–2 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.