Cloud infrastructure checklist for a calmer cutover.

For a calmer cutover, sort out discovery, access, cutover planning, user communication and post-migration support before cloud work begins.

See cloud infrastructure Talk through a project

Before migration

Audit users, shared systems, files and access
Review app and licence assumptions
Define success criteria and rollout order
Document dependencies and blockers

Cutover

Agree outage windows and communication timing
Verify sign-in, MFA and device readiness
Test critical workflows, shared files and permissions
Prepare escalation contacts for day one issues

After migration

Support users through the first friction points
Tidy permissions and unused artefacts
Confirm backup and compliance expectations
Document ownership and ongoing support routines

Clear planning

A migration runs more smoothly when decisions, checks and responsibilities are clear before the actual cutover begins.

What to decide early

Confirm who owns approvals, when staff are notified, how access is tested, what happens if cutover slips and who handles support in the first few days after migration.

FAQ

Questions tied directly to migration planning.

It keeps discovery, access, cutover planning and support responsibilities visible before the migration starts, which reduces last-minute surprises.

Missed dependencies, unclear permissions, weak communication timing, incomplete device readiness and no clear owner for day-one issues are common sources of friction.

Discovery steps, platform decisions, access rules, security baselines, cutover sequencing, communication templates and post-migration support commitments should all be tailored to the business.