Migration Manager for OneDrive and Teams Files: Beyond File Shares

Content consolidation projects rarely stop at the traditional file share. Enterprise and government tenants that have grown organically often hold significant volumes of active material in individual OneDrive accounts and in the document libraries that sit behind Microsoft Teams channels. These locations accumulate quietly, and without a deliberate consolidation strategy they become fragmented, poorly governed, and difficult to search across an organisation.

Migration Manager, available within the SharePoint admin centre, is frequently associated with moving on-premises file shares into Microsoft 365. Its usefulness extends well beyond that first scenario, however, and understanding how it applies to OneDrive and Teams-backed content allows an organisation to plan a controlled cutover rather than a series of ad hoc copies. This article outlines how to approach that broader consolidation with permission remapping and pre-migration remediation firmly in mind.

Why OneDrive and Teams content needs a different lens

OneDrive and Teams files are not simply folders on a network drive. Each Teams channel is backed by a SharePoint document library, and every user has a personal OneDrive that may contain both genuinely personal drafts and business records that belong in a shared, governed location. When these repositories multiply across departments, the organisation loses a single view of where authoritative content resides, and information that should be discoverable becomes trapped in personal or team silos.

Treating this content as though it were an ordinary file share ignores the metadata, sharing links, and version history that give it value. A considered approach recognises that consolidation is as much about restoring governance as it is about moving bytes. Before any migration begins, the organisation should map which content is transient and can be left in place, which is duplicated and can be retired, and which represents records that must move to a managed destination with clear ownership.

Planning the consolidation and remediation

Pre-migration remediation is where most of the risk in a consolidation project is either removed or left to surface later. A discovery pass should identify unsupported characters in file and folder names, excessively long paths, blocked file types, and items that exceed size thresholds, because these conditions commonly cause individual files to fail during transfer. Addressing them before the cutover reduces the volume of post-migration exceptions and gives the project team a realistic view of what will actually move cleanly.

Remediation also involves decisions that no tool can make on the organisation's behalf. Duplicate and redundant content should be rationalised so that the destination does not simply inherit the disorder of the source, and retention obligations should be confirmed so that records are neither prematurely deleted nor migrated without their required controls. For government tenants in particular, aligning the destination structure with information classification and handling requirements is a task best completed during planning rather than after users have begun working in the new location.

Permission remapping and identity considerations

Permissions are the element most likely to break trust in a consolidation effort. Content moved from a personal OneDrive or a departmental team into a consolidated library must arrive with access rights that reflect the destination governance model, not simply a copy of whatever sharing existed at the source. Permission remapping allows source identities and groups to be translated to their correct destination equivalents, which matters where accounts have been renamed, where security groups have been restructured, or where the destination uses a different membership model.

A disciplined approach documents the intended access model for each destination location before migration and validates it afterwards. Broad or inherited sharing links that made sense within a single team may be inappropriate once content is consolidated and more widely visible, so the cutover is an opportunity to tighten access rather than replicate historical over-sharing. Testing permission outcomes with a representative sample of content and users, before the full migration proceeds, gives the project team confidence that the mapping behaves as intended.

Controlling the cutover

A controlled cutover depends on sequencing, communication, and verification rather than on speed alone. Running an initial pass while the source remains in use, followed by an incremental pass that captures changes made in the interim, allows the organisation to keep disruption to a minimum and to schedule the final switch for a period of low activity. Clear communication with affected users about when their content will move, and where it will subsequently live, reduces confusion and the temptation to create yet more scattered copies during the transition.

Verification closes the loop. Migration reports should be reviewed to confirm which items succeeded, which were skipped, and why, so that exceptions are resolved deliberately rather than discovered by users weeks later. Retaining source content in a read-only state for a defined period after cutover provides a safety margin, and a formal decommissioning step ensures the old locations are eventually retired so the fragmentation the project set out to solve does not quietly return.

Conclusion

Extending Migration Manager beyond file shares turns a simple lift-and-shift into a genuine consolidation of an organisation's most active content. By combining pre-migration remediation, careful permission remapping, and a phased cutover, enterprise and government tenants can bring scattered OneDrive and Teams material into governed, discoverable locations without eroding the access controls their obligations demand.

The value of this work lies in the outcome for the organisation and its people: a clearer picture of where authoritative content resides, access that reflects current structures rather than historical accidents, and a foundation for consistent information governance. Approached methodically, consolidation delivers lasting order rather than a one-off tidy-up that unravels within months.

References

• Migration Manager overview, Microsoft Learn
• Prepare and remediate content for migration, Microsoft Learn
• Australian Government Information Security Manual, ACSC