Migrate your Proton data

Proton Mail messages are encrypted on the client before transmission. We extract messages via the IMAP bridge export or direct E2E decryption during import, preserving subject, body, sender, recipient, timestamp, read status, and attachments. Folder hierarchy maps to Labels in Proton Mail.

Each paid Proton plan supports multiple encrypted email addresses. We migrate all addresses within the organization's plan scope, mapping each to a corresponding user identity at the destination. Catch-all domain addresses are preserved individually.

Proton Mail supports up to 10 hide-my-email aliases on Mail Plus. We extract these as separate address objects and map them to equivalent alias or forwarding rules at the destination, noting that destination platforms may handle aliases differently.

Proton Calendar events include title, description, location, start/end time, reminders, attendees, and recurrence rules. We extract calendar data via Proton Calendar API and map events into the destination calendar's native object model, preserving all event properties.

Proton Contacts include name, email addresses, phone numbers, physical addresses, and custom fields. We export contacts in vCard format and map fields to the destination CRM or address book object, preserving all available properties.

Proton Drive stores files with end-to-end encryption. We extract file binaries and folder structure, decrypting client-side. Version history (up to 365 days on Professional) is included when within scope. Shared links and permissions are mapped to the destination's sharing model.

Workspace Standard supports up to 15 custom domains; Workspace Premium supports up to 20. We extract domain configuration and DNS records, then map them to the destination's domain verification and routing setup. MX and SPF records must be reconfigured at the DNS level after migration.

Proton Mail uses both folders (hierarchical) and labels (tag-style, with color coding). We preserve the full label taxonomy and folder hierarchy and map them to the destination's equivalent organization system, whether that uses folders, tags, or both.

Proton for Business organizes users into teams with role-based access. We extract user accounts, roles, and team membership and map them to the destination's user and permission model. Shared mailboxes on Enterprise require additional scope definition.

Proton VPN configuration profiles are platform-specific and tied to Proton's infrastructure. We do not migrate VPN tunnel configurations as they cannot be meaningfully mapped to other VPN providers. VPN subscription data is noted for billing reconciliation during account migration.

Proton Pass stores credentials in an encrypted vault. We extract entries in a structured format and map them to the destination password manager. Because Proton Pass uses E2E encryption, the migration requires the customer's encryption key to be available during extraction.

Proton Drive generates shareable links with optional password protection and expiration. We preserve link URLs and access settings, but links to Proton infrastructure become invalid at the destination. We flag all shared links for customer review before migration to identify which need to be recreated.