IT audit, then the MAP programme: the order of work in an SME
An SME considering a move to AWS hears about IT audits and the MAP programme at the same time, often from two different people. Both are useful, but not in any order. Here is the sequence we recommend, and what each step must have settled before moving to the next.
Two exercises that answer different questions
An IT audit answers the question "what state is our IT in?". It covers the whole information system: workstations, network, backups, access, providers, contracts, security. We set out the first checks in IT audit: where an SME should start.
The MAP programme answers a different question: "how do we move to AWS, and with what funding?". Its assess phase looks at what should migrate, with which dependencies, to which target. It has no interest in your workstations or your phone contracts.
Confusing the two leads to one of two mistakes: migrating an information system whose weak points nobody knows, or spending months auditing an estate that is going to leave anyway.
Step 1: the checks that cannot wait
Before any thought about the cloud, four points can be checked in a few days, because they expose the company today, migration or not.
Backups. Do they exist off site, and have they ever been restored? A backup that has never been tested is an assumption.
Access. Who holds administrator rights, and have the accounts of people who left been closed? Is strong authentication in place on email and remote access?
Providers. Who holds the passwords, the documentation and the contracts? A provider who is the only one to know how your IT works is a risk in itself.
Versions. Which systems are out of support? They are the ones that will complicate the migration, and the ones attacked first.
Whatever can be fixed quickly gets fixed straight away. The rest goes into the plan.
Step 2: decide what is meant to migrate
Once the baseline is set, the question becomes: what would gain from being on AWS? Not everything. A business application at end of life, replaced next year by online software, does not need to migrate. A file server can move to a storage service rather than to a virtual machine. These are leadership decisions, not technical ones.
This is the right moment to settle who owns the project on the company side. The MAP case commits to a scope and a schedule, so someone needs the mandate to defend them. When nobody does IT full-time, fractional IT leadership holds that role.
Step 3: the MAP assessment, on a scope that is already clean
The MAP assessment then starts from a clear scope and an estate whose weak points are known. It produces the detailed inventory of the workloads to migrate, their dependencies, the target architecture and the costing. The funding case rests on it, and we build that case for you: it is the core of our funded AWS migration offer.
A good prior audit shortens that assessment and makes it easier to defend: dependencies have already been mapped, privileged accounts listed, and the applications that stay out of scope already identified.
Step 4: migrate, then run
Migration happens in waves, from the least coupled applications to the most critical, each with its own go / no-go. The target is built to be run from day one: multi-account foundation, infrastructure described in code, monitoring, tested backups.
Then come operations, and with them the monthly bill. It is the part SMEs underestimate most, because the funding covers the move, not what follows. Our AWS page describes how we sequence audit, migration and operations, and our guide what a cloud migration really costs sets out the cost lines.
Two shortcuts to avoid
Building the MAP case before the baseline. The case is accepted, the schedule is committed, and halfway through you discover a backup that does not exist or an application nobody has the source code for. The schedule slips, and part of the funding with it.
Turning the audit into a project of its own. A months-long audit of an estate that is about to migrate produces a report that is out of date the day it is delivered. The step 1 checks take a few days; the rest is handled in the assessment.
In short
First secure what exposes the company today. Then decide what should migrate, and name who owns the decision. Launch the MAP assessment on that scope. Migrate in waves, then run with an owner for the bill. In that order, the audit serves the migration, and the funding serves the company.
Frequently asked questions
Do you need an IT audit before applying for the MAP programme?
The essential checks, yes: backups, access, providers and out-of-support versions. They take a few days and avoid discovering, mid-migration, a problem that pushes the schedule back. A long audit is not needed: the MAP assessment then takes over on the scope to migrate.
Does everything have to move to AWS?
No. An application at end of life, or soon to be replaced by online software, is not meant to migrate. Deciding what stays out of scope is part of the work, and it is a leadership decision.
Who should own the project in an SME with no IT staff?
A named person, with the mandate to arbitrate scope, hold the schedule and sign off cutovers. Fractional IT leadership holds that role when the company has nobody full-time on the subject.
Go further
This maps to our AWS Migration, MAP-funded offer, or talk it through with us.
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.