A good SharePoint migration plan for a small business comes down to five jobs, done in order: decide what is worth moving, scan and tidy it, design where it will live, test with a small pilot, then move the rest in waves while keeping your team informed. Skip the first three and you simply copy a messy shared drive into a shinier home. We set up and manage Microsoft 365 for small businesses, so this is the plan we would hand a friend who runs a ten-person firm and wants their files off an old server or a pile of shared folders.
TL;DR
- Migration is mostly preparation. Decide what to move, what to archive and what to bin before you copy anything.
- Run a scan-only check first, so file names, path lengths and permissions problems show up before they stop a transfer.
- Design the target (sites, libraries, who sees what) on paper, then pilot with one team and a few real users.
- Move in waves outside working hours, check file counts and permissions afterwards, and tell your staff early.
- Your originals are copied, not deleted, so you keep a safety net until you are happy.
Table of Contents
- What a SharePoint migration actually is
- Step 1: Decide why you are moving and what goes
- Step 2: Audit and scan before you copy
- Step 3: Design where the files will live
- Step 4: Clean up and fix the problems
- Step 5: Run a pilot
- Step 6: Migrate in waves
- Step 7: Check that everything arrived
- Step 8: Tell people early, then help them use it
- The one-page SharePoint migration checklist
- Our view: plan it like a change in how you work
- Getting Microsoft 365 set up around your migration
- FAQ
- Sources
What a SharePoint migration actually is
SharePoint is the part of Microsoft 365 where a business keeps shared documents, team sites and intranet pages. A migration means moving your existing files, from a file server, a network drive or an older version of SharePoint, into it.
For most small businesses the content is a shared drive that has grown for a decade: folders called “Old”, “Old 2” and “Final FINAL”, with permissions set by someone who left in 2019. That is why the plan matters more than the tool. Microsoft’s own file share migration guide lists the stages as planning, assessment and remediation, preparing the target environment, migration, and user onboarding. Notice that only one of those five is the copying.

The reassuring part: Microsoft’s migration overview states that migration copies content and does not delete the source files. Nothing disappears on the day. That lets you work calmly and keep the old location read-only until everyone is settled.
Step 1: Decide why you are moving and what goes
Start with the reason, in one sentence. “Staff can’t get at files from home” or “we keep emailing different versions of the same quote” are good ones. That sentence decides your priorities later, when you are choosing between a perfect folder structure and a Friday deadline.
Then look at the content. Microsoft’s rollout planning guidance recommends asking people to review their content and delete or archive what is no longer needed, which saves both migration time and Microsoft 365 storage. In practice, sort what you have into three piles:
- Live work: current clients, projects, templates, policies. This moves.
- Reference material: finished jobs you must keep for tax, contract or insurance reasons. Move it into a quieter, read-only area, or archive it.
- Clutter: duplicates, personal files, installers, test documents. Delete it.
Do not do this alone in an office. The person who created a folder usually knows in ten seconds whether it matters, and you do not. Give each team lead a simple list of their top-level folders and a deadline of a week.
A worked example
Imagine a twelve-person building services firm with 400 GB on an old office server. After a review, the team agrees that around a third is finished jobs older than seven years, and another chunk is duplicate photos. The live material comes to perhaps 150 GB. That is a far friendlier migration than 400 GB, and the team now knows where everything is. The numbers here are illustrative, but the pattern is very common.
Step 2: Audit and scan before you copy
This is the step small businesses skip and then regret. Before anything moves, find out what will cause trouble. Microsoft’s guide says to assess the source, how relevant and how used the content is, how it maps to the target, permissions, file extensions, names and path lengths, and recommends running the SharePoint Migration Tool (SPMT) in scan-only mode to identify file problems before transferring content. Microsoft describes SPMT as a free solution for moving file shares and on-premises SharePoint sites into Microsoft 365.
What the scan typically turns up:
- Very long file paths. Folders nested ten deep with long names. Flatten them.
- Unsupported characters or file types. These need renaming or removing.
- Odd permissions. Folders shared with people who left, or with “everyone”.
- Huge files and forgotten backups. Often the real reason a transfer takes days.
Write the findings down in a simple spreadsheet: folder, owner, problem, fix, done. It becomes your migration log and later your proof that everything arrived.
Check who can do the work
Migration needs the right access. Microsoft’s Migration Manager guidance says the source credentials need read access to the network shares, and the destination requires a Global admin or SharePoint/OneDrive admin account. Sort this out before the pilot, not on the evening of the move.
Step 3: Design where the files will live
This is where you stop copying the old mess. Resist the urge to recreate every folder as it was. Think in terms of how people work.
A simple structure that suits most small businesses:
| Area | What goes in it | Who has access |
|---|---|---|
| Company site | Policies, templates, handbook, brand assets | Everyone, edit rights for a few |
| Finance and admin | Invoices, contracts, payroll, HR | Directors and finance only |
| Each team or department | Day-to-day working files | That team |
| Client or project libraries | Files per client or job | The people on that work |
A few rules keep this healthy:
- Fewer folders, clearer names. Two or three levels is plenty. Use search and a consistent file naming habit instead of deep nesting.
- Permissions by group, not person. Give “Finance” access, not Sarah and Tom. When someone joins or leaves, you change one group.
- Keep sensitive areas separate. It is much easier to lock down a whole library than a single folder buried in a shared one.
It helps to know what moves across with your files. Microsoft states that SPMT migrates file and folder structure, user-level permissions, and site, document and folder metadata, while explicit deny permissions are not migrated. If your old server uses deny rules to hide folders, write those down and rebuild them deliberately in the new design rather than assuming they came across.
If you want to track extra details on documents, such as client name or document status, create those columns and content types in the destination before the migration so the information has somewhere to land. Do not overdo it. Two or three useful columns beat twelve nobody fills in.
Step 4: Clean up and fix the problems
Now work through the audit list. Rename the awkward files, shorten the long paths, remove the clutter, and tidy the permissions you identified. This is dull work, and it is where the quality of the whole project is decided.
Two practical tips:
- Freeze the old location’s structure once cleaning starts, so nobody invents new folders while you are tidying.
- Decide about workflows. Microsoft’s planning guidance asks you to decide how file-related workflows, such as automated approvals or macros that reference file paths, will be integrated with Microsoft 365 or migrated there. Spreadsheets with links to the old drive letter are the classic casualty.
Step 5: Run a pilot
Pick one team, ideally one that is friendly towards change and has a manageable amount of content, and migrate their files first. Ask two or three of them to work in the new site for a few days.
What you are checking:
- Can people find their files and open them?
- Do they have the right access, and nothing more?
- Are the folder structure, metadata and version history as expected?
- Do shortcuts, linked spreadsheets and templates still work?
- Is syncing to their computers working smoothly?
Collect every problem in the same log, with an owner and a fix. Retest the fixes. Then, and only then, plan the full migration. The pilot always finds something, and it is far better to find it with one team than with twelve people on a Monday morning.
Step 6: Migrate in waves
With the pilot signed off, move the rest in stages, team by team or library by library, rather than everything in one go. Smaller waves are easier to check and easier to roll back in your head if something looks wrong.
Some sensible habits:
- Schedule transfers for evenings or weekends. Microsoft’s guidance warns that large moves can cause a surge in network activity, so make network impact part of your scheduling. On a small-office broadband line, a big upload during the working day can make video calls and cloud software crawl.
- Use the migration tool’s reporting. Microsoft’s Migration Manager supports prescans, monitoring, and downloadable summary and task-level reports, which give you a record of what moved and what failed.
- Keep the source as it is. Because content is copied, set the old location to read-only on cut-over day rather than deleting anything.
- Plan a final “delta” pass. If people edited files during the migration, run a last catch-up copy right before switching.
Step 7: Check that everything arrived
After each wave, compare the new site against your log. Do not trust a green tick alone. A sensible post-migration check covers:
| Check | What to look at |
|---|---|
| File counts | Does the number of files and folders match the source? |
| Integrity | Do a sample of files open properly, including large ones? |
| Permissions | Can the right people open it, and can the wrong people not? |
| Metadata and versions | Are dates, authors and version history preserved where they matter? |
| Links and shortcuts | Do internal links, templates and linked spreadsheets still work? |
| Sync | Does the library sync cleanly to a few real laptops? |
Finish with a short sign-off from each team lead. One named person saying “yes, my team’s files are all here and working” is worth more than any report.
Step 8: Tell people early, then help them use it
Most migrations that go badly do so because staff were surprised. Microsoft’s advice is to communicate early and often about the migration and what it means for people, instead of waiting until the end.
A light communication plan for a small team:
- Two to three weeks before: say what is changing, why it helps, and the date.
- One week before: show where their files will be, with a five-minute demo.
- Cut-over day: send a short note with the new location, how to sync, and who to ask.
- First fortnight: be around. A named person who answers quick questions removes most of the friction.
Keep training practical: how to find a file, share it with a colleague, edit with someone else at the same time, and get an old version back. Those four skills cover most daily use. The same principle applies to any new business system; our guide to getting your team to actually use new software covers it from the CRM side, and it holds just as well for SharePoint.
If your email is also moving, plan it as a separate project with its own timetable. We have written a full guide to migrating email to Microsoft 365 that you can run alongside this plan.
The one-page SharePoint migration checklist
Use this as a final pass. It follows the stages Microsoft sets out for file migrations.
Before
- [ ] Reason for moving written down
- [ ] Content reviewed by owners; obsolete material deleted or archived
- [ ] Scan-only assessment run and findings logged
- [ ] Migration account has the right source and destination access
- [ ] Target structure, groups and permissions designed
- [ ] Columns or content types created in the destination, if you use them
During
- [ ] Problem files fixed (names, paths, unsupported types)
- [ ] Pilot team migrated and tested; issues fixed and retested
- [ ] Waves scheduled outside working hours
- [ ] Final catch-up copy done before cut-over
After
- [ ] File counts, permissions, versions and links checked
- [ ] Team leads signed off
- [ ] Old location set to read-only, not deleted
- [ ] Staff trained, with a named person for questions
Our view: plan it like a change in how you work
We have seen a lot of small businesses treat a SharePoint move as an IT job. It is really a how-we-work job. The software is the easy part. The hard part is deciding who owns which files, who should see what, and getting twelve busy people to use the new place instead of the old habit.
That is why we start with the people and the paperwork, not the tool. We look at how your team actually works, design a structure that matches it, and keep it simple enough that nobody needs a manual. Because we manage Microsoft 365 for small businesses and have a locally based Derbyshire team, we can also be there in person when the day comes, which is a big comfort when your files are on the line.
If you are going to do this, do it once, do it tidily, and leave yourself a business that is easier to run on the other side.
Chris
Getting Microsoft 365 set up around your migration
SharePoint sits inside Microsoft 365, so the licences, security settings and user accounts need to be right before the first file moves. Our Microsoft 365 packages start from £16 per month per user, and you can see what is included on our Microsoft 365 for business page. If you would rather have a local team plan and manage it with you, get in touch and tell us how your files are held today.
FAQ
How long does a SharePoint migration take for a small business?
It depends far more on preparation than on file size. Reviewing content, fixing problems and running a pilot normally take longer than the transfer itself, and the transfer time depends on how much you move and your internet connection. Moving in waves outside working hours keeps the disruption low.
Will I lose my old files when I migrate?
No. Microsoft states that migration copies content and does not delete the source files. Keep the original location read-only until you have checked the new one and your team has signed off.
Do permissions move across to SharePoint?
Mostly. Microsoft says SPMT carries over user-level permissions along with folder structure and metadata, but explicit deny permissions are not migrated. Review your permissions in the design stage and check them after each wave.
What should I move to SharePoint and what should I archive?
Move current, actively used files. Archive reference material you must keep for legal or tax reasons, and delete duplicates and clutter. Microsoft recommends having staff review content and delete or archive what is obsolete, which also saves storage.
Do I need a pilot if we only have a handful of staff?
Yes, but a small one. Migrating one team or one library first, and having two or three people use it for a few days, catches broken links, access problems and sync issues before they affect everyone.
Sources
- Migrate file shares to SharePoint and OneDrive (Microsoft Learn)
- Migration planning for SharePoint and OneDrive rollout (Microsoft Learn)
- Migrate to Microsoft 365 (Microsoft Learn)
- SharePoint Migration Tool for SharePoint and OneDrive (Microsoft Learn)
- Migrate your file shares to Microsoft 365 with Migration Manager (Microsoft Learn)
Recommended
- CRM data migration: your practical guide for UK SMEs
- Migrate email to Microsoft 365: your complete 2026 guide
- Site Migration SEO: How to Move Your Website Without Losing Rankings
Related reading: OneDrive vs Dropbox: which is right for your business? · Migrate email to Microsoft 365: the complete guide · Local SEO checklist for small businesses




