ElephantsPlan the route. Validate both sides. Migrate with evidence.
Read selected Gmail mailboxes through the Gmail API and deliver supported message content into prepared Exchange Online destinations with resumable processing.
Migration orchestration—not permanent data storage.
From connection to verified results
Source and destination preparation
The Google source requires live Gmail API access for each mapped user. The Microsoft destination must have an active mailbox, required licensing, IMAP application access and effective Exchange service-principal permissions before a batch can start.
Checkpointed message transfer
ElephantsData inventories messages, copies supported raw message content and records per-item outcomes. Durable checkpoints allow a retry or latest-changes pass to continue without restarting every successfully processed message.
Mailbox size and archive planning
Destination mailbox quotas and archive behavior must be confirmed before oversized mailboxes are scheduled. ElephantsData does not describe a normal custom copy as a full-fidelity native archive migration; unsupported or failed items remain visible for review.
Questions to answer before migration
Is Gmail to Microsoft 365 mailbox migration currently free with ElephantsData?
ElephantsData is currently free to use. Provider licensing, storage, API, network and other third-party charges may still apply.
How should I start a Gmail to Microsoft 365 mailbox migration project?
Confirm the supported route, prepare both providers, map each selected source to an explicit destination, run preflight checks and validate a representative pilot before expanding the batch.
Does a successful connection mean the workload is ready?
No. Authentication proves only that a connection can be established. Workload preflight must also verify permissions, destination provisioning, licensing, quota and mappings.
How should migration results be validated?
Review per-user transferred, skipped and failed outcomes, inspect representative destination data and document any route limitations before approving the migration.