Guide · Updated 2026-10-14
Back up before you migrate: a Microsoft 365 and cloud migration checklist
Most migration horror stories are not about the move itself. They are about a mailbox that did not copy, a permission that changed, or a file that was overwritten, with no clean copy to go back to. This checklist puts a backup and a rollback at every step.
1. List what you are moving
Write down every application, mailbox, file share and user group, and what depends on what. Mark what is critical and what can move later. This list becomes your test plan.
2. Take a backup of the source first
Before anything moves, make a copy of the current environment that you can restore from independently of the migration tool. If you are already on Microsoft 365, back up mail, OneDrive, SharePoint and your Entra ID directory before changing tenants, domains or licences.
3. Pick the cloud model and check where data will live
Decide between public, private or hybrid based on your security and performance needs. Check the region your data will be stored in. Storing it in Canada keeps it close to home. If a contract or regulator sets residency rules, confirm them with your advisor.
4. Move in phases, lowest risk first
Start with a small group or a low-risk system. Check that mail, files, sign-in and permissions all work before moving the next group. Keep the old system running until the new one is proven.
5. Test the rollback before each phase
Know how you would undo each phase, and try it on test data. A rollback you have never run is a guess. Record the date and the result.
6. Keep backing up after the move
The migration ends, but the risk does not. Under Microsoft's shared responsibility model, your data and configuration are yours to protect, and recycle bins are short. Make the new environment's backup automatic from day one.
storiv backs up Entra ID, Exchange mail, OneDrive and SharePoint to encrypted storage in Canada, with a change log and risk alerts. It restores users and groups today, and it is free for up to 5 users. It is not a migration tool: it does not move data between systems.
Common questions
- Should I back up before migrating to Microsoft 365?
- Yes. Keep a copy of the source that you can restore without the migration tool, so a failed or partial move never means lost data.
- Does storiv migrate my data to Microsoft 365?
- No. storiv backs up and restores data in Microsoft 365. Use a migration tool or partner for the move itself, and put the backup in place before and after.
- Why migrate in phases?
- A small first group shows problems with mail, permissions or sign-in while few people are affected, and gives you a safe point to roll back to.
Want this covered for your tenant?
storiv is onboarding a waitlist first. Free for up to 5 users.
Join the waitlist