Workstream 01
Prepare source and target relationships correctly
Record source and target tenant IDs, the affected user identities, legal ownership, administrator access, required add-on licences, data size and business restrictions. Confirm the appropriate SharePoint administrator relationships and PowerShell module prerequisites in current Microsoft documentation. The source OneDrive must meet Microsoft eligibility requirements; read-only or unsupported configurations may block a move.
Ask whether there are Customer Key, preservation or hold considerations and whether affected content can legally transfer to the new organisation. A migration tool cannot answer a divestiture's data ownership questions. Do not 'fix' compliance blockers by removing holds without the authorised records owner.
| Preflight item | Example failure | Required evidence |
|---|---|---|
| Target OneDrive site | Site was already created for user | Target provisioning check and remediated design |
| Cross-tenant licence | Required add-on not purchased/assigned | Entitlement per migrating user |
| Source state | Source OneDrive is read-only or ineligible | Source eligibility check |
| Legal/retention scope | Content subject to preservation obligation | Data owner and compliance sign-off |
Workstream 02
What data movement does and does not prove
Microsoft's native method moves file content and has link-redirection behaviour, but a redirect alone cannot guarantee every app, shortcut and externally shared resource works as before. Links embedded in CRM records, Teams channels or departmental workflows may still require manual validation. Different content stores such as SharePoint sites must not be silently considered covered by a personal OneDrive move.
Create a user-focused acceptance list with representative folders, files, shared links, edits, version history and authorised guest access. Sample large or complex items as well as a normal file. Record exceptions by owner, not simply count migrated objects.
Workstream 03
Plan the window and identify the stop conditions
Avoid treating the transfer as a repeated incremental sync that can run forever. Microsoft's native OneDrive workflow has its own scheduling and completion characteristics; the coordinated Migration Orchestrator may impose workload sequencing. Decide when the user stops editing the source and how they are told to start in the target. Establish which settings can be safely recovered if validation fails.
During a merger or split, staff may need controlled source access for an agreed period. Write down the cutover communication and the ownership of data left behind. The original site may redirect for users, but downstream application permissions still need separate acceptance.
What to capture before the decision
- Confirm target OneDrive is not provisioned
- Check source eligibility, licence and identity mapping
- Agree freeze/cutover and new sign-in instructions
- Test sharing and actual edit access as a normal user
- Document residual source records and aftercare
Workstream 04
Price the exception work rather than only file volume
Ask for distinct scope lines for user preparation, OneDrive transfer, restricted or unsupported content, sharing remediation, link repair, client setup and aftercare. An estimated volume cannot by itself identify guest permissions, legacy links or legal preservation requirements. Confirm any SharePoint or Teams work separately.
Require a pilot and an objective handover pack: user mapping, source and target inventory, transfer results, exception list and owner-accepted tests. An agreement should clearly define which content remains out of scope and who will manage the destination after delivery.
OneDrive cross-tenant migration is a controlled identity-and-content transfer. The most expensive mistake is letting target provisioning and user communications drift away from the technical move.
Source documents and limitations
These references establish current vendor behaviour; they do not verify an individual customer's configuration or imply Microsoft affiliation. Technical claims should be rechecked before execution.