About Expertise Work Managed Apps
Business Website Online Store Sales CRM Team Drive Online Academy Newsletter System Booking System Shared Inbox Knowledge Base Short Links Business Manager Photo Gallery Survey Platform Community Forum Project Boards Estate Agency Car Workshop Restaurant Clinic Photography Studio
AWS
Assess & advise Build & migrate Automate & operate Secure & comply Urgent & go-live
Projects
Hosted Monitoring & Dashboards Self-Hosted Observability Stack Bulk Document Data Extraction Email Deliverability Diagnosis & Repair SEO Migration Recovery AWS Security Review VPS Hardening & ModSecurity Cloud Architecture & Resilience Review SSL & Server Configuration Container Security Review DNS & Email Troubleshooting DevOps Deployment & Rollback Review WordPress Hardening Retainer Data Pipeline Rerun Review Metric Reconciliation
Free Tools
Website Health Check Email Domain Health Check DNS Health Check SSL Certificate Checker Redirect Chain Checker Robots.txt Checker XML Sitemap Validator Docker Compose Checker WordPress Security Check AWS IAM / S3 Policy Checker Domain Registration Lookup Uptime Monitoring Trial Downtime Cost Calculator AWS Cost Estimator Cloud Architecture Self-Assessment DevOps Engagement Builder Self-Managed VPS vs Managed AWS
Blog Certifications Hire Me

AWS Migration Readiness Assessment

What should move, what it will cost to run, and in what order — before anybody commits.

Price and scope

From $399

Typically $399–$899, fixed in writing before anything starts.

3–5 days
Working days, counted from the moment I have access — not from the day you agree.

What moves it up

  • An application nobody documented, where discovery is most of the work
  • A hard downtime limit, which changes the strategy rather than only the schedule
  • Licensing that follows the workload — databases and operating systems both bite here

Some of this you can check yourself, right now, for free: Self-Managed VPS vs Managed AWS →

The dependencies that are not on the diagramA web and application tier with a database, as documented. Outside that boundary sit three dependencies nobody drew: a shared file mount, a scheduled job on another machine, and an integration that only accepts one fixed IP address.THE SYSTEM, AS DOCUMENTEDweb tierapplicationdatabaseshared file mountjob on another hostpartner IP allowlisteach of these is discovered at cutover, or discovered now
AWS Migration Readiness Assessment

What actually goes wrong

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.

How I find it

  • An inventory taken from the running systems rather than from the documentation
  • netstat or ss on every host, to find the connections nobody drew on the diagram
  • A twelve-month cost model including transfer, IOPS and cross-zone traffic, not just compute
  • Licence terms checked for anything that changes price or validity when it moves to a cloud

What you get

  • A dependency map built from what is running, including the things not in the diagram
  • A per-workload recommendation — move as is, change it first, or leave it where it is
  • A twelve-month AWS cost estimate with the assumptions written down and challengeable
  • A sequenced plan with the risky steps identified and a rollback for each
  • An honest statement of what should NOT move, which most assessments do not include

Questions

What if the assessment says we should not migrate?

Then 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.

Do I have to use you for the migration afterwards?

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.

How accurate is the cost estimate?

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.

Can you assess something that is not on AWS yet at all?

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.

AWS Cost Optimization Audit

Where the money is going, what can be cut without touching reliability, and what it is worth.

From $249 2–3 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.

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.