Drag
loader

Contact info

Based in
Melbourne, Victoria

Follow us

All resources // CHECKLIST

The cloud migration readiness checklist

Most migrations that go badly go badly for reasons that were visible before anyone started. This is the question set we work through during our own assessment stage, so you can run it yourself first, whether or not we end up doing the work. Twelve sections, ending in a decision record you can put in front of whoever has to sign. It is longer than a checklist, and calling it a workbook is more honest, so that is what it is.

Fillable workbook · 17 pages. Free.

WHO THIS IS FOR
  • Anyone with a migration that has been quoted more than once and started never
  • Businesses whose critical system runs on hardware nobody wants to touch
  • IT managers who need to explain the risk to a board before asking for budget
// READ IT BEFORE YOU BUY IT

The questions that catch migrations out

A real page from the document. The black bars mark detail removed for publication, or space left for you to fill in.

WHAT IS INSIDE
What you actually have Including the applications one department bought directly, and the cloud services nobody in IT provisioned
The dependency sweep Finding the integration nobody remembered until cutover weekend
Licensing traps What stops working, costs more, or becomes non-compliant once it moves
Data volume and downtime maths A unit-safe formula, a reference table and a worked example, because dividing terabytes by megabits is how this goes wrong by a factor of eight
Recovery objectives, and who approves them The four numbers that one question about acceptable downtime hides
Identity, hosting and data residency Usually the hardest part, plus where the data lives and where the support desk lives as two separate questions
Rollback planning and decommissioning What has to be true to reverse the decision, and the step that quietly never happens
The go / no-go and the decision record Answered the week before, then written down for whoever has to sign
Ferres Systems Cloud Migration Readiness
SAMPLE
SECTION 02 OF 12 // THE DEPENDENCY SWEEP

A common cause of failed cutovers is a dependency nobody documented. Work through these before scoping, not during.

ASK OF EVERY SERVER
  • What else authenticates against this server, including devices and printers
  • What scheduled tasks or scripts run against it, and who wrote them
  • Which reports, spreadsheets or dashboards pull data directly from its database
  • What has a hard-coded IP address or server name pointing at it
  • Which supplier or third party connects to it, and do they know it is moving
  • What certificates are installed, and when do they expire
THE ONE PEOPLE MISS HIGH

Hard-coded server names inside spreadsheets and reporting tools. They do not appear in any inventory, they belong to finance rather than IT, and they break on the Monday after cutover in a way that looks like the migration failed. We have found one of these three weeks after a project everyone had already declared a success.

HOW TO FIND THEM

Firewall and connection logs over a full month, not a week, because month-end processes are exactly the ones that only run at month end. A month still will not surface quarterly reporting, annual reconciliations, financial-year rollover or an audit extract that runs once, so ask about those separately rather than trusting the logs alone.

READY TO PROCEED WHEN PASS

Every observed inbound connection over at least 30 days is accounted for and owned by a named person, quarterly, annual and financial-year jobs have been checked separately because a month of logs will not show them, and each owner has confirmed in writing that they know the date.

YOUR ENVIRONMENT Fillable in the PDF, with an evidence and owner column
Sample page. The full document continues. 1 / 8
// GET THE FULL VERSION

Send me the question set

One email, with the document attached. We use a work address because these are written for businesses, and because it tells us which of our writing is worth doing more of.

  • The document arrives within a few minutes
  • No follow-up emails unless you tick the box
  • Never sold or shared for anyone else's marketing. Delivery providers are named in the privacy policy
RELATED SERVICE IT Projects and Microsoft 365 Scope, timeline and what it costs

Rather just talk it through?

Shapes Shapes