How to Move Your Small Business Files from an Old File Server to SharePoint Online
Summary
This guide helps you troubleshoot and resolve: How to Move Your Small Business Files from an Old File Server to SharePoint Online. Follow the steps below to fix the issue.
Common Causes
Moving your small business files from an on-premise file server to SharePoint Online provides your team with secure, remote access to business documents from any device. This migration centralizes your data in the Microsoft 365 cloud, enabling real-time collaboration and removing the need to maintain physical server hardware in your office.
SharePoint Online is ideal for team collaboration and departmental file storage. If your staff require personal cloud storage for individual working files that are not shared with colleagues, consider OneDrive for Business instead. For most small business migrations, SharePoint document libraries provide the best balance of shared access and centralised management.
Prerequisites
Before starting your migration, ensure the following requirements are met:
- An active Microsoft 365 tenant is configured.
- Users have valid Microsoft 365 licenses that include SharePoint Online.
- A machine running Windows 10 or Windows Server with network access to both the source file server and the internet.
- The SharePoint Migration Tool (SPMT) downloaded from the official Microsoft Download Center.
Migration Steps
- Plan your SharePoint site and document library structure.
- Audit and clean up your existing file server data.
- Create SharePoint sites and document libraries.
- Install and configure the SharePoint Migration Tool.
- Run the initial migration and perform delta syncs.
- Recreate permissions manually in SharePoint.
- Sync libraries using the OneDrive sync client.
- Verify data integrity and notify users.
- Decommission the old file server and apply retention policies.
Detailed Instructions
1. Plan Your SharePoint Structure
Before migrating, decide how your files will be organized in SharePoint. We recommend creating a top-level site for your organization and separate document libraries for each department, such as Finance, HR, and Operations.
- Sign in to the SharePoint admin center at
https://admin.microsoft.com/sharepoint. - In the left-hand navigation, select Sites > Active sites.
- Click Create and choose Team site or Communication site.
- Enter the site name, description, and add members who require access to shared files.
- Inside the site, navigate to the Documents library or create new document libraries for each department.
2. Prepare Your File Server
Migrating unnecessary data increases migration time and clutters your cloud storage.
- Review your current network shares and identify files that have not been accessed in several years.
- Move archival data to a separate folder or external drive if it does not need to be in SharePoint.
- Close all files and ensure no users are actively editing documents during the migration window.
- Identify and exclude open database files (such as .mdb, .accdb, or .sql files) and Outlook PST files, as these cannot be migrated reliably while in use.
- SharePoint has a maximum file path length of 400 characters. Shorten deeply nested folder names before migrating.
- The maximum file size is 15GB per file. Split or archive any files larger than this limit.
- SharePoint does not support certain special characters in file and folder names, including
",*,:,<,>,?,/,\\, and|. Rename files containing these characters before migration. - The SharePoint Migration Tool does not automatically map NTFS permissions to SharePoint permissions. You must manually recreate access controls in SharePoint after migration.
3. Install the SharePoint Migration Tool
Microsoft provides a free utility called the SharePoint Migration Tool (SPMT) designed specifically for moving file shares to SharePoint Online.
- Download the SharePoint Migration Tool from the official Microsoft Download Center.
- Install the application on a machine with a stable connection to both your file server and the internet.
- Launch the tool and sign in with your Microsoft 365 Global Administrator account.
4. Run the Migration
- Select File share as the source type.
- Enter the file path of your source folder (e.g.,
\\Server\\SharedDocs). - Select the destination SharePoint site and document library you created earlier.
- Review the mapping and click Migrate.
- Monitor the progress in the SPMT dashboard. Once complete, review the migration report for any failed files.
5. Delta Migration and Incremental Sync
For large file servers, run an initial migration during a quiet period, then perform a delta migration to capture only files that changed since the first transfer. This minimises downtime during the final cutover.
- Run the initial full migration outside business hours.
- Allow staff to continue working on the file server during business hours.
- Run a delta migration immediately before decommissioning the old server to synchronise new and changed files.
- Schedule the final delta sync for a weekend or after-hours window to ensure no data is missed.
6. Sync SharePoint Libraries with OneDrive
To help staff adjust, you can sync SharePoint libraries to Windows File Explorer using the OneDrive sync client.
- Open your SharePoint document library in a web browser.
- Click Sync to open the OneDrive sync client.
- Follow the prompts to sign in and sync the library to your computer.
- Once synced, the SharePoint library appears in File Explorer under your organization's name.
7. Recreate Permissions and Notify Users
After migration, confirm that staff can access the files they need. Remember that NTFS permissions are not carried over automatically.
- In SharePoint, select the document library and click Settings > Library settings.
- Choose Permissions for this document library and stop inheriting permissions from the parent site if unique access controls are required.
- Grant Read, Edit, or Full Control permissions to the appropriate Microsoft 365 groups or individual users.
- Ask department heads to verify their teams can open, edit, and save documents.
- Provide staff with a short guide on accessing SharePoint via the web browser and the OneDrive sync client.
8. Post-Migration Decommissioning and Retention
- Keep the old file server online in read-only mode for at least 14 days as a rollback fallback.
- Compare critical folders between the source server and SharePoint to verify data integrity.
- Apply SharePoint retention policies or labels to document libraries to meet your business compliance requirements.
- Once you are confident the migration is complete, decommission the old file server hardware or repurpose it for other workloads.
Troubleshooting
Migration fails due to file path length
SharePoint has stricter limits on file path lengths than traditional Windows file servers.
- Shorten folder names to reduce the overall path length.
- Move files closer to the root of the source folder before migrating.
- Ensure the full path, including the file name, does not exceed 400 characters.
Unsupported file name characters
SPMT may skip files containing characters not supported by SharePoint.
- Rename files to remove
",*,:,<,>,?,/,\\, and|. - Re-run the migration for the affected folders only.
File size limit exceeded
SharePoint Online supports a maximum file size of 15GB per file.
- Split large files into smaller archives or move them to alternative storage if they exceed 15GB.
- Check the SPMT migration report for files that failed due to size restrictions.
Common SPMT error codes
- Error 403: Access denied. Verify the account running SPMT has Global Administrator rights and Read permissions on all source folders.
- Error 409: Conflict. A file or folder with the same name already exists in the destination. Rename the source item or choose a different destination library.
- Error 500: Internal server error. Wait a few minutes and retry the migration, or check Microsoft 365 service health.
- Error 503: Service unavailable. Reduce the number of concurrent migration tasks and retry during off-peak hours.
Permission errors during transfer
If the migration tool cannot access certain folders, it may be due to NTFS permissions on the source server.
- Ensure the account running the SharePoint Migration Tool has Read permissions for all source folders.
- Verify that the destination user has Contribute or Edit permissions on the SharePoint site.
Files not syncing after migration
If files appear in SharePoint but not in the local sync client:
- Restart the OneDrive sync client.
- Check for special characters in file names that SharePoint does not support.
- Ensure the user has a valid Microsoft 365 license assigned.
If you encounter issues that cannot be resolved using these steps, Open a Ticket.
Still Having Issues?
💻 Open a Ticket