Home › Knowledgebase › KB-1202

How to migrate files from office server to sharepoint

Summary

This guide helps you troubleshoot and resolve: How to migrate files from office server to sharepoint. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Plan your migration

Before moving any data, audit what is actually on your server or NAS. Many small businesses discover old backups, duplicate folders, and files that no one has opened in years. Cleaning this up first reduces migration time and keeps your SharePoint site tidy.

  1. Map your current network shares and identify which folders are actively used.
  2. List all current shared drives and their top-level folders.
  3. Identify redundant, obsolete, or trivial (ROT) data that can be archived or deleted before migration to save storage space.
  4. Sort by date modified to identify files that have not been opened in years. Move these to an archive folder rather than migrating them.
  5. Decide on a SharePoint site structure. For most small businesses, one team site per department works well (for example, Administration, Sales, Operations).
  6. Determine who needs access to each folder. SharePoint permissions are easier to manage when you assign them to Microsoft 365 groups rather than individual users.
  7. Document current NTFS or share permissions so you can replicate them in SharePoint.
  8. Choose a migration window outside of business hours to avoid disrupting staff.
  9. Check your Microsoft 365 subscription to ensure you have sufficient SharePoint storage for the data you plan to migrate. Note that storage quotas vary by licence and tenant, and Multi-Geo considerations may apply if your organisation stores data in specific geographic regions.
  10. Communicate with staff about the migration timeline and provide training on accessing files via OneDrive and SharePoint.
  11. Ensure the administrator account performing the migration is protected by multi-factor authentication (MFA) and complies with your organisation's conditional access policies.

Tip: Use descriptive site and library names. Staff are more likely to adopt SharePoint if the folder names match the language they already use in the office.

Prepare your source data

  1. Log on to your file server or NAS with an account that has administrative rights to the folders you plan to migrate.
  2. Open File Explorer and browse to the network drive or NAS share containing your business files.
  3. Review file names for characters that SharePoint does not support, such as #, %, &, *, :, <, >, ?, /, \, |, and ~. Rename any affected files before migrating.
  4. Check file path lengths. SharePoint has a combined URL and file name limit of 400 characters. Shorten deeply nested folder paths where possible.
  5. Ensure individual files are under the SharePoint limit of 250 GB, and avoid syncing more than 300,000 files in a single library for best performance.
  6. Close any open files and ensure no users are actively editing documents in the folders you are about to move.

Caution: Do not migrate files while staff are actively working in them. Open files can be skipped or locked, leading to incomplete transfers and version conflicts.

Create the SharePoint destination

  1. Sign in to Office.com with your Microsoft 365 business account.
  2. Select the SharePoint app from the Microsoft 365 app launcher.
  3. Click Create site and choose Team site for departmental collaboration or Communication site for organisation-wide news and resources.
  4. Enter a site name, such as Company Files or Projects, and complete the creation wizard.
  5. Inside the new site, select Documents from the left navigation.
  6. Click New, choose Folder, and recreate your top-level folder structure (for example, Finance, HR, Projects, Templates).
Use folders sparingly. SharePoint supports metadata and custom columns, which often make finding files easier than digging through nested subfolders.

Choose your migration method

For small businesses, the most practical approaches are manual upload through a web browser, synchronisation using the OneDrive sync app, or the SharePoint Migration Tool for larger volumes.

Option A: Manual upload via SharePoint in a browser

Best for smaller volumes of data or when you want to reorganise folders as you go.

  1. Open Microsoft Edge, Chrome, or Safari and sign in to office.com with your Microsoft 365 business account.
  2. Select the SharePoint app from the Microsoft 365 app launcher.
  3. Open the destination site and document library where you want the files to live.
  4. Click Upload and choose Files or Folder.
  5. Select the files or folders from your local server or mapped network drive and click Upload.

Option B: Sync with OneDrive and copy files

Best for smaller volumes and for preserving folder structures more easily. The OneDrive sync app is not designed for bulk copying from file shares to SharePoint. For large server-to-SharePoint migrations, it can hit throttling or performance issues, and the SharePoint Migration Tool is recommended instead.

  1. Install the OneDrive sync app on a Windows PC that has access to your file server.
  2. Sign in with your Microsoft 365 account and sync the target SharePoint document library to your computer.
  3. Open File Explorer and locate the synced SharePoint folder.
  4. Open a second File Explorer window and browse to your source server or NAS share.
  5. Copy the folders and files from the server and paste them into the synced SharePoint folder in File Explorer.
  6. OneDrive will upload the changes to SharePoint automatically. You can monitor progress in the OneDrive activity centre.

Option C: SharePoint Migration Tool

Best for very large volumes of data or complex folder structures. The SharePoint Migration Tool is a free Microsoft utility that can migrate file shares directly to SharePoint Online and is the recommended method for server migrations.

  1. Download and install the SharePoint Migration Tool from the Microsoft Download Center.
  2. Sign in with your Microsoft 365 global administrator or SharePoint administrator account.
  3. Create a new migration task and select File Share as the source.
  4. Specify the source folder path on your file server and the destination SharePoint site and document library.
  5. Run the migration and monitor progress in the tool dashboard.

Tip: If you are migrating a large volume of data, copy in batches rather than all at once. This makes it easier to spot errors and avoids overwhelming your internet connection.

Do not disconnect the network drive or shut down the source PC until the sync status shows all files have uploaded. Interrupting the transfer can result in incomplete files.

Set permissions and sharing

NTFS permissions do not automatically carry over to SharePoint. You must recreate permissions in SharePoint using Microsoft 365 groups and SharePoint sharing settings.

  1. In SharePoint, open the document library containing your migrated files.
  2. Select a folder or file, then click Manage access.
  3. Click Grant Access and add the Microsoft 365 groups or individuals who need permission.
  4. Choose the appropriate permission level: Can edit for staff who need to modify documents, or Can view for read-only access.
  5. Remove Everyone or broad legacy permissions that existed on the old server but are not appropriate for cloud collaboration.
  6. Review permission inheritance. By default, folders inherit permissions from the parent library; break inheritance only when you need unique permissions for specific folders.

Caution: Avoid sharing individual files with external guests unless necessary. Use SharePoint site membership for internal staff and specific file sharing only for trusted external partners.

Train your team on co-authoring

The biggest change for staff is moving from "save and email" to real-time collaboration. Run a short session covering the following:

Tip: Encourage staff to work directly from SharePoint rather than downloading copies to their local desktop. This ensures everyone is collaborating on the same version and reduces the risk of duplicate files.

Verify the migration and cut over

  1. Compare file counts between the source server and the SharePoint destination library to confirm all data has transferred.
  2. Spot-check random files across different folders to verify they open correctly and contain the expected content.
  3. Check file sizes and last modified dates on a sample of migrated documents to confirm data integrity.
  4. Set the source server or NAS to read-only for a defined fallback period, such as two weeks, so staff cannot create new files in the old location while you confirm the migration is complete.
  5. Communicate the official cut-over date to staff and instruct them to save all new and edited files to SharePoint only after that date.
  6. After the fallback period ends, decommission or repurpose the source server according to your organisation's data retention policy.

Troubleshooting common issues

File name errors

SharePoint blocks certain characters in file and folder names, including #, %, &, *, :, <, >, ?, /, \, |, and ~. If a migration fails, review the error log for invalid characters, rename the affected files on the source server, and retry the transfer.

Path length errors

SharePoint limits the combined URL and file name to 400 characters. Deeply nested folder structures often exceed this limit. Shorten folder names or flatten the directory structure before migrating, then restart the migration task for the affected folders.

Sync conflicts

When using the OneDrive sync app, conflicts occur if the same file is edited in two locations at once. OneDrive creates a separate conflict copy. Open both versions, merge the necessary changes, save the correct file to SharePoint, and delete the duplicate conflict copy.

Permission inheritance problems

If staff cannot access migrated folders, check whether permission inheritance has been broken unintentionally. In SharePoint, select the folder, click Manage access, and review the advanced permissions settings. Restore inheritance from the parent library or assign the correct Microsoft 365 group as needed.

Large file upload failures

Individual files larger than 250 GB cannot be uploaded to SharePoint. Very large files may also fail due to network timeouts or throttling. Compress or split oversized files where possible, or use the SharePoint Migration Tool, which handles large transfers more reliably than browser uploads or OneDrive sync.

If you need further assistance with your migration, Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket