Migrating user files to OneDrive for Business via a cutover migration requires careful planning to minimize data loss and downtime. A cutover migration moves all user data from a source system like Google Drive or Box to OneDrive in a single batch operation. This article explains the specific steps you must take to prepare end users before the migration starts and what to do immediately after the cutover completes.
Key Takeaways: User Preparation for OneDrive Cutover Migration
- Communication email sent 7 days before cutover: Notify users of the migration date, expected downtime, and required actions to save unsynced files.
- File size and naming check: Users must remove files over 250 GB and rename paths longer than 400 characters to prevent sync failures.
- Post-migration verification checklist: Users should open OneDrive sync app, confirm Files On-Demand is enabled, and verify that all folders appear.
What a OneDrive Cutover Migration Does and Why User Preparation Is Required
A cutover migration copies all user files from the source platform to OneDrive for Business in one pass. The process runs over several hours or days depending on data volume. During the migration, users cannot access their source files because the system locks the source account. After the migration completes, users sign in to OneDrive and see their files in the cloud.
User preparation prevents three common failure points. First, files that exceed OneDrive limits never transfer. Second, users who do not back up locally stored files lose data if the source account is deprovisioned early. Third, users who do not install the OneDrive sync app cannot access files offline. The IT team must coordinate communication, file cleanup, and post-migration verification with every affected user.
The preparation timeline spans two weeks. Week one covers communication and file inventory. Week two focuses on user training and the migration itself. This article covers both phases in detail.
Steps to Prepare Users for a OneDrive Cutover Migration
Follow these steps in order. Do not skip any step. Adjust timing based on your organization size.
Phase 1: Send Initial Notification 14 Days Before Cutover
- Draft the email with migration date and downtime window
State the exact date and time when the cutover begins. Example: “Your files will migrate starting Friday, March 24 at 6:00 PM local time. You will not be able to access your source files from that time until Monday, March 27 at 8:00 AM.” Include the expected duration in hours. - List required user actions with deadlines
Tell users to remove files over 250 GB, rename folders with special characters like # % & , and save any files stored only on their local device to the source cloud before the migration starts. Set a deadline of 3 days before the cutover. - Include a link to a short training video or PDF
Create a 3-minute video showing how to open OneDrive, sign in, and turn on Files On-Demand. Host it on your intranet or SharePoint. Provide a direct link in the email. - Set up a migration support mailbox
Create a shared mailbox named onedrive-migration@yourdomain.com. Add it to the email so users can ask questions. Assign two IT staff to monitor the mailbox during business hours.
Phase 2: File Cleanup and Backup 7 Days Before Cutover
- Ask users to run the file inventory script
Distribute a PowerShell script or a manual checklist that scans the user’s source folder for files exceeding OneDrive limits. OneDrive supports files up to 250 GB and paths up to 400 characters. Users must delete or archive oversized items. - Instruct users to save local-only files to the source cloud
Users who keep files on their desktop or Documents folder must upload them to the source cloud before the cutover. The migration only copies files stored in the source cloud, not local hard drives. Give a specific deadline: “Upload all local files by end of day Friday.” - Verify that each user has a valid Microsoft 365 license
In the Microsoft 365 admin center, go to Billing > Licenses. Confirm that each user assigned to the cutover has a license that includes OneDrive for Business. Licenses without OneDrive cause the migration to fail silently. - Run a test migration for 5 pilot users
Select 5 users who represent different departments. Run the cutover for those users only. Verify that all files transfer and that file permissions are intact. Fix any errors before the full migration.
Phase 3: Day of Cutover — Final Check and Communication
- Send a reminder email 2 hours before the cutover
Repeat the downtime window. Ask users to save any open files and sign out of the source system. Provide the support mailbox address again. - Run the cutover migration from the admin center
In the Microsoft 365 admin center, go to Admin centers > Migration. Select the cutover migration batch you created earlier. Click Start migration. Monitor the progress in the migration dashboard. - Notify users when the migration completes
Send an email with the subject “Your OneDrive is ready.” Include step-by-step instructions to sign in to OneDrive, open the sync app, and verify files. Set the expectation that files may take up to 24 hours to appear in the sync app due to indexing.
Phase 4: Post-Migration User Verification
- Ask users to open OneDrive and check Files On-Demand
Users right-click the OneDrive cloud icon in the system tray, select Settings, go to the Sync and backup tab, and click Advanced settings. Under Files On-Demand, confirm that “Save space and download files as you use them” is selected. This setting prevents the user’s hard drive from filling up. - Instruct users to open 5 random files
Users should open an Office document, a PDF, an image, a text file, and a file from a shared folder. If any file shows a red X or does not open, the user should report it to the support mailbox. - Set up OneDrive Known Folder Move for new users
In the OneDrive admin center, go to Sync > Known Folder Move. Enable the policy to automatically back up Desktop, Documents, and Pictures folders. This step is optional but recommended for all new OneDrive users.
Common User Mistakes During a OneDrive Cutover Migration
Users forget to save local files before the cutover
The most frequent issue is users losing files stored only on their local hard drive. The cutover migration does not touch local folders. To recover these files, the user must manually upload them to OneDrive after the migration. To prevent this, send a second reminder 48 hours before the cutover that specifically says “Files on your computer are not migrated.”
Files with special characters in the name fail to sync
OneDrive does not sync files with characters like # % & { } \ : < > ? / | ” ~. If a user has files with these characters, the migration logs an error. The file remains in the source system. After the migration, the user must rename the file in the source system and then manually upload it to OneDrive. To avoid this, run a pre-migration scan that identifies files with invalid characters and ask users to rename them.
Users cannot find shared folders after migration
Shared folder permissions do not always transfer in a cutover migration. If a user had access to a shared folder in the source system, they must be re-invited in OneDrive. After the migration, the IT team should run a permissions report from the OneDrive admin center and re-share any missing folders. Users should check their “Shared with me” list in OneDrive and report missing items.
| Item | Before Cutover (Day -7) | After Cutover (Day 0) |
|---|---|---|
| File storage location | Source cloud + local hard drive | OneDrive cloud only |
| File size limit | Depends on source system | 250 GB per file |
| Path length limit | Depends on source system | 400 characters |
| Special characters allowed | May allow # % & | Not allowed |
| Shared folder permissions | Active in source system | Must be re-invited |
| Files On-Demand setting | Not applicable | Must be enabled manually |
You now have a complete user preparation plan for a OneDrive cutover migration. Start with the 14-day communication email, run the file cleanup checklist, and finish with the post-migration verification steps. For your next migration, consider using a staged migration instead of a cutover if your organization has more than 500 users or files over 1 TB total. The staged approach reduces downtime by moving users in smaller groups.