How to Stage a OneDrive Migration by Department

Moving user files to OneDrive for Business across an entire organization can overwhelm IT teams and disrupt daily work. A departmental migration lets you move one group at a time, reducing support tickets and user confusion. This article explains how to plan, prepare, and execute a staged OneDrive migration by department using Microsoft 365 admin tools and PowerShell. You will learn the exact steps to move data in controlled waves, monitor progress, and avoid common mistakes.

What a Departmental OneDrive Migration Is and Why It Matters

A departmental OneDrive migration moves user files from local network drives or personal folders to OneDrive for Business in organized waves based on department membership such as Sales, Engineering, or Finance. This approach avoids moving all users at once, which can saturate bandwidth, overload support teams, and cause confusion when everyone needs help simultaneously.

Microsoft 365 does not provide a single button to migrate by department. Instead, you must prepare your tenant, organize user data, and use the SharePoint Migration Tool or PowerShell to target specific groups. The key prerequisite is having the Department attribute populated in Azure Active Directory for every user. Without this, you cannot filter users programmatically.

The migration itself involves scanning source folders, uploading files to the correct OneDrive location, and validating that data arrived intact. Each department wave should have its own schedule, communication plan, and rollback procedure. Staging by department also lets you test the migration process on a small group before scaling to larger departments.

Steps to Stage a OneDrive Migration by Department

Follow these steps to plan and execute a controlled departmental migration. The process assumes you have Global Admin or SharePoint Admin permissions and access to the Microsoft 365 admin center.

1. Verify and populate the Department attribute for all users
   Go to Microsoft 365 admin center > Users > Active users. Select a user, then choose the Contact info tab. Confirm the Department field shows the correct value. Use PowerShell to bulk-update missing departments: run Set-MgUser -UserId user@domain.com -Department "Sales". Export all users with Get-MgUser -All | Select DisplayName, UserPrincipalName, Department | Export-Csv users.csv to verify completeness.
2. Map source folders to OneDrive destinations
   Identify the network share or local folder path for each department. For example, the Sales department files might reside at \\fileserver\departments\Sales. Create a CSV mapping file with columns: SourcePath, TargetUserPrincipalName, TargetPath. The TargetPath should be /personal/{userprincipalname}/Documents/DepartmentFiles. Save this file as mapping-Sales.csv.
3. Install and configure the SharePoint Migration Tool
   Download the SharePoint Migration Tool from Microsoft Learn. Run the tool and select the option to migrate files using a CSV mapping file. Choose the mapping-Sales.csv file. Set migration priority to Normal for small departments or High for critical ones. Do not select the option to migrate all users at once.
4. Run a pilot migration for one small department
   Select a department with fewer than 10 users, such as HR. Start the migration in the SharePoint Migration Tool. Monitor progress from the tool dashboard. After completion, check OneDrive for each pilot user by signing into onedrive.com and verifying file presence and folder structure. Resolve any errors before proceeding to the next department.
5. Schedule departmental waves with communication and rollback
   Create a migration calendar with one department per week. For each wave, send an email to affected users three days before migration. Include the migration date, expected downtime, and a link to OneDrive setup instructions. Assign two IT support staff per wave to handle user questions. Prepare a rollback plan: if a department wave fails validation, restore files from the original network share backup and reschedule the wave.
6. Monitor migration health and user adoption
   After each wave, run Get-SPOMigrationJobProgress -Identity in PowerShell to check for failed items. Review OneDrive storage usage in the Microsoft 365 admin center under Reports > Usage > OneDrive. Verify that users in the migrated department are actively syncing files by checking the OneDrive sync client activity report in the admin center.

Common Mistakes and Things to Avoid When Migrating by Department

Migrating users without checking OneDrive storage quotas

Each OneDrive user gets 1 TB by default plus additional space if the tenant has more than five users. If a department has users with more than 1 TB of data, the migration will fail for those users. Check storage usage before migration by running Get-SPOSite -IncludePersonalSite $true in PowerShell. For users exceeding quota, either reduce the data set or submit a storage increase request through Microsoft 365 admin center.

Not updating file permissions before migration

OneDrive inherits permissions from the user account, not from the source network share. If department files have shared permissions set on the network folder, those permissions are lost after migration. Before migrating, document all share-level and NTFS permissions for the source folder. After migration, use OneDrive sharing settings to recreate external access for each file or folder that needs it.

Running multiple department migrations simultaneously

Running two or more department migrations at the same time increases network bandwidth usage and slows down the migration tool. It also splits IT support attention. Always run migrations sequentially with a minimum of 48 hours between waves. This gives time to validate data, handle user issues, and adjust the next wave based on lessons learned.

Forgetting to redirect Known Folder Move after migration

After user files are in OneDrive, configure Known Folder Move to redirect Desktop, Documents, and Pictures folders to OneDrive. This prevents users from creating new local files outside the synced environment. In Microsoft 365 admin center, go to OneDrive > Sync > Show notification to users who have Known Folder Move available. Enable the policy for each department after its migration wave completes.

Department Migration vs Full Organization Migration: Key Differences

Item	Department Migration	Full Organization Migration
Scope	One department at a time	All users simultaneously
Support load	Low per wave, predictable	High, often overwhelming
Network bandwidth	Controlled, scheduled	Peak usage may saturate link
Rollback complexity	Simple, one department only	Complex, affects entire tenant
Testing opportunity	Pilot on small department	No pilot possible

Department migration reduces risk and allows you to refine the process with each wave. Full migration is faster in total calendar time but requires more upfront planning and infrastructure.

You can now plan and execute a staged OneDrive migration by department using the SharePoint Migration Tool and PowerShell filtering. Start with a pilot department of fewer than 10 users to validate your mapping CSV and permission handling. After the pilot, schedule waves with at least 48 hours between each department. Use the Microsoft 365 admin center reports to confirm that users in each wave are actively syncing their files within one week of migration.

For advanced control, create a PowerShell script that reads department names from a CSV and launches migration jobs sequentially. This eliminates manual job creation for each wave. Always keep a full backup of source file shares until all department waves have completed and passed validation.