OneDrive for Business file server migration troubleshooting for finance folders: misses files

When migrating finance folders from a file server to OneDrive for Business, you may discover that some files are missing after the migration completes. This problem usually occurs because of file name length limits, blocked file types, or permission mismatches that the migration tool does not report. This article explains the root causes of missing files during a finance folder migration, provides step-by-step troubleshooting steps, and covers related failure patterns you should check before and after the migration.

Why Finance Folder Migrations Miss Files

Finance folders often contain files with long descriptive names, nested subfolders, and special characters such as &, %, and #. OneDrive for Business and SharePoint Online enforce a maximum path length of 400 characters. Any file whose full path exceeds this limit is silently skipped by most migration tools. Additionally, certain file types are blocked by default in SharePoint and OneDrive, including executable files (.exe, .msi), script files (.ps1, .vbs), and archive types (.zip, .rar) when they contain blocked content. If finance staff stored scripts or compressed archives on the file server, those files will not appear in OneDrive after migration. Permission inheritance breaks also cause missing files: if a subfolder has unique permissions and the migration tool does not have explicit read access, the files inside that subfolder are omitted without a clear error.

File Path Length Limits

The maximum path length for a file stored in OneDrive or SharePoint is 400 characters. This includes the site URL, library name, folder path, and file name. For example, a finance folder path like Finance/Annual Reports/2024/Q1/Consolidated Financial Statements - Draft v2.xlsx can easily reach 200 characters before adding the site URL. If the full path exceeds 400 characters, the migration tool skips the file and logs a generic error. The file remains on the file server but is never uploaded.

Blocked File Types

SharePoint Online and OneDrive block over 200 file extensions by default. Finance departments sometimes use macro-enabled Excel files (.xlsm), password-protected archives (.zip with password), or custom finance software export formats (.prn, .qif). These extensions may be blocked at the tenant level or the site collection level. When a migration tool attempts to upload a blocked file, the file is rejected and the tool continues without retrying.

Permission Mismatches

File server permissions often use domain groups that do not exist in Microsoft 365. If the migration tool runs under a service account that lacks explicit read access to a subfolder, that subfolder and its contents are skipped. Finance folders frequently have unique NTFS permissions for auditors, controllers, and managers. A migration tool that inherits permissions from the parent folder will miss these subfolders entirely.

Steps to Identify and Fix Missing Files After Migration

1. Export the migration log
   Open your migration tool SharePoint Migration Tool or third-party tool. Locate the completed job and select Export Log. Save the CSV file. Open it in Excel and filter the Status column for Failed or Skipped. Look for error codes such as 0x80070057 invalid parameter or FileNotFound. Each row shows the source path and the reason for failure.
2. Check file path lengths against the 400-character limit
   In the exported log, sort the SourcePath column by character length. Use the formula =LEN(A2) in a new column to calculate path length. Any row with a path longer than 400 characters must be shortened. Rename the file or move it to a shallower folder on the source file server, then re-run the migration for that specific folder only.
3. Review blocked file types in the tenant
   Sign in to the Microsoft 365 admin center as a global admin. Go to SharePoint > Policies > Access control > Blocked file types. Compare the list with the file extensions in your finance folders. If you find blocked extensions like .exe, .ps1, or .zip, remove the block for your finance site collection only by creating a custom policy. Navigate to SharePoint > Active sites > select your finance site > Settings > Files and folders. Under Blocked file types, choose Custom and add only the extensions you need to allow.
4. Verify folder-level permissions on the source
   On the file server, open Windows File Explorer. Right-click the finance root folder and select Properties > Security > Advanced. Look for any folder that says Not Inherited. Click Add to give the migration service account Read access to that folder. Alternatively, run the migration tool with an account that has Full Control on the entire finance share.
5. Re-run the migration for the affected folders only
   In your migration tool, create a new job. Select only the source folders that had failures. Set the destination to the same OneDrive or SharePoint library. Enable the option to Overwrite existing files if the file content has changed. Run the job and monitor the log for new errors.

If OneDrive Still Has Issues After the Main Fix

OneDrive Shows a Red X on Shared Office Files

A red X on a file in OneDrive sync means the file failed to sync. This often happens when a finance file is open in another program or when the file name contains characters like a colon or asterisk. Close all Office applications. Rename the file on the source file server to remove invalid characters. Then re-run the migration for that file.

Finance Folders Are Empty After Migration

If an entire finance folder appears empty in OneDrive, the folder structure may have been created but the contents were skipped due to the 400-character limit on the folder path itself. Check the folder path length. For example, a path like Finance/Annual Reports/2024/Q1/Consolidated Financial Statements is 72 characters, which is fine. But if the folder is nested inside several layers of year and month folders, the combined path may exceed the limit. Flatten the folder structure by removing intermediate folders, then re-run the migration.

Files Are Present but Cannot Be Opened

Some finance files may upload successfully but fail to open because the file type is blocked for viewing. This occurs with macro-enabled Excel files .xlsm when macros are disabled at the tenant level. Go to the Microsoft 365 admin center > SharePoint > Policies > Access control > Blocked file types. Add .xlsm to the allowed list for the finance site. Users may need to close and reopen the file after the policy change.

File Server Permissions vs OneDrive Sharing: Key Differences

Item	File Server NTFS Permissions	OneDrive / SharePoint Permissions
Permission model	Access Control Entries ACE per user or group	Share permissions and site-level groups Owners, Members, Visitors
Inheritance	Inherited from parent folder by default	Inherited from parent folder, but unique permissions can be set
Breaking inheritance	Right-click > Properties > Security > Advanced > Disable inheritance	Library settings > Permissions for this document library > Stop Inheriting Permissions
Maximum path length	260 characters for most Windows systems	400 characters for file path including site URL
Blocked file types	None by default	Over 200 extensions blocked by default
Group type	Active Directory security groups	Microsoft 365 groups or Azure AD security groups

Now you can run a targeted re-migration for the missed finance files after checking path lengths, blocked extensions, and folder permissions. Use the migration tool log export as your primary diagnostic tool. For ongoing sync of shared finance folders, enable Files On-Demand in the OneDrive sync app settings under Sync and backup > Advanced settings. This prevents local disk space issues on finance team laptops. As an advanced tip, schedule a weekly PowerShell script using the SharePoint Online Management Shell to compare the source file server folder structure with the OneDrive library and generate a delta report of missing files.