Migrate from Proton to Pipedrive

Proton Contacts in vCard format (name, email addresses, phone numbers, physical addresses, organization name, and custom fields) map to Pipedrive People records. We extract contacts via Proton Contacts API, preserving the full vCard field taxonomy, then map to Pipedrive's name, email, phone, address, and organization link fields. Any Proton contact custom fields migrate as Pipedrive custom fields on the People object. Proton Plus plan and above are required for full API access to contacts export.

Proton does not have a standalone Organization object; the organization is stored as a text field on the Contact record. We extract the organization name, deduplicate across all contacts (case-insensitive, trimmed), create one Pipedrive Organization per unique organization name, then link each People record to its corresponding Organization via the Pipedrive org_id field. This creates a normalized Organization list in Pipedrive from Proton's flat contact structure.

Proton Calendar events (title, description, location, start/end time, attendees, and recurrence rules) map to Pipedrive Activities. Single-occurrence events with no linked people map as Tasks. Events with attendee lists map as Meetings with attendee entries added to the Activity. Recurring events expand into individual Activity records per occurrence. Each Activity is linked to the corresponding People record via the Person ID when an attendee email matches a migrated Pipedrive People email address.

Proton team members on a paid plan map to Pipedrive Users. We extract user display names and primary email addresses and match them to Pipedrive User records by email. If the Proton plan has more users than the target Pipedrive tier allows, we scope migration to the active users the customer identifies and defer the rest. Pipedrive Essential supports up to 5 users; higher tiers support more with admin role assignment.

Proton Mail messages do not have a native Pipedrive equivalent because Pipedrive's data model does not include an email message object. We offer two preservation paths: (1) export email threads as .mbox or .eml files and attach the compressed archive to the corresponding Pipedrive People or Organization record, or (2) export individual relevant emails as PDF or EML and attach them as individual files. The customer chooses during scoping which path applies to which contact segment. This is a file attachment migration, not a native record migration.

Proton Workspace supports up to 15 custom domains on Standard and 20 on Premium. Custom domain addresses used by team members map to additional email fields on the corresponding Pipedrive People record. We do not migrate MX, SPF, DKIM, or DMARC DNS records — these are DNS registrar configuration items handled separately. Custom domain routing after Proton deactivation requires updating DNS and setting up the domain in Pipedrive's email settings if the customer wants Pipedrive-sent emails to use the custom domain.

Proton Mail supports up to 10 hide-my-email aliases on Mail Plus and unlimited on Unlimited and higher. Aliases do not map to standard Pipedrive People fields. We extract aliases as a comma-separated list and store them in a custom Pipedrive People field (text or multi-line) so that the alias inventory is preserved for the customer's admin to configure forwarding rules or reply-to handling in Pipedrive.

Proton Mail labels (tag-style with color coding) and folder hierarchy (hierarchical) do not have a native Pipedrive equivalent. We extract the label taxonomy and folder structure and append them as a structured note on the relevant People or Organization record. Pipedrive's tagging feature can be used for label replacement if the customer specifies which Proton labels map to Pipedrive tags during scoping.

Proton Drive stores files with end-to-end encryption. We extract file binaries and folder structure by decrypting client-side, then attach relevant files (such as proposals, contracts, or documents shared with specific contacts) to the corresponding Pipedrive People or Organization record as file attachments. This is scoped per-customer to the files they identify as relevant to their Pipedrive contacts, not a full Proton Drive export. Proton Drive version history (365-day on Professional and Premium) is not migratable as version history but the current file version is included.

Proton Drive generates shareable links with optional password protection and expiration dates. We preserve the original Proton share link URL and access settings in a Pipedrive custom field on the related People or Organization record. These links become non-functional at the destination because they point to Proton infrastructure, but the URL record preserves the sharing context for audit purposes.

Proton for Business organizes users into teams with role-based access. We extract user accounts, roles, and team membership and map them to Pipedrive Users with matching role assignments (admin, member). Pipedrive does not have a standalone team object; team membership is managed through user groups. We create Pipedrive user groups matching Proton team names during migration so that Pipedrive activity assignment can reference team groupings.