Migrate from Proton to Twenty CRM

Proton Contacts (name, email addresses, phone numbers, physical addresses, and custom fields) map directly to Twenty People. We export contacts in vCard format from Proton Contacts, parse each field (givenName, fn, email, tel, adr, org), and map them to Twenty's name, email, phone, address, and companyName fields. Custom fields on Proton contacts migrate as custom fields on Twenty People, created in Settings → Data Model before import. Multi-value email addresses on a single Proton contact create multiple People records with a shared external ID for relationship reconstruction at the destination.

Proton Contacts with an organization field (org, orgunit, title, role) are extracted as a preliminary Company deduplication pass. Where a Proton contact has no org field but shares a domain with other contacts, we derive a Company record from domain grouping. Twenty Company is created before the related People import so that the companyId lookup is satisfied at insert time. Domain becomes the Company domain field for dedupe.

Proton Calendar events (title, description, location, start/end time, reminders, attendees, recurrence rules) map to Twenty Task records. We set Task title from the Proton event summary, description from the event body, dueDate from the event start, and status based on completion state. Recurrence rules are documented in a separate recurrence mapping note since Twenty's Task does not have native recurrence — the customer's admin configures a recurring task pattern post-migration if required. Attendees migrate as Task relations to People records where email matches exist.

Proton Calendar event details with rich description, location, and attachment references migrate to Twenty Note records attached to the parent Task. This preserves event context beyond what the Task title and due date capture. Notes are linked via ContentDocumentLink to the corresponding Task for a complete activity timeline in Twenty.

Proton user accounts within an organization's workspace map to Twenty Members. We extract workspace members (display name, email) and provision them as Twenty users with matching email for SSO or invite routing. Shared mailboxes in Proton (multiple addresses per account) are documented as aliases on the primary member record and as a written alias inventory for the customer's admin to configure in Twenty email settings post-migration.

Proton Mail supports up to 10 hide-my-email aliases on Mail Plus and unlimited on higher tiers. We extract aliases as separate email address objects and map them to Twenty's email alias configuration on the corresponding People record. Aliases that were used as send-from addresses in Proton contacts become secondary email fields on the related Twenty People record. The customer reviews alias routing post-migration since Twenty does not support true send-as aliases at the same depth as Proton.

Proton Mail labels (tag-style, color-coded) and folder hierarchy (hierarchical) are preserved as Twenty Tags and as custom select fields on People or Company. We map the full label taxonomy to a tag inventory document for the customer to configure in Twenty Settings → Tags. Folders that represent organizational categories (client, partner, internal) become custom picklist fields on People rather than tags for cleaner filtering in Twenty views.

Proton Workspace supports up to 15 custom domains on Standard and 20 on Premium. We extract domain configuration (MX, SPF, DKIM, DMARC records) as a DNS verification checklist. The DNS cutover runs as a parallel workstream: Proton continues receiving mail during propagation, and routing rules are updated at the DNS registrar once Twenty domain verification is complete. This prevents mid-migration email loss from premature MX changeover.

Proton Drive files are end-to-end encrypted binaries stored with Proton's infrastructure. We extract file metadata (filename, path, size, modified date) and create a reference document listing every file that should be re-uploaded to Twenty or a linked storage system. The files themselves cannot be decrypted server-side. We map folder structure as a directory reference so the customer's admin can recreate the folder hierarchy in Twenty's file attachments or a connected storage provider post-migration.

Proton Drive shareable links (with optional password protection and expiration) point to Proton infrastructure and become invalid after migration. We extract link metadata (original URL, access settings, expiration date) as a written inventory for the customer's admin to recreate as Twenty attachments or external links. Links with expiration dates in the past are flagged as already expired and excluded from the inventory.