Cloud migration readiness worksheet
IT MGMT · Planning aid · Updated September 17, 2026
Use this with your IT provider before moving email, files or applications. Print it or save a PDF with your browser’s Print command. Keep completed notes in your own business systems.
Project / review date: __________________________________________
Business owner / IT contact: ____________________________________
Leave passwords, recovery codes and private customer information out of these notes.
| Decision to make | Owner, evidence and next action |
|---|---|
| Purpose and scope What problem are we solving? What source, destination, users and data are included? What stays where it is? | |
| Ownership Who approves changes, owns each account and controls recovery? Who is the backup contact? | |
| Dependencies Which applications, licenses, printers, devices, vendors and network connections must work? | |
| Permissions Who should have access? Which former users or external sharing links need review? | |
| Pilot Who will test each representative task, from which device and location? What counts as a pass? | |
| Cutover When will changes stop on the old system? Who communicates with staff and performs the final synchronization? | |
| Fallback What triggers a pause? Who decides? How will work created after the switch be preserved if we revert? | |
| Recovery What data is protected, how long is it retained and who can test a recovery? | |
| Acceptance What evidence shows the agreed workflows and permissions work? Who signs off? | |
| Handover Where are instructions stored? Who supports the team and approves retirement of the old service? |
A sample acceptance test
Planning example: an authorized employee signs in from a supported laptop, opens an agreed sample customer file and shares it with an approved colleague. A user without permission cannot access it. Record the date, actual result and issue owner. Choose separate tests for email, calendars, printing and any business application in scope.
Go or pause?
- Scope and account ownership confirmed.
- Dependencies resolved and representative tasks passed.
- Permissions checked with authorized and unauthorized test roles.
- Cutover, communications and fallback approved.
- Recovery, retention and support responsibilities documented.
Decision: proceed / pause / more evidence needed
Approved by / date: ____________________________________________
Open issues, owner and due date: _________________________________
Next review: __________________________________________________
A successful pilot is evidence for that test, not a promise of a disruption-free migration. Preserve the old service and required records until the agreed acceptance and retirement checks are complete.
Read the full planning guide or discuss a Business IT project with IT MGMT.