Will the business stop during the migration?
The process is built to stay seamless. Assessment and planning come first, so cutover is a step in a sequence. The business is the point of the project, and the plan is written around keeping it running.
How do you keep the AWS bill from drifting?
Cost is part of the plan, and optimization is the last step of the engagement. The migration is carried out to stay time- and cost-effective after the workloads are on AWS.
What if the environment is poorly documented?
That is a usual place to begin. Assessment exists to see the data center as it is, including the parts that were never written down, before a plan asks anyone to move them.
What happens when we write to you?
Use the assessment form, or write to us directly. You get the assessment, not a commitment to move. We reply with what should move, wait, or be retired, and what that will take in time and cost.
Do we have to choose what to rebuild before we talk?
No. That choice is an output of the assessment. Some workloads should move as they are, some should change, and some should be retired. You see the recommendation before a migration starts.
How long does a move take?
The assessment sets the time. A smaller estate is a shorter sequence than a large one, and the order is written down before cutover.
What if a cutover has to stop?
The plan includes a way back. The systems you run today stay in place until the path on AWS is proven, so a cutover that stops returns to the estate you already have.
What do we receive from the assessment?
A written picture: what should move, wait, or be retired; the order of the move; the time; and the cost. The migration is a decision you make after that picture exists.