← All servicesService

Migration to AWS from on-premises, a VPS or Azure

I migrate your servers and databases to AWS on AWS's migration lifecycle: assess, mobilize and migrate in waves, with rollback at every cutover.

Get a migration assessmentThe quote comes out of the assessment.

01When it makes sense

  • Your servers or your hosting contract are reaching their end.
  • You are on Azure and the rest of your operation is already on AWS.
  • Nobody dares migrate because nobody knows what depends on what.

02How the work goes

  1. 01

    Assess

    Inventory, dependencies and team readiness. Out of it come the 7R strategy and the quote.

  2. 02

    Mobilize

    A landing zone in Terraform and a pilot wave, with your team in it.

  3. 03

    Migrate & Modernize

    The rest in waves: rehost, replatform or refactor per workload.

  4. 04

    Handoff

    IaC in your repository, runbooks, and your team operating.

03What is included

  • Readiness through the AWS Cloud Readiness Assessment, built on the CAF perspectives.
  • A 7R strategy per workload and a TCO comparison.
  • Replication with AWS MGN and AWS DMS.
  • A landing zone in Terraform, reviewed against AWS Well-Architected.

What is not

  • Running the environment after handoff.

04Records

Two real migrations: one into AWS and one out of it, because the platform is chosen in the assessment.

05Questions

How long is the service down?
As long as each cutover, scheduled with you and with a rollback ready.
How much does it cost?
It comes out of the assessment: with the inventory I put together a quote, and you approve it before anything starts. What AWS bills is pay-per-use and goes straight to AWS.
Who owns what gets built?
You do: the account, the code and the documentation.

Tell me what you have today and I will reply, almost always within 24 hours.

Get a migration assessment