Scale Me NowSCALE ME NOW
Scale Me Now / Guides / AWS from audit to operations: how to sequence MAP, IT leadership and run
Guide

AWS from audit to operations: how to sequence MAP, IT leadership and run

On AWS the stages are well known: audit, fund, migrate, run. What makes projects fail is rarely a stage done badly, it is the joint between two stages, when what one learned never reaches the next. Here is how we sequence the four, and what each must pass on.

Why the order matters

The leaders who call us often already hold one piece of the puzzle: an audit done two years ago, a migration proposal priced by a provider, an AWS bill that keeps rising without anyone knowing why. Each piece was produced on its own, by someone who would never see the next one.

The outcome is predictable. The audit lists gaps the migration ignores. The funding case describes a target that operations only discover when they take it over. The bill afterwards has no owner. None of these problems is technical: they are problems of continuity.

Our AWS page presents the four stages as one path for that reason. This guide explains the logic behind it.

Stage 1: the audit, to know what we are talking about

Everything starts from an evidence-based review: accounts, configurations, invoices, and, when a migration is on the table, the code and infrastructure still running elsewhere. On an existing AWS estate, that is the Well-Architected audit: security, cost, reliability, performance, operations. On an estate not yet in the cloud, the assess phase of the MAP programme plays that role.

What the audit must hand on: a real inventory, gaps ranked by their consequence for your business, and a first view of what has to be fixed before anything moves. An audit that stops at a list of generic recommendations hands nothing useful to the next stage.

Stage 2: the MAP programme, to fund and commit

AWS's Migration Acceleration Program co-funds migrations: the assessment first, then credits tied to the workloads actually migrated. The case is built with a partner, on a scope, a target and a schedule. We have explained how it works in the AWS MAP programme, explained simply.

What matters here is the joint. A solid MAP case is built on the inventory from stage 1, not on a self-declared questionnaire. It commits to a schedule, so someone on the company side needs the mandate to hold it.

What the case must hand on: a path per domain, the order of the waves, and the list of what deliberately stays out of the cloud.

Stage 3: the cutover, domain by domain

Migration happens in waves, from the least coupled applications to the most critical. Each wave has its go / no-go: tests passed, backups checked, rollback plan written. It is a risk decision, not a technical one.

Two mistakes keep coming back at this stage. The first is building the target without thinking about how it will be run: accounts created by hand, monitoring left "for later". The second is letting the migration provider decide alone what goes and what waits. In MAP without a CIO we set out the decisions that cannot be delegated.

What the cutover must hand on: a clean multi-account foundation, infrastructure described in code, up-to-date documentation, and backups that have been restored at least once.

Stage 4: operations, where the bill is decided

Once the migration is over, cloud consumption becomes a living cost line that moves every month. The funding paid for the move; it does not pay for the operations that follow. It is often around month six that the bill comes as a surprise, when test environments still run at night and machines have never been resized since the cutover.

Operations cover deployments, monitoring, changes, backups and incidents, with on-call cover when the business needs it. They include cost control: scheduled shutdowns, right-sizing, clearing orphaned resources, and a monthly report leadership actually reads. Without that, the migration cost money without paying back.

The role that holds it together

Four stages, up to four providers, and one question: who makes the calls end to end? That is the job of IT leadership, in-house or fractional. It reads the audit, defends the scope of the case, signs off the cutovers and opens the bill every month. Our fractional CIO offer holds that role when the company has nobody full-time on the subject.

One caution applies to every firm, ours included: whoever arbitrates the scope and whoever invoices the delivery should not be the same signature without a safeguard. When one firm holds both roles, ask for the steering mandate to be written separately, with its own milestones and its own right to say no.

Where to come in

You do not have to start with a migration. Many engagements begin with the free audit, or with taking over the running of an AWS estate already in place. What matters is that the stage you start from already knows what it will have to hand to the next one.

Frequently asked questions

Do you need an audit before filing a MAP case?

For an estate not yet in the cloud, the assess phase of the MAP programme plays that role: it produces the inventory and the path the case rests on. On an existing AWS estate, the Well-Architected audit comes first, to fix what needs fixing before the platform grows.

Does the MAP programme fund operations after the migration?

No. It co-funds the assessment and the migration itself. The operations that follow, and the monthly cloud bill, stay with the company, which is why they need a named owner from the start.

Can you start by running an existing AWS estate?

Yes. Many engagements start by taking over operations of an environment already in place, preceded by an audit to know what is being taken over. Migrating other workloads can come later.

Go further

This maps to our AWS Migration, MAP-funded offer, or talk it through with us.

/ Contact

Let's talk about your situation.

A 30-minute call, no strings attached. Reply within 24 business hours.

Your details are used only to answer your enquiry: never sold, never used for cold outreach. Privacy policy.

/ Scale Me Now

A question about your IT?

Book 30 minutes

An expert replies within 24 business hours.