A migration tool needs broad access to your tenants. Here is exactly how Aatrex connects, what it keeps, and how your administrators stay in control.
Microsoft 365 tenants connect through Microsoft admin consent to the Aatrex app. Google Workspace connects through a service account with domain-wide delegation. Aatrex never asks your users for their passwords — IMAP sources are the one exception, where the protocol itself needs a per-mailbox login.
Aatrex requests only the scopes each migration needs (for example, read-only on the source side of a Google move). Your administrators can revoke access at any time — remove the app consent in Microsoft Entra ID, or delete the delegation in the Google Admin console — and every job stops.
Client secrets, service-account keys, certificates and IMAP passwords are encrypted in the database with AES-256-GCM. Traffic between Aatrex, your tenants and your browser is encrypted with TLS.
Mail, files and messages stream from source to destination. Aatrex keeps what it needs to run and prove the migration — users, mappings, job status, item counts and logs — not copies of your content.
Who started, paused, retried or changed what is recorded in the project activity log. Item-level migration logs show what moved, what was skipped and why.
Migration logs are kept for 180 days by default, then deleted automatically. Ask us if you need a different retention period.
Organization admin, project manager and viewer roles control who can connect tenants, start migrations or only watch progress.
Aatrex runs on cloud infrastructure in India. For a data processing agreement, the sub-processor list or a security questionnaire, email us.
Found a security issue, or need our DPA or sub-processor list? Email support@aatrex.in. See also our Privacy Policy and Terms.