How to migrate office files from an old server without downtime
Summary
This guide helps you troubleshoot and resolve: How to migrate office files from an old server without downtime. Follow the steps below to fix the issue.
Common Causes
How to migrate office files from an old server without downtime
Moving from traditional network shares or NAS devices to Microsoft 365 allows your team to collaborate in real time, access files from any device, and eliminate version control headaches. This guide walks you through migrating your office files to SharePoint Online and OneDrive for Business with minimal disruption to your small business operations.
Pre-migration communication plan
Small businesses cannot afford surprises during a migration. Notify all staff at least one week before the migration begins.
- Send an email to all staff explaining the move from the old file server to SharePoint Online and OneDrive for Business.
- State the migration dates, the cutover date, and what staff need to do to prepare.
- Identify a "migration champion" in each department who can answer basic questions and escalate issues.
- Post reminders in your team chat channel two days before and on the morning of the cutover.
- Advise staff to save any urgent work to their local desktop before the cutover window begins.
Step 1: Audit your current file server
- Log in to your existing file server or NAS device using an administrator account.
- Review all shared folders and identify which ones are still in active use.
- Note any folders with broken permissions, orphaned files, or outdated data that can be archived rather than migrated.
- Document the current folder hierarchy so you can replicate it in SharePoint Online.
- Identify files that are actively being edited so you can plan a delta migration for those items later.
Step 2: Plan your SharePoint site structure
- Open a web browser and sign in to the Microsoft 365 admin centre at
https://admin.microsoft.com. - In the left navigation, expand Admin centres and select SharePoint.
- In the SharePoint admin centre, select Active sites from the left menu.
- Click Create and choose Team site to create a new site for each department or major project group.
- Use a consistent naming convention, such as
Finance-DocumentsorMarketing-Assets. - Inside each site, select Documents from the left navigation to create document libraries that mirror your old folder structure.
- Avoid creating too many nested folders; SharePoint works best with flat structures and metadata.
Step 3: Map permissions and access groups
- Review the NTFS permissions on your existing file shares.
- In the Microsoft 365 admin centre, go to Teams & groups > Active teams & groups and create Microsoft 365 groups that match your existing access levels.
- Alternatively, in the SharePoint admin centre, select a site, click Permissions, and create SharePoint groups for granular access.
- Assign Members to staff who need edit access and Visitors to staff who need read-only access.
- For sensitive folders, break inheritance and use unique permissions rather than inheriting from the parent site.
Step 4: Perform the initial migration
- Download the SharePoint Migration Tool from the Microsoft Download Centre.
- Run the installer and follow the prompts to complete installation on a workstation with access to both the old server and the internet.
- Launch the SharePoint Migration Tool and sign in with your Microsoft 365 administrator account.
- Select File share as the source type.
- Enter the source file share or NAS path, for example
\\ServerName\SharedFolder. - Select SharePoint site or OneDrive for Business as the destination.
- Enter the destination URL and select the target document library.
- Map your source folders to the corresponding SharePoint libraries.
- Click Add to create the migration task, then click Run to start the initial data transfer.
- Monitor the migration log for any failed files or permission errors.
Step 5: Perform delta migrations for active files
To achieve near-zero downtime, you must migrate changes made to files after the initial transfer but before cutover.
- While staff continue working on the old server, run the SharePoint Migration Tool again using the same source and destination.
- The tool compares timestamps and migrates only new or changed files (delta files) since the last run.
- Schedule delta migrations daily or every few hours during the week leading up to cutover.
- Keep a log of each delta run to confirm all active files are captured.
Step 6: Coordinate the cutover date
- Select a cutover date that falls on a quiet day, such as a Friday afternoon or a public holiday, to minimise disruption.
- Confirm the date with all department heads and add it to the company calendar.
- On the cutover day, place the old file server into read-only mode. Remove write permissions for all users except the migration administrator.
- Run a final delta migration to capture any last-minute changes.
- Once the final delta is complete, update any mapped network drive shortcuts or bookmarks to point to the new SharePoint libraries or OneDrive locations.
- Notify staff that the old server is now read-only and that all new work should be saved to SharePoint Online or OneDrive for Business.
Step 7: Transition users to OneDrive and SharePoint
- Ask staff to save personal working files to OneDrive for Business instead of their local
C:\Users\profile or desktop. - Direct team collaboration files to the relevant SharePoint document library.
- Show users how to sync SharePoint libraries to File Explorer using the OneDrive sync client.
- Demonstrate co-authoring: multiple staff can open the same Word or Excel file in Microsoft 365 apps and edit simultaneously.
- Explain version history: users can click File > Info > Version History to view and restore previous versions.
User training schedule
- Week 1 before migration: Send a short guide explaining where to find files in SharePoint and OneDrive.
- Day of cutover: Hold a 30-minute team walkthrough showing how to open, edit, and sync files.
- Week 1 after migration: Offer drop-in sessions for staff who need help with the OneDrive sync client or co-authoring.
- Week 2 after migration: Send a follow-up email with links to Microsoft 365 training resources and a reminder about version history.
Step 8: Decommission the old server
- Keep the old server online in read-only mode for at least two weeks after migration.
- Verify that all critical files are accessible in SharePoint and OneDrive.
- Confirm that staff no longer rely on mapped network drives before powering down the old hardware.
- Archive the old server data according to your organisation's data retention policy.
Rollback plan
If critical issues arise after cutover, you can roll back to the old server.
- Communicate the rollback to all staff immediately via email and team chat.
- Restore write permissions on the old file server shares.
- Reconnect mapped network drives to the old server paths.
- Advise staff to save new work to the old server until the issue is resolved.
- Investigate the SharePoint or OneDrive issue, then plan a new cutover date once it is fixed.
Unsupported file names and characters
SharePoint Online does not support certain characters in file or folder names. Files containing these characters will fail to migrate.
- Double quote:
" - Asterisk:
* - Colon:
: - Less than:
< - Greater than:
> - Question mark:
? - Forward slash:
/ - Backslash:
\ - Pipe:
|
SharePoint also has a limit of 400 characters for the full file path, including the site URL and library name.
Troubleshooting
SharePoint Migration Tool installation fails
- Ensure the workstation meets the minimum system requirements for the SharePoint Migration Tool.
- Run the installer as an administrator.
- Temporarily disable third-party antivirus software during installation, then re-enable it afterwards.
- Check that .NET Framework is installed and up to date on the migration workstation.
- Review the installation log in
%TEMP%for specific error codes.
Authentication errors during migration
- Confirm you are signing in with a Microsoft 365 administrator account that has access to the target SharePoint site.
- Check that multi-factor authentication is not blocking the connection; use an app password if required.
- Verify that the migration account has read access to the source file share or NAS path.
- Clear cached credentials in Windows Credential Manager and sign in again.
Large file upload failures
- SharePoint has a maximum file size limit of 250 GB per file, but smaller limits may apply depending on your browser and network connection.
- Split very large files into smaller parts or compress them before migration if possible.
- Ensure the migration workstation has a stable, high-speed internet connection.
- Pause other large downloads or cloud backups on the network during the migration.
- Check the migration log for timeout errors and retry the failed files individually.
Files fail to migrate
- Check that file names do not contain unsupported characters such as
",*,:,<,>,?,/,\, or|. - Ensure file paths are not too long; SharePoint has a limit of 400 characters for the full file path.
- Verify that the migration account has read access to the source folder.
Users cannot access migrated files
- Confirm the user has been added to the correct SharePoint group or Microsoft 365 group.
- Check that the user has the appropriate licence assigned in the Microsoft 365 admin centre.
- Ask the user to clear their browser cache or sign out and sign back in to Office apps.
Sync conflicts in OneDrive
- If a conflict occurs, OneDrive creates a separate copy. Users should compare versions and save the correct one.
- Ensure the OneDrive sync client is up to date.
Version history is missing
- Version history must be enabled on the SharePoint document library.
- Go to Library Settings > Versioning settings and ensure Create major versions is selected.
- Older files migrated without history may not show previous versions; this is expected for content moved from a legacy file server.
If you need assistance with your migration, Open a Ticket.
Still Having Issues?
💻 Open a Ticket