What if we are not ready to move?

We start with a roadmap. It says what moves, in what order, and what has to stay up. Execution is a later agreement.

Do you stay after the move?

We can. Operating the account, including cost and security, is a separate engagement from the migration itself.

What do you need before a roadmap?

What you run today, what cannot go down, and the limits you already have on security and cost.

AWS cloud migration

We move what you run onto AWS. If the move is still a question, the first deliverable is a roadmap. If the decision is made, we execute it.

Plan an AWS move

Roadmap or move

Some teams need to know what the move costs and what has to stay up before they commit. That engagement is an assessment and a roadmap. Some teams have already decided. That engagement is the plan and the move.

We will not pretend a roadmap is a migration, or start moving systems while the constraints are still unknown.

Assessment of what you run and what has to stay up
A roadmap with the order of the move
Hands-on execution once the scope is agreed

What stays in scope

Security and cost are part of the move, not a slide at the end. The target is workloads on AWS that your team can operate, with the practices we agreed.

Common questions

What if we are not ready to move?: We start with a roadmap. It says what moves, in what order, and what has to stay up. Execution is a later agreement.
Do you stay after the move?: We can. Operating the account, including cost and security, is a separate engagement from the migration itself.
What do you need before a roadmap?: What you run today, what cannot go down, and the limits you already have on security and cost.

AWS cost and operations
Cost, security, and day-to-day operations for AWS you already run.

AWS migration

Tell us what you run and what has to stay up. We will say whether you need a roadmap or a move.