OneDrive Admin Checklist: file server migration misses files for engineering files

When you migrate engineering files from a file server to OneDrive, some files may not transfer. This happens because engineering file types such as CAD drawings, 3D models, and simulation outputs often have long paths, special characters, or file locks that OneDrive does not handle by default. The OneDrive sync engine skips files with paths longer than 400 characters and files that contain certain characters like double quotes or pipe symbols. This article explains why these files get missed and provides a step-by-step admin checklist to locate and move every engineering file successfully.

ADVERTISEMENT

Why Engineering Files Get Missed During a File Server Migration

OneDrive for Business uses the same sync engine as the consumer version. That engine has built-in rules that skip files that could cause sync errors. Engineering files are more likely to trigger these rules because of their naming conventions and folder structures.

Path Length Limit

OneDrive cannot sync files whose full path exceeds 400 characters. Engineering projects often use deep folder hierarchies: Project > Subassembly > Part > Revision > CAD file. A path like \server\projects\A380\Wing\Flap\Rev03\Flap_assy_v3.SLDPRT can easily exceed 400 characters. OneDrive silently skips these files without showing an error in the sync status.

Invalid Characters

The OneDrive sync engine blocks files whose names contain any of these characters: ", |, , ?, <, >, :, \, /. Engineering files sometimes include these characters in version notes or revision tags, for example: Part_v2.1 (final).step. The parentheses are allowed, but a colon or pipe character will cause the file to be skipped.

File Locks from Engineering Applications

CAD, CAM, and simulation software often hold file locks while the file is open. OneDrive sees a locked file as inaccessible and skips it. If users leave engineering applications open overnight, the migration process will miss those files. The sync engine does not retry locked files automatically.

Admin Checklist to Find and Move Missing Engineering Files

Use this checklist before, during, and after the migration to ensure no engineering file is left behind.

Before Migration: Scan the File Server

1. Run the OneDrive Path Length Checker
   Download the Microsoft-provided Path Length Checker tool from the Microsoft 365 admin center. Point it to the root folder of your engineering data. The tool exports a CSV list of all files whose paths exceed 400 characters. Review the list and decide whether to shorten folder names or move files to a shallower folder structure.
2. Identify files with invalid characters
   Run a PowerShell script that scans the file server for names containing ", |, , ?, <, >, :, \, or /. Use this command in an elevated PowerShell window: Get-ChildItem -Path "\\server\engineering" -Recurse | Where-Object { $_.Name -match '["|?<>:\\/]' } | Export-Csv "invalid_chars.csv". Rename those files before migration.
3. Check file extensions blocked by OneDrive
   OneDrive blocks sync of certain file types by default. Go to the Microsoft 365 admin center > Settings > Org settings > OneDrive > Sync. Under "Block syncing of specific file types," review the list. Engineering extensions like .SLDPRT, .STEP, .IGS, .STL, and .DWG are not blocked by default, but verify that your custom extensions are not in the block list.

During Migration: Use the SharePoint Migration Tool

1. Use the SharePoint Migration Tool instead of drag-and-drop
   Do not drag files from the file server to the OneDrive folder. The SharePoint Migration Tool SPMT handles long paths and retries locked files. Download SPMT from the Microsoft 365 admin center. Set the source to your file server share and the destination to the target OneDrive or SharePoint document library.
2. Enable the SPMT setting for long file paths
   In SPMT, go to Settings and check "Enable migration of files with long paths." This tells the tool to truncate paths automatically where possible or report them for manual review.
3. Schedule migration during off-hours
   Set the SPMT job to run after business hours when engineering applications are closed. This reduces the number of locked files. If you cannot schedule off-hours, ask users to close all CAD and simulation software before the migration window.

After Migration: Verify and Recover Missing Files

1. Compare file counts between source and destination
   Run a PowerShell script that counts files in the source folder and in the OneDrive sync folder. Export both counts to a CSV and look for discrepancies. Use this command on the source: Get-ChildItem -Path "\\server\engineering" -Recurse -File | Measure-Object | Select-Object Count. Run the same command on the destination folder.
2. Check the SPMT migration report
   After the SPMT job completes, open the report. It lists every file that failed to migrate and the reason. Look for entries with error codes like "PathTooLong" or "FileLocked." Address each failed file manually.
3. Manually upload remaining files via OneDrive web
   For files that SPMT could not migrate, use the OneDrive web interface. Open the target folder in a browser, click Upload > Files, and select the problematic files. The web uploader handles paths up to the SharePoint limit of 400 characters and shows a clear error if the file still fails.

If Engineering Files Are Still Missing After Migration

OneDrive Shows Sync Pending for Engineering Files

This usually means the file is still open in an application. Ask the user to close the CAD or simulation program. If the file remains pending for more than 24 hours, restart the OneDrive sync by right-clicking the OneDrive icon in the system tray and selecting Pause syncing, then Resume syncing.

OneDrive Reports a File Name Conflict

Engineering teams sometimes have files with identical names in different folders. OneDrive renames the second file by adding a number in parentheses. Check the migration report for files that were renamed. Notify users so they can update references in assemblies or drawings.

OneDrive Skips Files with Revision Numbers in Parentheses

Parentheses are allowed in OneDrive file names, but some engineering naming conventions use parentheses in a way that triggers sync issues. For example, Part_(v2).SLDPRT is fine, but Part_(v2) [final].SLDPRT may cause a sync error because of the square brackets. Rename files to remove square brackets, curly braces, and percent signs before uploading.

Item	OneDrive Sync Engine	SharePoint Migration Tool SPMT
Path length limit	400 characters	400 characters with truncation option
Special character handling	Blocks 9 characters	Reports invalid characters; does not block
Locked file retry	No automatic retry	Retries up to 3 times
File type block list	Admins can block extensions	Migrates all file types unless blocked by tenant policy
Reporting on skipped files	No detailed report	CSV report with error codes

After following this checklist, you can identify every engineering file that was missed and move it to OneDrive successfully. Start by running the Path Length Checker on your file server. Then use SPMT with the long path setting enabled. Finally, verify the file count and manually upload any remaining files through the OneDrive web interface. An advanced tip: use the Microsoft 365 admin center > Reports > Usage > OneDrive to monitor sync health across your engineering team for two weeks after migration.