Before You Migrate File Shares to SharePoint: What IT Directors Should Decide First

TL;DR

Before migrating file shares to SharePoint, IT Directors should decide:

• What content should be migrated, archived, or deleted
• Who owns each department, client, project, or business area
• Which permissions should be redesigned instead of copied
• What belongs in SharePoint, Teams, and OneDrive
• How sites, libraries, metadata, and navigation should be structured
• What retention, sensitivity, and compliance requirements apply
• How external sharing should be controlled
• How users will be trained before launch
• How migration waves, pilot groups, and validation will work
• Who will govern the environment after migration

A successful migration is not measured only by how many files moved successfully.

It is measured by whether users can find, trust, secure, and manage the content after the migration.

---

Table of Contents

1. Why File Share Migrations Fail
2. Decision 1: What Content Should Actually Move?
3. Decision 2: Who Owns Each Business Area?
4. Decision 3: Should Existing Permissions Be Copied or Redesigned?
5. Decision 4: What Belongs in SharePoint, Teams, and OneDrive?
6. Decision 5: What Should the SharePoint Information Architecture Look Like?
7. Decision 6: What Retention, Compliance, and Sensitivity Rules Apply?
8. Decision 7: How Should External Sharing Be Managed?
9. Decision 8: How Will the Migration Be Phased and Validated?
10. Decision 9: How Will Users Be Trained?
11. Decision 10: What Happens After Migration?
12. Real-World Scenario
13. Practical Migration Readiness Checklist
14. Final Thoughts

---

Why File Share Migrations Fail

Most file share migration problems do not start during migration.

They start before migration.

The most common mistake is treating the project as a technical transfer instead of a business and governance initiative.

A file share usually contains years of organizational history. Some of it is valuable. Some of it is duplicated. Some of it is obsolete. Some of it has unclear ownership. Some of it may contain sensitive client, employee, financial, legal, or operational information.

When everything is moved without review, the organization carries the same problems into SharePoint Online.

Common symptoms after a rushed migration include:

• Users cannot find documents because old folder structures were copied without redesign
• Permissions are overly complex or inherited from outdated file share models
• Business owners do not know which sites they are responsible for
• Sensitive content becomes easier to discover but not necessarily better governed
• Teams create duplicate locations because the new structure is confusing
• Retention policies are not aligned to the way content is stored
• IT becomes the owner of every access request, cleanup question, and support issue
• Leadership assumes the migration is complete, but users still work around the system

A migration should be used as an opportunity to improve the way information is managed.

Not just where it is stored.

---

Decision 1: What Content Should Actually Move?

The first major decision is not which tool to use.

The first decision is what should move.

Many file shares contain ROT content:

• Redundant content: duplicate files, copied folders, old exports, repeated reports
• Obsolete content: outdated working drafts, retired project material, old templates
• Trivial content: temporary files, personal files, low-value content with no business purpose

Migrating ROT content increases cost, complexity, search noise, storage usage, and governance risk.

It also makes SharePoint harder for users to trust.

If employees search SharePoint and find five versions of the same document, they may go back to emailing attachments or keeping their own copies.

Before migration, IT Directors should ask:

• What content has not been opened or modified in several years?
• Which folders have no clear business owner?
• Which areas contain duplicate exports or backups?
• Which documents are official business records?
• Which files should be archived instead of migrated into active SharePoint sites?
• Which content can be deleted after business approval?
• Which content requires legal, compliance, or records review before deletion?

The goal is not to delete aggressively without business input.

The goal is to avoid moving everything blindly.

Practical recommendation

Create a migration disposition model:

Content Type	Recommended Action	Notes
Active business content	Migrate to SharePoint	Needs owner, permissions, and validation
Completed project records	Migrate or archive	Depends on retention and search needs
Old duplicate folders	Review before migration	Avoid copying unnecessary clutter
Unknown owner content	Hold for business review	Do not place into production sites without ownership
Personal or temporary files	Exclude or archive	Confirm with department leads
Regulated or sensitive content	Review with compliance/security	May need labels, restricted sites, or special handling

---

Decision 2: Who Owns Each Business Area?

SharePoint works best when ownership is clear.

A file share often grows organically. A folder may have been created by someone who left the organization years ago. Another folder may be used by three departments. Some project areas may have no obvious owner.

If ownership is not decided before migration, IT can accidentally become responsible for everything.

That is not sustainable.

Before creating SharePoint sites and libraries, decide who owns each major area.

Ownership should be assigned at a level that makes business sense:

• Department
• Business unit
• Client
• Project
• Region
• Practice area
• Functional process
• Records category

Each area should have at least one business owner and one backup owner.

The owner does not need to be technical. Their role is to make business decisions about content, access, lifecycle, and validation.

Questions to ask business owners

• Is this content still active?
• Who should have access?
• Is any content confidential, regulated, or client-sensitive?
• Are there external users or partners involved?
• How long should this content be retained?
• What should happen when the project, client, or business process ends?
• Who will approve access requests after migration?
• Who will validate that the migrated content is complete?

Practical recommendation

Create a simple ownership matrix before migration.

Source Location	Future SharePoint Location	Business Owner	Backup Owner	Access Model	Retention Need	Migration Decision
\FileShare\Finance	Finance SharePoint Site	Finance Director	Finance Manager	Finance team only	7 years	Migrate active + archive old
\FileShare\Projects\ClientA	Client A Project Site	Engagement Lead	PMO Lead	Assigned project team	Client policy	Migrate after cleanup
\FileShare\HR	HR Restricted Site	HR Director	HR Operations Manager	Restricted	Employee records	Compliance review required

This type of matrix helps convert migration from a technical task into a controlled business process.

---

Decision 3: Should Existing Permissions Be Copied or Redesigned?

Copying file share permissions exactly into SharePoint may sound safe.

In many cases, it is not.

File share permissions often reflect years of exceptions, temporary access, nested groups, inherited access, direct user assignments, and undocumented business decisions.

SharePoint has a different permission model. It includes Microsoft 365 groups, SharePoint groups, site permissions, library permissions, item-level permissions, sharing links, external access, and sensitivity controls.

A direct copy can create long-term governance problems.

When copying permissions may be acceptable

Copying existing permissions can be reasonable when:

• The source permission model is already clean
• Access is managed through well-named security groups
• Business owners have validated the access model
• There are no major sensitive data concerns
• The migration needs to preserve strict continuity for active work

When permissions should be redesigned

Permissions should be redesigned when:

• There are many direct user assignments
• There are deeply nested groups with unclear purpose
• Users have access because of old roles or temporary exceptions
• Sensitive content is mixed with general department content
• External users are involved
• Permissions are managed differently across similar folders
• Business owners cannot explain who should have access
• Copilot readiness or oversharing risk is a concern

Practical recommendation

Use migration as a permission cleanup opportunity.

A strong target model usually includes:

• Fewer unique permission breaks
• Clear Microsoft 365 or Entra ID group ownership
• Standard SharePoint groups where appropriate
• Separate sites or libraries for truly restricted content
• Limited direct user permissions
• A defined access request and approval process
• Periodic access reviews after migration

The goal is not to make permissions complicated.

The goal is to make permissions explainable.

If a business owner cannot explain why a group has access, that access should be reviewed before it is recreated in SharePoint.

Planning a file share to SharePoint migration? I can help review your source structure, permissions, governance risks, and target SharePoint design before files start moving.

Book a free 30-minute consultation

---

Decision 4: What Belongs in SharePoint, Teams, and OneDrive?

One of the most important migration decisions is helping users understand where work belongs after the file share is retired.

A simple model is:

• OneDrive = Me
• Teams = Us
• SharePoint = Everyone / the organization / managed business records

This is not a perfect rule, but it is a useful starting point.

OneDrive

OneDrive is best for personal work files, early drafts, and documents that are not yet ready for team or organizational use.

However, OneDrive should not become the long-term home for important business records.

If a key document lives only in one employee’s OneDrive, the organization may have access, continuity, and ownership problems when that employee is unavailable, changes roles, or leaves.

Teams

Teams is best for active collaboration within a group.

Files uploaded to a Teams channel are stored in the SharePoint site connected to that team, but users often experience the files through the Teams interface.

Teams works well for conversations and active work. But it can become messy if every long-term business record is stored in random channels without governance.

SharePoint

SharePoint is best for managed content, department portals, intranet content, document libraries, records, knowledge bases, controlled access areas, and business-owned document repositories.

For many organizations moving from network drives, SharePoint should become the primary destination for important business content that needs ownership, structure, retention, permissions, and findability.

Practical recommendation

Create a simple user guidance table.

Scenario	Recommended Location	Why
Personal draft not ready to share	OneDrive	Owned by the individual
Team working document	Teams channel / connected SharePoint library	Supports active collaboration
Approved department policy	SharePoint communication site or document center	Needs visibility, ownership, and retention
Client project documents	SharePoint team site or project site	Needs structured access and lifecycle
Organization-wide template	SharePoint intranet or document library	Needs a single trusted source
Temporary meeting notes	Teams or OneDrive	Depends on audience and lifecycle
Official business record	SharePoint with retention/governance	Needs control and long-term management

Training users on this model is just as important as configuring the sites.

---

Decision 5: What Should the SharePoint Information Architecture Look Like?

Information architecture is the structure that helps users find, manage, and trust content.

In a file share, structure is usually folder-based.

In SharePoint, structure can include:

• Hub sites
• Team sites
• Communication sites
• Document libraries
• Metadata
• Content types
• Views
• Document sets
• Navigation
• Search configuration
• Site templates
• Naming standards

A migration should not automatically recreate the deepest folder structure from the file share.

Deep folder structures may have made sense on a network drive, but they can create usability and governance problems in SharePoint.

Practical questions

Before migration, decide:

• Should this content become one site or multiple sites?
• Should sensitive content be separated into its own site or library?
• Should project/client content use a repeatable template?
• Are folders still useful, or should metadata be introduced?
• What naming conventions should be used for sites, libraries, and groups?
• How will users navigate from the intranet or hub site to key document areas?
• Which views will users need on day one?
• Which areas need search optimization?

Practical recommendation

Avoid designing SharePoint only from the source folder tree.

Design around how the business works now:

• Departments
• Client work
• Project lifecycle
• Compliance requirements
• User navigation
• Search needs
• Security boundaries
• Ownership model

A good SharePoint structure should make sense to users without requiring them to memorize where everything went.

For more guidance on structuring document libraries, see SharePoint Document Library Best Practices.

---

Decision 6: What Retention, Compliance, and Sensitivity Rules Apply?

Many organizations move files to SharePoint because Microsoft 365 gives them better governance options than traditional file shares.

But those benefits do not happen automatically.

Retention, sensitivity, records management, and compliance settings need planning.

Before migration, IT Directors should identify:

• Which content is considered a business record
• Which content has legal or regulatory retention requirements
• Which content contains confidential, financial, client, employee, or regulated data
• Which content should be labeled
• Which content should be restricted from external sharing
• Which content should be archived after a period of inactivity
• Which content may be discoverable by Microsoft Search or Microsoft 365 Copilot

Practical recommendation

Involve compliance, legal, records, or security stakeholders early.

Do not wait until after migration to ask retention questions.

If retention requirements are known before migration, you can design the SharePoint structure to support them more cleanly.

For example:

• HR records may need a restricted site with specific retention policies
• Client project documents may need lifecycle rules based on project status
• Policies may need version control and acknowledgement tracking
• Financial records may need longer retention than general working documents
• Sensitive content may need sensitivity labels or restricted sharing controls

The migration project should not try to solve every compliance issue at once.

But it should avoid creating a structure that makes compliance harder later.

---

Decision 7: How Should External Sharing Be Managed?

External sharing is one of the biggest differences between a traditional file share and SharePoint Online.

In SharePoint, users can collaborate with external partners, vendors, clients, and guests if the tenant and site settings allow it.

That flexibility is valuable, but it needs guardrails.

Before migration, decide:

• Which sites allow external sharing?
• Which sites should block external sharing completely?
• Who can approve external access?
• Are anonymous links allowed, restricted, or disabled?
• Should sharing links expire?
• Should external users be reviewed periodically?
• Should sensitive sites use stricter controls?
• How will external sharing be reported and audited?

Practical recommendation

Do not use one blanket rule without understanding business needs.

Some areas may need external collaboration. Others should be locked down.

A better model is usually risk-based:

Content Area	External Sharing Recommendation
Public marketing files	May allow controlled sharing
Active client project site	May allow approved guests
HR records	Block external sharing
Finance records	Block or tightly restrict external sharing
General department collaboration	Allow internal-only by default
Vendor collaboration site	Allow guests with review process

External sharing should be designed before users start creating their own workarounds.

---

Decision 8: How Will the Migration Be Phased and Validated?

Large file share migrations should rarely be one big cutover.

A phased approach reduces risk and gives the team time to learn.

A practical migration approach often includes:

1. Discovery
2. Content inventory
3. Ownership mapping
4. Cleanup and disposition
5. Target SharePoint design
6. Pilot migration
7. User acceptance testing
8. Permission validation
9. Business sign-off
10. Migration waves
11. Delta migration
12. Cutover
13. Post-migration support
14. Governance review

Pilot migration

A pilot migration should include a real business area, not just a small test folder with clean files.

The pilot should validate:

• File count and size handling
• Special characters and path length issues
• Permissions mapping
• Metadata behavior
• Version history decisions
• Sharing behavior
• User experience
• Sync behavior
• Search behavior
• Support process

Migration waves

Migration waves should be based on business risk and readiness, not just folder size.

Consider grouping waves by:

• Department
• Business unit
• Client area
• Project type
• Permission complexity
• Sensitivity level
• Readiness of business owners
• Training schedule

Practical recommendation

Create a wave plan that includes business sign-off.

Wave	Area	Risk Level	Owner	Pilot Needed?	Training Date	Cutover Date	Validation Owner
1	Internal IT	Low	IT Manager	Yes	TBD	TBD	IT Lead
2	Finance	High	Finance Director	Yes	TBD	TBD	Finance Owner
3	Operations	Medium	Operations Director	No	TBD	TBD	Operations Lead
4	Client Projects	High	PMO Director	Yes	TBD	TBD	PMO Lead

This gives leadership visibility and helps prevent surprises.

For a detailed look at how I approach migration execution, see How I Plan and Execute SharePoint Migrations to Microsoft 365.

---

Decision 9: How Will Users Be Trained?

Training is often underestimated in SharePoint migrations.

Users are not only learning a new location. They are learning a new way to collaborate.

A file share migration may change:

• How users open documents
• How users share documents
• How users request access
• How users sync files
• How users search
• How users use Teams-connected files
• How users recognize official records
• How users avoid creating duplicates
• How users work with metadata and views

Training topics that matter

At minimum, users should understand:

• When to use OneDrive, Teams, and SharePoint
• How sharing links work
• The difference between direct access and sharing links
• Why they should avoid copying links from browser paths without understanding permissions
• How to request access properly
• How to use version history
• How to recover deleted files where appropriate
• How to use SharePoint search
• How to use library views
• When not to sync a large library
• Who to contact for support

Practical recommendation

Create short role-based training instead of one long generic session.

Examples:

• Department owner training
• General user training
• Site owner training
• Records/compliance training
• Executive overview
• Help desk support training

Training should explain not only how to use SharePoint, but why the organization is changing.

Users are more likely to adopt the new model when they understand the business reason behind it.

---

Decision 10: What Happens After Migration?

Migration is not the finish line.

It is the beginning of the new operating model.

After migration, the organization needs a plan for:

• Site ownership reviews
• Permissions reviews
• External sharing reviews
• Inactive site cleanup
• Storage monitoring
• Retention policy validation
• New site provisioning
• New project or client workspace creation
• Support requests
• Training refreshers
• Governance reporting
• Continuous improvement

Without post-migration governance, SharePoint will slowly drift.

New sites will be created inconsistently. Permissions will become messy. Users will create duplicate libraries. External sharing may expand without review. Old content will accumulate again.

Practical recommendation

Define a lightweight governance rhythm.

Governance Activity	Suggested Frequency	Owner
Review external sharing reports	Monthly or quarterly	IT / Security
Review inactive sites	Quarterly	M365 Admin / Business Owners
Review high-risk permissions	Quarterly	IT / Site Owners
Confirm site ownership	Twice per year	Business Owners
Review storage growth	Monthly	IT
Review new site requests	Ongoing	Governance Owner
Update training materials	Quarterly or as needed	IT / Adoption Lead

Governance does not need to be heavy to be useful.

It needs to be consistent.

For more on managing SharePoint site lifecycle after migration, see Managing Inactive SharePoint Sites.

---

Real-World Scenario

Imagine an organization with a 6 TB network file share.

The file share contains department folders, client folders, project folders, HR records, finance records, old exports, archived reports, and years of duplicated content.

The initial request may sound simple:

We want to move the file share to SharePoint.

But after discovery, the real questions appear:

• Which folders are still active?
• Which client areas are closed but need to be retained?
• Which permissions are based on job role versus old exceptions?
• Should each client have a separate site?
• Should each department have a hub-connected site?
• Should HR and Finance be separated from general collaboration?
• Should external partner access be allowed?
• What happens when a project closes?
• How will users know whether to store files in Teams or SharePoint?
• Who approves access after migration?

This is why discovery and planning are so important.

A migration tool can move files.

It cannot decide your governance model, ownership structure, retention approach, or adoption strategy for you.

Those decisions need leadership input.

---

Practical Migration Readiness Checklist

Before approving a file share to SharePoint migration, IT Directors should be able to answer these questions.

Content readiness

• Do we know how much data exists in the source file share?
• Do we know the folder depth and path length risk?
• Do we know which content is active, stale, duplicate, or obsolete?
• Do we have a ROT cleanup approach?
• Do we know what should be archived instead of migrated?

Ownership readiness

• Does each major content area have a business owner?
• Is there a backup owner?
• Are owners responsible for validating migration results?
• Are owners responsible for approving access decisions?

Permission readiness

• Have source permissions been reviewed?
• Are there direct user permissions that should be replaced with groups?
• Are there sensitive areas that need separate sites or libraries?
• Has external sharing been reviewed?
• Is there a post-migration access review plan?

For more on permissions strategy, see SharePoint Site Permissions Best Practices.

SharePoint design readiness

• Do we know the target site structure?
• Do we know which areas belong in Teams versus SharePoint?
• Are naming conventions defined?
• Are hub sites, navigation, libraries, and views planned?
• Are metadata, content types, or document sets needed?

Compliance readiness

• Are retention requirements known?
• Are sensitivity or confidentiality requirements known?
• Are records management stakeholders involved?
• Are legal hold or regulatory concerns identified?
• Are Copilot/search exposure risks understood?

Migration execution readiness

• Is there a pilot migration plan?
• Is there a wave plan?
• Is there a validation process?
• Is there a rollback or issue resolution process?
• Is there a cutover communication plan?

Adoption readiness

• Are users trained on OneDrive, Teams, and SharePoint usage?
• Are site owners trained?
• Are help desk/support teams prepared?
• Are quick reference guides available?
• Is there a support window after launch?

Governance readiness

• Is there a site provisioning process?
• Is there a permissions review schedule?
• Is there an inactive site process?
• Is there an external sharing review process?
• Is someone accountable for ongoing SharePoint governance?

Planning a file share to SharePoint migration? I can help review your source structure, permissions, governance risks, and target SharePoint design before files start moving.

Book a free 30-minute consultation

---

Business Impact of Making These Decisions Early

When these decisions are made before migration, the organization gets more than a new document location.

It gets a cleaner operating model.

The business impact includes:

• Lower migration risk
• Better user adoption
• Fewer support tickets
• Clearer ownership
• Cleaner permissions
• Reduced oversharing risk
• Better search experience
• Stronger compliance alignment
• Better readiness for Microsoft 365 Copilot
• Less content sprawl after migration
• More confidence from leadership and business teams

A well-planned migration can improve the way the organization manages information.

A rushed migration can make existing problems more visible.

---

Final Thoughts

Migrating file shares to SharePoint is not just about moving files from one location to another.

It is a chance to decide how the organization wants to manage content going forward.

Before the migration starts, IT Directors should align with business owners on content cleanup, permissions, ownership, retention, external sharing, adoption, and governance.

The migration tool is important.

But the strategy around the tool is what determines whether SharePoint becomes a trusted business platform or just another place where files get lost.

If your organization is preparing to move network drives, file shares, or legacy document repositories into SharePoint Online, start with the decisions first.

The files can move later.

---

Need Help Planning a SharePoint Migration?

I help organizations plan and implement practical SharePoint and Microsoft 365 migrations with a focus on discovery, permissions, governance, information architecture, adoption, and long-term supportability.

If you are preparing for a file share to SharePoint migration and want a second set of eyes before the project starts, you can reach out through my contact page.

Book a free 30-minute consultation