How to Plan a File Server to OneDrive Migration in OneDrive for Business

You need to move files from a network file server to OneDrive for Business but the process involves more than just copying folders. A file server migration requires careful planning to avoid broken permissions, lost version history, and user confusion. This article explains the key phases of a migration project from inventory and cleanup to sync configuration and cutover. You will learn how to map file server shares to OneDrive and SharePoint destinations, handle permission migration, and manage user adoption.

What a File Server to OneDrive Migration Involves

A file server migration moves data from on-premises network shares to cloud storage in OneDrive and SharePoint. The process is not a simple copy-paste operation because file servers and OneDrive have different permission models, sync behaviors, and storage limits. OneDrive is designed for individual user files while SharePoint is better for team-shared folders. You must decide which folders belong in OneDrive versus SharePoint before the migration starts.

Microsoft provides the Migration Manager tool in the SharePoint admin center to handle large-scale migrations. This tool uses lightweight agents installed on your file servers to scan, assess, and transfer files to Microsoft 365. You can schedule migrations in batches and monitor progress from a single dashboard.

OneDrive vs SharePoint: Where Should Files Go?

OneDrive is best for personal work files that only one person owns. Each user gets 1 TB of storage by default. SharePoint document libraries are designed for shared content that multiple team members need to edit. A common pattern is to map home drives (H: drives) to OneDrive and departmental shares (S: drives) to SharePoint. You can also use SharePoint for project-specific folders that require granular permission control.

Prerequisites Before Starting the Migration

Before you begin, verify that your Microsoft 365 tenant has enough licenses for all users. Each user needs a OneDrive for Business license included in Microsoft 365 Business Basic or higher. The file server must run Windows Server 2012 R2 or later and have network connectivity to Microsoft 365 endpoints. You also need at least 10 GB of free disk space on the server where the migration agent runs.

Review your current file server folder structure. Remove stale files older than three years and orphaned user folders. Reducing the data volume speeds up migration and lowers storage costs.

Steps to Plan and Execute a File Server to OneDrive Migration

Follow these steps to move file server data to OneDrive and SharePoint. The process assumes you have access to the SharePoint admin center and local administrator rights on the file server.

1. Inventory your file server shares
   Create a list of all shared folders on the file server. Note the folder name, path, size, number of files, and current NTFS permissions. Identify which folders contain personal user data and which are team or department data. Use a tool like the Microsoft 365 Migration Manager assessment or a PowerShell script to export this information.
2. Classify folders into OneDrive vs SharePoint destinations
   Map each folder to a destination. Personal folders such as home drives go to the corresponding user’s OneDrive root. Team folders go to a SharePoint document library. Create a mapping table with source path, destination type, destination URL, and target library name. For example, map \\fileserver\users\john.doe to John’s OneDrive and \\fileserver\marketing to a SharePoint site called Marketing.
3. Clean up and deduplicate files
   Delete temporary files, duplicates, and files older than the retention policy. Run a disk cleanup utility on the file server. Remove broken shortcuts and zero-byte files. This step reduces the total data volume and avoids transferring unnecessary files to the cloud.
4. Install and configure the Migration Manager agent
   Go to the Microsoft 365 admin center and navigate to SharePoint > Migration center > Migration Manager. Download and install the agent on the file server. Register the agent with your tenant using the provided key. The agent scans the file server and reports file metadata, permission details, and any blocking issues.
5. Create and run a migration task
   In the Migration Manager dashboard, select the source file server share and the destination OneDrive or SharePoint library. Choose the migration mode: staged or complete. Staged mode moves files in batches over several days. Complete mode moves all files at once and is suitable for smaller datasets. Set the migration schedule to run during off-peak hours to minimize network impact.
6. Map permissions during migration
   Enable the option to copy NTFS permissions to SharePoint. The Migration Manager translates NTFS ACLs into SharePoint permission groups. Group owners and members are recreated in SharePoint. For OneDrive, permissions are not copied because OneDrive files are private by default. Only the user gets access to their migrated personal folder.
7. Communicate the migration timeline to users
   Send an email to all affected users two weeks before the cutover date. Explain that their files will move to OneDrive and that they should sign in with their work account to access them. Provide a link to the OneDrive sync app download page. Include instructions on how to find files after migration.
8. Perform a test migration
   Select a small folder with representative data and run a test migration. Verify that all files appear in the correct OneDrive or SharePoint location. Check that permissions are applied correctly. Ask a test user to open a file and edit it. Resolve any issues before the full migration.
9. Execute the full migration and verify data
   Run the migration for all remaining folders. Monitor the Migration Manager dashboard for errors. After completion, spot-check 10 percent of the migrated folders. Confirm that file counts, sizes, and modification dates match the source.
10. Redirect user folders with Known Folder Move
    For users migrating from a home drive, enable Known Folder Move in the OneDrive sync app. This redirects Desktop, Documents, and Pictures to OneDrive. Users can access their files from any device without manually navigating to the OneDrive folder.

Common Migration Issues and How to Avoid Them

File Path Length Exceeds 400 Characters

OneDrive and SharePoint have a path length limit of 400 characters including the server and library name. Files with longer paths fail to upload. Before migration, scan for files with paths exceeding 256 characters on the file server. Shorten folder names or restructure deep hierarchies to stay under the limit.

Special Characters in File Names

OneDrive blocks files with characters like ~ # % & : < > ? / \ { | }. The Migration Manager automatically renames files containing these characters. Review the rename log after migration and notify users of any changes. You can pre-rename files on the file server using a PowerShell script to avoid surprises.

Permission Loss After Migration

If you do not enable permission migration in the task settings, all files become private to the user or the SharePoint site owner. Always select the option to copy NTFS permissions. For OneDrive migrations, permissions are not copied because OneDrive is a personal storage location. Users must reshare files manually after migration.

OneDrive vs SharePoint: Where to Migrate Each Folder Type

Item	OneDrive	SharePoint
Primary use	Personal files owned by one user	Team files shared among multiple users
Typical source	Home drives (H: or U: drives)	Departmental shares, project folders
Storage limit per user	1 TB default, up to 5 TB with admin override	25 TB per site collection default
Permission model	User is owner; sharing done per file or folder	Site groups with unique permission levels
Sync behavior	Syncs to user’s OneDrive folder	Syncs to SharePoint document library via sync button
Version history	500 major versions per file	500 major versions per file

Use this table to decide the destination for each file server folder. Personal folders with a single owner go to OneDrive. Shared folders with multiple editors go to SharePoint.

You now have a complete plan to migrate your file server to OneDrive and SharePoint. Start by running the inventory and cleanup steps. Then install the Migration Manager agent and run a test migration. After verifying the test results, schedule the full migration and redirect user folders with Known Folder Move. For advanced control, use the SharePoint Migration API to automate tasks across multiple servers in parallel.