Follow one small batch from your first project to verified destination access.
3 min readUpdated
Quick answer
Create a project, connect both tenants, scan and match the content, then prepare, review, approve, and verify a batch.
Your next step
Start with a small site whose content has already been migrated. Keep the source available for the scan and final safety check.
Before you begin
Have an administrator available for each Microsoft 365 tenant connection.
Migrate the files and folders to their destination first. Confirm the destination content opens correctly.
Choose a small, representative pilot: a direct user share, a shared folder, and an external guest if those are in scope.
Know the destination account or group for each source recipient. Check Account and credits before approving changes.
1. Create and connect the project
Open Projects and select Create project. Give it a name your team recognizes.
Connect the source tenant, then connect the destination tenant. Review the tenant shown after each Microsoft consent flow.
If a different administrator must approve access, use the connection link from the relevant tenant card and have that administrator complete it.
2. Find and match the content
Expand Scan options. For a pilot, choose Specific site URLs and enter the source and destination site addresses separately.
Choose whether Restore shares to groups should be on. Leave it off when you want user-level restoration, including users found through shared groups.
Run Scan source tenant and Scan destination tenant. Wait for each scan to finish.
Match each source site or OneDrive to the correct destination, select the matched items, and create a batch.
3. Prepare and review the batch
Open the batch and follow Prepare batch. ShareRestore inventories the selected content and builds the proposed access changes.
In Review and approve, inspect destination paths, recipients, and Read or Edit access. Use the filters to inspect blocked and review entries.
Resolve unmatched people or groups. Choose Save decisions and prepare again, then review the rebuilt plan.
Confirm the credit estimate and scope before using the approval action. Only eligible, approved changes can run.
4. Restore and verify
Approve the reviewed batch. ShareRestore checks whether the source changed before it proceeds with destination changes.
Follow Restore access for background progress. If the source changed, review the safety-check decision instead of repeatedly approving.
Open Verify results. Separate verified changes, already-present access, skipped entries, and failures.
Test the destination with representative recipients. Check both what they can open and whether their access level is correct.
Save review/result exports or an audit package before expanding to a larger batch.
Common questions
Do I need to finish the whole migration first?
The destination content in the batch must exist before its access can be restored. You can work in smaller migrated batches while other content is still being migrated.
Does opening the app or preparing a batch change sharing?
No. Destination changes occur during approved restore execution, after the preparation and review steps.
