Move the shared drive to SharePoint without the chaos

The short answer

To migrate a file server to SharePoint, clean up the shared drive first, then map each top-level folder to a SharePoint site or document library based on who needs access, not on the old folder tree. Check the drive against SharePoint limits, such as the 400-character path limit and blocked characters. Use Microsoft’s free tools, Migration Manager or the SharePoint Migration Tool, to copy the data, run incremental passes to catch changes, and cut over on a weekend by making the old share read-only. Personal files go to each person’s OneDrive. Train staff on the new locations before Monday.

Step 1: take inventory and clean up

Every shared drive carries years of clutter. Moving it all costs time and storage and makes search worse.

• Report total size, file count, largest folders and files not opened in years.
• Ask each department head what can be archived or deleted. Keep anything your retention rules require.
• Find duplicate copies, old installers, PST files and backups stored on the share.
• Identify personal folders and home drives. These belong in each person’s OneDrive, not in a team site.
• Flag files used by applications, such as desktop databases or linked spreadsheets. They may not behave the same in the cloud.

Check the total against your storage. Microsoft 365 business plans include 1 TB of SharePoint storage per organization plus 10 GB per license, according to Microsoft’s service limits. Extra storage can be bought, but cleaning up is cheaper.

Step 2: design sites around permissions

The most common mistake is recreating the server’s folder tree inside one giant SharePoint library. Design around who needs access instead.

• One site per team or function that has its own audience: Finance, HR, Operations, Sales, Projects.
• Libraries within a site for major content types, such as Contracts and Invoices within Finance.
• Shallow folders. Two or three levels, not eight. Use metadata or separate libraries instead of deep nesting.
• Permissions at the site or library level, through Microsoft 365 groups, not on individual folders and files.

Microsoft’s limits back this up. When a list, library or folder holds more than 100,000 items, you can no longer break or restore permission inheritance on it, and Microsoft recommends staying under 5,000 unique permissions per library. Broken permissions on hundreds of subfolders are the main reason SharePoint migrations turn messy.

Step 3: check the limits and fix problems

Scan the share for issues before migration, not during it. According to Microsoft’s documentation:

• The full decoded path, including folder names and file name, cannot exceed 400 characters.
• Individual files can be up to 250 GB.
• Certain characters, such as quotation marks, asterisks, colons, angle brackets, question marks, slashes and pipes, and reserved names such as CON, PRN, AUX and desktop.ini are not allowed in file and folder names. Spaces at the start or end of a name are not allowed either.
• For good sync performance, Microsoft recommends syncing no more than 300,000 files across the libraries a user syncs.

Long paths are the usual problem. Shortening a few top-level folder names often fixes thousands of files at once. The 300,000-file guidance is why some teams should use the browser or Teams for large archives rather than syncing everything to their laptop.

Step 4: choose the migration tool

Both copy files rather than move them. Microsoft notes that source files are not deleted, so the old server stays intact as a fallback. Both support re-running a job to copy only what changed since the last pass. For personal Desktop and Documents folders, Microsoft’s Known Folder Move redirects them to OneDrive automatically. Third-party tools exist for complex permissions or very large data sets, but most small businesses never need them.

Step 5: pilot, then copy in passes

1. Pilot one department. Migrate a small team’s library and let them work in it for a week. Fix structure and permission issues before the rest.
2. Bulk copy. Run the main copy during the work week while people keep using the server. Large drives can take days depending on upload speed.
3. Review the reports. Both tools report failed files. Fix names, paths and permissions, then rerun.
4. Incremental passes. Re-run the jobs to pick up changes. Each pass gets shorter.

Want a second opinion before you start? Our free Technology Health Assessment takes 30 minutes of data collection and gives you a plain-language report the next day on IT operations, applications, integration and business continuity, with a short list of next steps in order.

Step 6: cut over in one weekend

1. Friday evening, set the old share to read-only so nobody saves to the wrong place.
2. Run the final incremental pass.
3. Spot-check folders in each library against the source: counts, a few files opened, permissions tested with a regular user account.
4. Remove old mapped drives from computers and add SharePoint shortcuts or sync for the libraries each team uses.
5. Keep the server read-only for 30 to 60 days, then archive a final backup and retire it.

Common migration mistakes

• Copying the mess. Moving ten years of clutter makes search worse and fills storage you pay for.
• One library for everything. It hits permission and sync limits and confuses users.
• Folder-level permissions everywhere. They are hard to audit and break easily. Use separate sites or libraries instead.
• Syncing every library to every laptop. Sync only what each person uses daily.
• Forgetting linked files. Spreadsheets that link to other spreadsheets by drive letter will break. Find and update them during the pilot.
• No communication plan. Tell people the cutover date a week ahead, the day before and on Monday morning.

Step 7: train people and set backup

• Give each team a one-page guide: where their files live, how to sync, how to share with a link and how to restore a previous version.
• Explain the difference between OneDrive for personal work and SharePoint for team files.
• Review external sharing settings in the SharePoint admin center before people start sending links.
• Add a third-party backup for Microsoft 365. Version history and the recycle bin help, but they are not a full backup.

JLB USA provides managed IT for businesses with roughly 25 to 100 employees, including Microsoft 365 administration, file migrations, and backups with tested restores. Before you open SharePoint to the whole team, review our guide to Microsoft 365 security settings.

Keep reading

• SharePoint vs OneDrive: where should your business files live?
• Microsoft 365 Business Standard vs Premium: which plan should you buy?
• On-premise server vs cloud: should a small business keep the office server?
• How much do managed IT services cost per month in 2026?

Related services

• Managed IT services
• Free Technology Health Assessment
• Microsoft 365 security settings
• Backup and disaster recovery