Cross-Tenant SharePoint and OneDrive Migrations During Machinery-of-Government Changes

When Western Australian agencies undergo machinery-of-government changes, functions move between departments and the information that supports those functions must move with them. Restructures frequently reassign entire programmes, and the SharePoint sites, document libraries, and OneDrive content underpinning that work often sit in a Microsoft 365 tenant that no longer aligns with the responsible entity. The challenge is not simply copying files; it is transferring active workloads while preserving the context, permissions, and collaboration history that public servants rely on every day.

Cross-tenant migration is the discipline of moving that content from one Microsoft 365 tenant to another in a controlled, auditable way. Done well, it lets a reassigned team continue its work with minimal disruption and without leaving orphaned records behind in a source tenant. This article explains how the Microsoft-native cross-tenant migration tooling supports these moves, how to preserve metadata and sharing links, and what agencies should plan for when content must follow a reassigned function.

Why machinery-of-government changes complicate content mobility

Machinery-of-government changes rarely respect tidy technical boundaries. A single restructure can split a business unit across two new departments, absorb a function into an existing agency, or stand up an entirely new entity that requires its own tenant. Each scenario places different demands on the underlying content, because SharePoint sites and OneDrive accounts carry not only documents but also version history, retention labels, permissions, and links embedded in emails, Teams messages, and other documents.

These dependencies are precisely what make a naive copy-and-paste approach risky. If sharing links break, staff lose access to material they were actively using, and records managers lose the audit trail that demonstrates compliance with the State Records Act obligations that WA agencies must meet. A well-planned cross-tenant migration treats content as a live system of record rather than a static archive, so that the receiving agency inherits a working environment rather than a disconnected file dump.

The Microsoft-native cross-tenant migration tooling

Microsoft provides first-party capability for moving SharePoint sites and OneDrive accounts directly between tenants, without exporting to an intermediate location. This tooling operates at the tenant level and is administered through PowerShell, allowing administrators in both the source and target tenants to establish trust, scope the content in play, and schedule the moves in stages. Because the transfer happens within the Microsoft 365 service boundary, content does not need to traverse third-party storage, which reduces exposure and simplifies data handling for sensitive government information.

The cross-tenant SharePoint and OneDrive migration features form part of SharePoint Advanced Management, which is a licensed add-on rather than a capability included in every plan. Agencies should confirm licensing prerequisites early, because the commercial model influences both cost and timing. It is also worth recognising that the tooling supports a staged approach: administrators can pilot a small set of sites, validate the outcome, and then progressively migrate larger workloads, which suits the phased nature of most restructures.

Preserving metadata, permissions, and sharing links

Metadata is the connective tissue of a SharePoint environment, and its preservation is central to a successful move. Content types, managed metadata columns, version history, and created and modified attributes all carry meaning for records management and discovery. The native cross-tenant tooling is designed to retain these properties during migration, so that a document arriving in the target tenant still reflects who authored it, when it changed, and how it is classified, rather than appearing as a freshly created file with no provenance.

Sharing links and permissions deserve particular attention, because they determine whether people can keep working after cut-over. The migration process maps identities from the source tenant to the corresponding accounts in the target tenant, which means identity planning must happen before any content moves. Where a user does not exist in the target tenant, their permissions cannot be reconstructed accurately, so agencies should reconcile their directory, provision accounts, and validate group memberships in advance. Testing a representative sample of shared documents after migration confirms that links resolve correctly and that access aligns with the receiving agency's security posture.

Planning, security, and governance considerations

Successful cross-tenant migrations begin with discovery rather than tooling. Agencies should inventory the sites, libraries, and OneDrive accounts in scope, identify their data classifications, and map the retention and sensitivity labels that must persist. This is also the moment to confirm that the target tenant enforces equivalent or stronger controls, so that content does not lose protection when it changes hands. Aligning migrations with the Australian Cyber Security Centre's Essential Eight and with the receiving agency's information security policies helps ensure the move strengthens rather than weakens the overall posture.

Change management and communication are equally important, because a restructure affects people as much as data. Staff need clear guidance on what will move, when access will change, and how to report problems during and after cut-over. A defined validation window, a rollback position, and a documented decommissioning plan for source content together reduce the risk of confusion, duplicated records, or inadvertent retention breaches. When these governance elements are settled before the technical work begins, the migration becomes a predictable, low-disruption event that lets a reassigned function continue serving the public with its information intact.

References

• Microsoft Learn: Cross-tenant OneDrive migration
• Microsoft Learn: SharePoint Advanced Management
• Australian Cyber Security Centre: Essential Eight