OneDrive Admin Checklist: file server migration misses files for department moves

When a department moves from one file server to another, OneDrive sync can miss files. This happens because the migration tool copies files but does not update OneDrive’s sync metadata. File timestamps, folder IDs, or share paths change during the move. OneDrive then treats the files as new or skips them entirely. You need a checklist to verify that every file is present and syncing correctly after the migration.

Why File Server Migrations Cause OneDrive to Miss Files

When you move a department’s data from one server to another, the migration tool typically copies files and folders. The tool may change the internal file system IDs, timestamps, or share paths. OneDrive relies on these attributes to track which files it has already synced. If the attributes change, OneDrive may treat the files as new and re-upload them, or it may skip them because it thinks they are unchanged or duplicate. Additionally, if the migration tool does not preserve the folder structure exactly, OneDrive may fail to sync nested files. The result is that users in the department cannot find files that were present before the move.

Common Migration Tools and Their Behavior

Tools like Robocopy, SharePoint Migration Tool, or third-party solutions each handle file attributes differently. Robocopy with the /COPYALL flag preserves timestamps and security, but it does not update OneDrive’s sync database. The SharePoint Migration Tool maps file server paths to SharePoint document libraries, but it can miss files if the source path contains characters that SharePoint blocks. Third-party tools may change the folder GUID, which OneDrive uses to identify synced folders. If the GUID changes, OneDrive treats the folder as a new sync relationship.

Pre-Migration Checklist: Prepare the File Server and OneDrive

Before you start the migration, complete these steps to reduce the chance of missing files.

1. Run a full sync on the source server
   Ensure that all files in the department’s shared folder are synced to OneDrive. Open OneDrive settings and check the sync status. Resolve any errors before the migration.
2. Document the folder structure and file count
   Use File Explorer to export a list of all files and folders in the department share. Include file names, sizes, and last-modified timestamps. Save this list for comparison after the migration.
3. Check for blocked file types or characters
   Review the OneDrive admin center for file type restrictions. Rename any files that contain characters like # % & { } \ : ? < > | or leading/trailing spaces. OneDrive cannot sync these files.
4. Pause OneDrive sync on all department computers
   In the OneDrive sync app, right-click the OneDrive icon in the taskbar and select Pause syncing. This prevents sync conflicts while the migration is in progress.

Post-Migration Verification Steps

After the migration tool finishes copying files, follow these steps to verify that OneDrive has all files.

1. Compare file counts between source and destination
   Run a directory listing on the new server location. Compare the count of files and folders against the pre-migration list. Any discrepancy indicates missing files.
2. Check OneDrive sync status for each user
   Have each user in the department open OneDrive settings and go to Account > Choose folders. Confirm that the synced folders match the new server paths. If a folder is missing, select it again to resync.
3. Review the OneDrive activity log for errors
   Sign in to the OneDrive online portal. Navigate to My files and sort by the Activity column. Look for entries that say “sync pending” or “error.” Click each entry for details.
4. Check file version history
   Right-click a sample of files in File Explorer, select Properties, and go to the Previous Versions tab. If no versions appear, the migration may have overwritten the files without preserving history.
5. Run a test upload from the new location
   Ask one user to create a new file in the department folder on the new server. Confirm that the file appears in OneDrive and is accessible to other department members.

If OneDrive Still Misses Files After Migration

Even with careful preparation, some files may not appear. Here are the most common issues and how to resolve them.

Files with special characters that OneDrive blocks

OneDrive cannot sync files that contain characters like # % & { } \ : ? < > |. To find these files, run a PowerShell script that searches for these characters in the file names. Rename the files using a script or manually, then resync the folder.

Folder GUID changed during migration

OneDrive identifies synced folders by their internal GUID. If the migration tool changed the GUID, OneDrive treats the folder as new. To fix this, stop syncing the old folder in OneDrive settings, then add the new folder. This will re-sync all files.

File timestamps not preserved

If the migration tool set all files to the current date and time, OneDrive may think the files are new and re-upload them. This can cause duplicate files. Use Robocopy with the /COPYALL flag to preserve timestamps. If duplicates already exist, delete the copies from the OneDrive recycle bin.

User permissions not migrated

OneDrive respects NTFS permissions. If the migration did not copy the security descriptors, users may see a sync error that says “You don’t have permission to sync this folder.” Reapply the permissions from the source server using the Security tab in File Explorer.

File Server Migration vs OneDrive Sync: Key Differences

Item	File Server Migration	OneDrive Sync
Purpose	Move data from one server to another	Keep local and cloud files in sync
File tracking method	Uses file system attributes like GUID and timestamps	Uses internal database of file IDs and version history
Handles special characters	Most tools copy files regardless of characters	Blocks files with # % & { } \ : ? < > |
Preserves version history	Depends on tool flags like /COPYALL	Maintains up to 500 versions per file
Permission handling	Copies NTFS security descriptors if configured	Respects NTFS permissions but may show sync errors if they change

You now have a complete checklist to prevent and fix missing files during department moves. Start by running a full sync before the migration and documenting the file structure. After the migration, compare file counts and check the OneDrive activity log for errors. For persistent issues, use the OneDrive sync app’s Choose folders feature to re-select the migrated folder. As an advanced tip, use the SharePoint Migration Tool with the /MigrateOneDrive flag to automatically map file server paths to OneDrive sync folders.