ElephantsPlan the route. Validate both sides. Migrate with evidence.
Identify where historical email is stored, confirm that the selected route can read it, prepare destination capacity and validate archive outcomes separately from the primary mailbox.
Migration orchestration—not permanent data storage.
From connection to verified results
Identify every archive location
An online archive, a local PST or MBOX file, a desktop cache and messages in ordinary server folders are different sources. Inventory ownership, format, size, item count, encryption and accessibility before selecting a migration method.
Confirm route support honestly
Standard IMAP does not guarantee access to a provider-native online archive or local file. Confirm the current supported source and destination combination in ElephantsData and use a separate approved workflow where the archive cannot be read directly.
Prepare destination capacity
Check Exchange Online licensing, primary and archive quotas, automatic expansion behavior, retention policies, holds and accepted item sizes. Decide whether historical data belongs in the primary mailbox, online archive or another governed repository.
Pilot and validate historical data
Test old messages, deep folders, large attachments, unusual character sets and encrypted or malformed items. Reconcile archive results independently and document skipped, failed and intentionally excluded content before source retirement.
Questions to answer before migration
Is archive mailbox migration planning 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 archive mailbox migration planning 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.