IDENTITY
PENDINGMapping readiness
Check that each user in the old environment is matched to the right user in the new one.
No validation saved yet.
Mapping result
Mappings0
Errors0
Warnings0
Saved locally. No identity rows are stored.
Microsoft 365 migration workspace
Prepare a Microsoft 365 migration step by step.
Create a local project, follow one next step at a time and keep the important readiness checks together before the move.
01 / PROJECTS
Migration projects
Create a project. Opselith will show one next step at a time.
0 local projects
Create migration project
Imports are parsed locally and limited to 1 MB.
No migration projects are stored in this browser yet.
ACTIVE PROJECT
Migration project
Mapping pending
User mappingPending
Exchange OnlineNot started
Domain moveNot started
Selected scope0 workloads
SourceSource organizationsource.example.com
TargetTarget organizationtarget.example.com
EXCHANGE ONLINEExchange readinessNOT STARTED
Validate recipients first. When they pass, confirm the tenant setup here.
No recipient readiness summary saved yet.
Recipient result
Recipients0
Ready0
Review0
Blocked0
Saved locally. No recipient rows are stored.
TENANT SETUP
Only confirm what you verifiedConfirm the Exchange connection
What is being confirmed?
These are tenant-level confirmations for Microsoft's native cross-tenant mailbox move path. Opselith records only your local confirmations and does not connect to either tenant.
MICROSOFT TEAMSTeams chat & meeting readinessNOT STARTED
Confirm only the tenant and user prerequisites that are in scope for the Microsoft cross-tenant Teams path.
OPTIONAL SUPPORTING SCRIPTExport Teams inventoryRead-only inventory to support this readiness check.
Scope boundary
Microsoft’s native orchestrator migrates Teams chats and meetings, not Teams/channel shared content. SharePoint-backed content belongs in the SharePoint preparation path. Opselith stores only these local confirmations.
ONEDRIVEOneDrive readinessNOT STARTED
Confirm the source account, target user and target-site boundaries before scheduling native OneDrive moves.
OPTIONAL SUPPORTING SCRIPTExport OneDrive site inventoryRead-only OneDrive inventory for source readiness review.
Why these checks?
Native cross-tenant OneDrive moves fail when the target OneDrive already exists. Source accounts must be Read/Write, target users must be prepared, and the tenant relationship and identity mapping must be ready. Opselith stores only your confirmations.
DOMAIN CUTOVERDomain readinessNOT STARTED
Use this checklist only when the source domain will be detached and moved. Mark an item only after you have verified it.
OPTIONAL SUPPORTING SCRIPTExport Microsoft 365 domain dependency reportRead-only dependency report before domain cutover.
Why these checks?
Microsoft 365 cannot remove a custom domain while users, groups or other tenant objects still depend on it. DNS and mail-flow changes should also be planned before cutover. Opselith records only your confirmations; it does not inspect either tenant.
Selected areas · 0
About this workspace
A local foundation for Microsoft 365 migration work
Migration Workspace keeps preparation context and review checkpoints together before any migration tool or script performs changes. Projects can be exported as JSON for backup or transfer between browsers.
Built to grow with the migration
User mapping, Exchange, Teams chat/meeting, SharePoint, OneDrive and domain cutover readiness now share the same local project. Vendor-specific preparation can attach to this project later without changing the local-first boundary.