IT leads in a merger
You have a date, two tenants and a board that wants "seamless". Waves by department, delta passes nightly, one cutover evening, a report for the file.
Every route has been done with PST files, with the platforms' own tools, or by hand. Here is what each costs you in downtime, fidelity and weekends.
| MigrateX | PST / Takeout exports | Built-in platform tools | By hand or consultant | |
|---|---|---|---|---|
| Downtime for users | None until a guided cutover evening | Days: export, transfer, import per user | Varies; usually a switch date with a gap | Depends on the person and the hour |
| Mail with dates, read state, folders | Yes, on every route | Folders yes; dates and read state often reset | Mail only, same platform only | Yes, if done carefully |
| Shared mailboxes with rights | Recreated with Full Access, Send As, aliases | Not covered | Not covered | Manual re-creation, easy to miss |
| OneDrive / Drive sharing and permissions | Re-granted to matched people; links listed | Lost | Partial, same platform only | Manual re-sharing |
| SharePoint, sites, shared drives | Sites with URL alias, libraries and roles | Not covered | Limited, same platform only | Rebuilt by hand |
| Teams / Chat history with original authors | Migration-mode import keeps authors and dates | Not possible | Not covered | Not possible |
| Between Microsoft 365 and Google Workspace | Both directions, converted field by field | Mail only, via files | Google offers mail-only imports | Mail only, slowly |
| Exchange Server (on-premises) to Microsoft 365 | Mailboxes and public folders over EWS; no hybrid, no PST | PST per mailbox; public folders by hand | Hybrid or cutover migration: setup-heavy, no public folder contents | Days of PowerShell |
| Zoho Mail to or from Google Workspace | Mail, contacts and calendars over IMAP/CardDAV/CalDAV; one CSV of app passwords | Export per mailbox, import per mailbox | Google's mail-only import; Zoho's inbound migration tool | Client-by-client IMAP copying |
| Target accounts, groups and contacts created | Directory sync from Active Directory, Entra ID or Google — previewed first | Not covered | Active Directory to Entra ID only | CSV imports and scripts |
| Delta sync until cutover | Unlimited, free | Re-export everything | Sometimes, with limits | No |
| Per-item verification | Every folder and drive compared; missing items copied in one click | Count PST sizes and hope | No | Spot checks |
| Admin passwords shared | Never — application permissions | Often, or per-user passwords | No | Usually |
| Data stored outside the tenants | Nothing — streamed through memory | Yes, on laptops and drives | No | Yes, on someone's machine |
| Change record | Printable sign-off report + CSV, audit log | A folder of files | Logs | Whatever was written down |
| Cost model | Per person migrated; passes free | "Free" plus days of admin time per user | Free, limited scope | Day rates, scale with size |
Built-in tools change over time; check the current scope of each platform's own migration features for your case.
You have a date, two tenants and a board that wants "seamless". Waves by department, delta passes nightly, one cutover evening, a report for the file.
Several customers, several routes, one panel. Roles per customer, licenses pooled per organization, notifications to your own Teams channel.
Charge for judgement, not for babysitting exports. Let the engine run overnight and bring the verification report to the client.
Acquisitions arrive on the other platform. Bring them across with their history instead of asking them to start from zero.
Run the free assessment on a real source tenant. If the findings don't tell you something you didn't know, you have lost ten minutes.
Answers from the documentation.
Hi. Ask me what a status means, why an item stopped, or what to do next. I answer from the documentation.
I can’t change anything or see message contents. For billing or a person, use contact.