Migrate Teams, mailboxes, OneDrive, SharePoint, and chat history between Microsoft 365 tenants. Production-validated: 153,584 files, zero errors.
Frequently asked questions
Does migration data go through gtools.pro servers?
No on Desktop — data flows operator machine → source tenant → destination tenant with no third-party server in the loop. On Cloud, only ciphertext transits.
Are Teams chats and channel messages migrated?
Yes, including channel messages and 1:1 chat history. BitTitan caps Teams at 100 GB; GTools.pro has no fixed cap.
How is this priced compared to BitTitan and ShareGate?
Time-boxed project SKU instead of BitTitan's per-user $57 consumable or ShareGate's $5,995–$17,995/year machine-based license.
Is EU data residency supported?
Yes. Desktop runs on the operator machine, so residency is whatever the operator chooses. Cloud lets you pick the region; ciphertext only.
Limitations of tenant-to-tenant migration
Move handles Microsoft 365 → Microsoft 365 migrations only. Cross-platform migrations (Google Workspace, Slack, Box) are out of scope — BitTitan, ShareGate, or Quest are better fits there. Throughput is capped by Microsoft Graph throttling on both source and target tenants (~400 requests / 10 s per app per tenant) plus destination ingestion quotas.
Some workloads ride limited Graph surfaces today: Teams private-channel chat history, retention-label propagation across libraries, and per-user OneDrive sharing-link rewrites all carry caveats documented in the migration runbook. Items already present at the destination are detected via content hash and skipped; conflict-merge rules are configurable but never silent.