Scope before you move
Start with an inventory: which teams own which trees, what can be archived instead of migrated, and who the MANAGER of each target team folder will be. The Migration Center binds every import job to one target team folder, so this mapping is the whole plan.
- Create the target team folders first and assign MANAGERs.
- Use one import job per source tree; jobs are idempotent to create.
- Store source credentials only in the job — they are envelope-encrypted and never displayed again.
Dry-run everything
A dry run is mandatory before any import runs. It produces a manifest — folder count, item count, total bytes and an entry preview — while writing nothing. Review it with the folder's MANAGER and confirm the scope matches expectations.
Run, verify, cut over
The run recreates the source tree as subfolders and lands every file in quarantine until it passes the malware scan, so imported content meets the same bar as uploads. Per-item failures are listed in the report without aborting the rest.
- Verify the report's per-item errors and re-run — existing folders are reused, not duplicated.
- Cut users over team by team; keep the source read-only during the transition window.
- Retire the source only after MANAGERs sign off on their trees.