IT admins at 100-2000 person companies are handed file server retirement deadlines without a structure design step. Migration tools move content but do not decide the target architecture, so small teams either stall the project or lift and shift deep folder trees into SharePoint, breaking sync, paths, permissions, and findability, and burning trust they need for every later cleanup.
If this problem is unfamiliar, start here.
When companies retire on-premises file servers, the content has to move into Microsoft 365, usually SharePoint for shared content and OneDrive for personal files. Microsoft provides Migration Manager, a free tool in the SharePoint admin center that copies file shares into SharePoint. The hard part is not the copy: it is deciding the target structure, because SharePoint organizes content into sites and libraries with permission inheritance and metadata, which behaves very differently from a deeply nested shared drive.
Click any term to see its definition.
The Reality
IT admin, Microsoft 365 admin, or SharePoint site owner at a 100-2000 person company on a 1-3 person team
The email from my IT manager this morning was short: the file server goes dark at the end of the quarter, finance has already cancelled the hardware refresh, and the VPN complaints mean nobody will defend keeping it. So that decision is made. What is not made is literally everything else.
I spent an hour in the F drive before lunch just looking. Marketing has folders eleven levels deep. Operations has a folder called New Structure from 2019 sitting next to the old structure it was meant to replace. There are three folders named Final. I opened Migration Manager in the SharePoint admin center and the tooling side honestly looks fine: agents, tasks, reports. It will happily copy all of this exactly as it is, which is exactly what scares me.
A small win this afternoon: I picked one small team, the five-person quality group, sketched a single team site with two libraries for them, and it took twenty minutes and felt obvious. Then I multiplied that by forty departments and ten years of undocumented folders and felt sick again. When I asked the operations lead what in their tree is still used, the answer was probably most of it, which means nobody knows.
What I actually want is not a migration tool. I want a method: a way to walk a folder tree with its owner for one hour and come out with a site and library decision, a keep or archive line, and a name written down next to it. If I had that, the deadline would feel like a project instead of a cliff.
30-55 • Intermediate Microsoft 365 generalist; became the SharePoint person by fixing the first issues, not by training as an architect
Skills
Frustrations
Goals
Top Objections
How They Talk
Use These Words
Avoid
Learning Pathway
Go from an undocumented folder tree and a scary deadline to an owned, written migration map and a pilot migration that proves the method.
Showing 3 of 3 recommendations
From staring at an undocumented folder tree under deadline dread to running a known method that converts each department into a one-hour decision session with a written, defensible output.
You'll build: Complete the migration map for at least three departments including one pilot department migrated with Migration Manager, with a written review of where the pilot matched and diverged from the map.
From tool anxiety and vendor noise as a stand-in for a plan, toward a recorded, defensible tool choice made before any content moves.
You'll build: A completed one-page tool decision record: chosen path, the three decisive factors, what was ruled out and why, and the date and source versions the decision relied on.
From migration decisions scattered across notebooks, email, and memory, toward one list the whole project, and its leadership reporting, runs from.
You'll build: The configured tracker list with all views working, at least one department's rows entered, and one row moved through the full status flow as proof.
Build brief: Existing-tool setup · Maker handoff
We traced backward through five layers of "why" until we hit the source. Here's what's really driving this.
Why is the migration stuck or painful?
The deadline is set externally, but the structure decisions, sites, libraries, ownership, and exclusions have not been made and cannot be deferred past the copy step.
Why are the structure decisions so hard?
Folder trees grew for ten or more years with no documentation. A one-to-one copy fails technically and functionally, but nobody can say what each area is for or what is stale.
Why does a one-to-one copy fail?
SharePoint organizes content by site and library with flatter structures, metadata, and inheritance-based permissions. Deep nested trees hit path, sync, and sharing problems and bury content Copilot and search later amplify.
Why has nobody mapped the content before now?
Ownership was never recorded. Department folders belong to everyone and no one, so the admin cannot get decisions about what to keep, restructure, or delete without a method for forcing small, answerable questions.
Why does no method exist in the team?
Migration tooling answers how to move bytes, and enterprise guidance assumes architects and change managers. There is no repeatable, small-team design step between copy everything and redesign everything.
Root Cause
Migration tools and deadlines exist, but the design step does not: small IT teams have no repeatable method for turning an undocumented folder tree into a SharePoint structure with named owners and explicit exclusions, so lift and shift wins by default and recreates the mess.

The Numbers
Key metrics that determine the opportunity value.
Overall Impact Score
Urgency
They need this fixed now
Build Difficulty
Complex, needs deep expertise
Market Size
Healthy demand exists
Competition Gap
Moderate competition
"There are many decisions to be made, like types of sites, the amount of content to migrate, security, and permissions."
"The SharePoint Migration Tool is free, but it comes with several caveats that teams need to plan for up front."
"If anyone's found a good file server to SharePoint migration strategy/framework I'd like to know too!"
Current market solutions and where there are opportunities.
The pattern they all miss — and how to beat it.
Tooling and documentation answer how to move bytes. Small-team practitioners still need a way to decide target structure, ownership, and exclusions in days, which is the actual blocker.
The non-negotiables and nice-to-haves for any product or service tackling this problem.
The 3 Wishes
Walk any department folder tree with its owner for one hour and walk out with a written site and library decision, a keep, archive, or leave-behind line for every top-level folder, and a named owner, repeated until the whole file server has a migration map a small team can execute.
Must Have
A repeatable folder-walk method with scripts and decision questions
A migration map artifact: source path, target site and library, owner, action, date
A what-not-to-migrate decision rule set
A permissions translation step from ACLs to SharePoint inheritance
A pilot-first sequence with a rollback story
Nice to Have
Migration Manager prescan walkthrough
Department communication templates
A naming convention starter set
Out of Scope
Tenant-to-tenant migration
SharePoint Server on-premises targets
Records management and legal retention design
Custom tooling or scripts requiring developer support
Success Metrics
A completed migration map covering every in-scope share
Every mapped area has a named owner and an explicit action
One pilot department migrated and reviewed against the map
A written exclusion list leadership has seen
Solution Strategy
Migration Manager and paid tooling compete on copy speed and fidelity; consultants compete on done-for-you redesign. Nothing serves the small team that must design the structure itself in days. A method-first course with a tracker beats both: cheaper than consultants, and it makes any copy tool safer.
Lead with a course teaching the folder-walk mapping method producing a migration map, support it with a briefing that settles the Migration Manager versus paid tooling decision, and add a blueprint for a migration decision tracker the team runs during the project.
Technologies and trends that could disrupt this space. Factor these into your timing.
Mapping gets faster, but owner decisions and exclusions remain human; the method stays valuable as the review layer
Strengthens the free path this content already centers on; tooling briefing needs periodic refresh
Marketing hooks, SEO keywords, and buying triggers to help you create content around this problem.
Events that make people search for solutions
Attention-grabbing hooks for your content
What people type when looking for solutions
The Evidence
Every claim in this report is backed by public sources. Verify anything.
Problem published by Collab365 Spaces. Cite as "We have to move our file shares into SharePoint, and I do not know how to structure it", Collab365 Spaces. 7 sources referenced.
Have a question or correction?