How it works
A clear process from setup to completion
Migration Platform follows the same six-step workflow for every migration project, regardless of source or destination platform. Each step is discrete, reversible, and designed to surface problems before they affect your data.
The six steps
Choose your source and destination platform — Microsoft 365, Google Workspace, or Exchange on-premises — and give the project a name. Source and destination can be the same platform type or different.
For Microsoft 365, guided setup walks you through Azure app registration, API permission assignment, and admin consent — or enter credentials manually if you have an existing app. For Google Workspace, provide a service account JSON key with domain-wide delegation.
A non-destructive scan enumerates all reachable mailboxes on the source, counts mail folders, mail items, calendar entries, and contacts, and generates size estimates. No data is written to the destination at this stage.
Mailboxes with a clear source-to-destination match are auto-suggested. Exceptions are surfaced for manual resolution — override a mapping, exclude a mailbox, or flag missing destination mailboxes for automatic creation.
Migrations consume prepaid credits at a flat rate per mailbox. Ensure the account balance covers the run before launching — the platform checks and holds credits before the first item transfers.
Launch the migration and track progress at both project and per-mailbox level. Open the mailbox log for any in-flight mailbox to see transfer rate, items per minute, health status, and a full chronological event log.
Migration modes
Run exactly what you need
Each project supports four run modes that can be used independently or in sequence, giving you full control over what transfers and when.
Enumerates all mailboxes, counts folders and items, and estimates sizes. Builds auto-suggested mappings. No data written to the destination. Free to run — no credits consumed.
Replicates the source folder hierarchy at the destination without migrating any mail items. Useful for validating mapping accuracy and pre-staging the environment before a full run.
Copies all mail items, calendar entries, and contacts from source to destination. One credit per mailbox is consumed at run start. Options let you include or exclude calendars and contacts independently.
Transfers only items that have changed or arrived since the last full run. Ideal for keeping a destination current during a cutover window. Delta runs are free — no credits consumed.
On-premises Exchange
Migrations to and from Exchange Server
On-premises Exchange is supported as both source and destination. Two connectivity options are available to handle different network configurations.
Used when the Migration Platform platform has direct network access to the Exchange server over HTTPS. Credentials are validated and connectivity confirmed before any migration run begins.
A small Windows executable runs inside the customer network and polls for work over outbound HTTPS — no inbound firewall rules required. The connector handles credential storage and EWS communication locally.