File Share to SharePoint Migration: Cleanup Tips Before You Move
- Jul 7
- 6 min read
Most organizations know their file shares are messy. The problem is nobody knows exactly how messy until a migration project starts.
A department folder has 18 versions of the same policy. A finance drive contains files from systems retired years ago. A project folder contains final, final-final, and really-final copies.
This is normal. File shares have been used for decades because they are simple. They are easy to create, access, and expand. This simplicity is also why they tend to grow into large, unstructured repositories with limited ownership and inconsistent governance.
A file share to SharePoint migration creates an opportunity to fix these issues. This should not be treated as a straight copy exercise: if the goal is moving the same folder structure into SharePoint Online, the organization is likely to end up with the same confusion in a newer platform. The better opportunity is to use the migration to clean up content, reduce duplication, redesign the information architecture, and give users a SharePoint environment they can trust.
A Migration Exposes What the File Share has Been Hiding
File shares often look manageable from the top level. The first few folders may appear organized by department, function, region, or project. The difficulty usually starts a few levels down. Teams create their own naming conventions. Old departments disappear but their folders remain. Users copy content instead of linking to it. Sensitive files are mixed with general collaboration content. Some folders become working areas, some become archives, and some become dumping grounds. Over time, the file share stops being a system of record and becomes a shared memory of how work used to happen. This creates problems during migration.
Large volumes of content take longer to scan, package, move, validate, and reconcile. Deep folder structures may not translate cleanly into SharePoint. Duplicate files increase storage and clutter search results. Unclear ownership slows decision making. Permissions that made sense in a file server model may not align well with SharePoint sites, Microsoft 365 groups, Teams, or modern sharing controls.
The migration team can almost always move the content. The harder question is whether all of it deserves to move.
File Share Cleanup Before Migration is Not Just Housekeeping
File share cleanup before migration is often described as removing old junk. That is certainly part of it, but it is too narrow a description.
Good cleanup gives the organization a better understanding of the source environment before decisions are made. IT can assess the technical volume, records and information managers can identify business value and retention concerns, governance teams can pinpoint sensitive, duplicate, or unmanaged content, and business owners can make practical decisions based on evidence rather than folder names alone.
At a minimum, cleanup should answer a few basic questions:
What content do we have?
Who owns it?
What is duplicate, obsolete, or low value?
What should be retained, archived, deleted, or reviewed?
What content needs stronger access controls?
What structure should it move into?
These questions are not just technical. They are operational. If the organization cannot answer them before migration, SharePoint becomes the place where the uncertainty lands.
Deduplication Should Be Handled Carefully
Duplicate files are one of the most common problems in file share migrations.
Some duplicates are harmless; others create real confusion. A policy document may appear in multiple department folders. A contract may be copied into legal, finance, procurement, and project folders. A spreadsheet may exist in several locations with small differences, and no one is certain which one drove the final decision.
A useful deduplication approach separates identification from resolution. First, identify where duplicate files exist. Then define rules for what should happen next. Those rules may consider location, owner, date, file type, business function, or whether a folder is considered authoritative.
For example, an organization may decide exact duplicate files in personal working folders can be removed when the same file exists in an approved departmental library. It may also decide duplicates in legal, finance, or regulated records areas require review before deletion.
This distinction matters. Deduplication is not just about reducing storage. It is about reducing uncertainty. Users should not have to open five copies of the same document to decide which one is reliable.
Do Not Rebuild the Old Folder Maze in SharePoint
Design your information architecture before you migrate.
One of the biggest mistakes in a file share to SharePoint migration is rebuilding the old folder structure exactly as it exists today. While this feels safe because it preserves what users already know, it also avoids difficult design conversations and can create long-term problems.
SharePoint is not just a cloud version of a network drive. It works best when content is organized around a clear information architecture that includes SharePoint sites, document libraries, folders, metadata, permissions, ownership, and governance rules.
Before migration, take the time to define the target structure. A good SharePoint information architecture does not need to be complicated. In many cases, the best design is the most straightforward. In practice, this looks like department sites for department-owned content. Project or program sites for work with a defined team and lifecycle. Document libraries for major content groupings. Metadata where it helps users filter, search, classify, report, or apply governance. Permissions aligned to sites and libraries wherever possible.
The key is to avoid designing only from the file path. Metadata should also be part of the design but should not become a burden. File shares usually depend on folder names, file names, and user memory. SharePoint gives organizations better options, but over-designing metadata can make the system harder to use. If users are forced to complete too many fields, they may avoid SharePoint, store content elsewhere, or enter poor-quality values just to move on.
Permissions also need to be handled as part of the information architecture, not as a separate technical task. File share permissions are often complicated. They may include nested groups, inherited permissions, broken inheritance, legacy access rules, and users who no longer work in the same role. Some permissions reflect real business needs. Others are leftovers from years of exceptions. Migrating permissions exactly as they are into SharePoint may preserve access but also preserves the mess.
Cleanup decisions also influence how governance controls can be applied after migration.
Consider Records and Retention Before Content Moves
Older file shares often contain a mixture of active documents, reference material, convenience copies, official records, and content that should have been deleted years ago.
Once this content moves into SharePoint Online, the organization may want to apply retention labels, retention policies, sensitivity labels, or other Microsoft Purview controls. These controls work better when the target location has a clear purpose.
It is much easier to apply retention to a well-structured library of contract records than to a large, migrated folder containing contracts, drafts, invoices, meeting notes, and old exports. It is also easier to manage sensitive information when the site, library, ownership, permissions, and metadata all support the same governance model.
What Good Cleanup Changes After Migration
The benefits of cleanup are most visible after the migration is complete, as a cleaner migration produces a cleaner SharePoint environment. Search results are more useful because users are not sorting through the same file that has been duplicated across multiple libraries. Storage is reduced because unnecessary duplicate files and obsolete content were not carried forward without review. Permissions are easier to maintain because access was designed around sites and libraries rather than inherited file share exceptions.
The user experience improves as well, as people are more likely to trust SharePoint when the structure makes sense. They can find the current version of a document. They understand where a new file belongs. They are less likely to create shadow storage in OneDrive, Teams chats, or new unmanaged sites.
Governance also becomes more realistic. It is easier to apply retention, sensitivity, lifecycle, and ownership controls to content that has a clear home. Records managers can focus on content with business value instead of sorting through years of duplicates and abandoned folders. IT can support the environment without managing an endless set of exceptions.
Where Peregrine Fits
At small scale, organizations can often manage cleanup with scripts, exports, and manual review. As content volumes grow, however, visibility, consistency, and traceability become increasingly difficult to maintain.
Peregrine helps organizations assess, clean up, and migrate file share content into SharePoint Online with greater control and ease. The tool supports duplicate detection, ROT identification, metadata mapping, permission rationalization, migration waves, and traceability through the migration process.
The value lies not only in moving content. Rather, it lies in the organization getting better visibility before, clearer rules during, and a better governed SharePoint environment after the move.
Cadence Solutions helps organizations plan and execute file share to SharePoint migration projects across Microsoft 365, SharePoint Online, and legacy content environments.
If your organization is preparing for a file share cleanup or SharePoint Online migration, book a Peregrine demo to see how Cadence helps reduce migration volume, improve governance, and build a cleaner foundation for SharePoint.