Migrate from Proton to Odoo CRM

Proton Contacts extract as vCard format including name, email addresses (primary and aliases), phone numbers, physical addresses, and custom fields. They map to Odoo res.partner records. The primary email address becomes partner email; additional addresses populate email_normalized and are noted as aliases. We preserve the original Proton contact ID as an external ID field for reference. If the Odoo deployment uses the Contacts app separately from CRM, the same res.partner record is shared across both apps.

Proton Contacts that include organizational affiliation (company name, job title, department) are split: the company name creates or matches a res.partner with company_type = company, and the individual contact becomes a child res.partner with company_id pointing to the parent. This mirrors Odoo's partner hierarchy model. If Proton stores only individual contacts without company linkage, we load them as individual res.partner records and leave company_id blank for the admin to link manually or via Odoo's contact deduplication.

Proton Calendar events export via the Proton Calendar API with title, description, location, start/end datetime, reminders, attendees, and recurrence rules. They map to Odoo calendar.event. Attendees from Proton map to calendar.attendee records linked to the event and to corresponding res.partner records. Recurrence rules (RRULE) translate to Odoo's rrule format. We preserve the original event ID for timeline reconciliation.

Proton Mail messages are decrypted client-side before export. We map the message body to Odoo mail.message linked to the sender's res.partner (WhoId) and optionally to a related crm.lead or project.task if the customer has a linking convention. Attachments migrate as ir.attachment records linked via mail.message. The Proton folder hierarchy (INBOX, Sent, custom folders) is preserved as a tag field on mail.message rather than as Odoo folder structure, since Odoo does not replicate a hierarchical email folder model natively.

Proton Mail folders (hierarchical) and labels (tag-style with color coding) do not have a direct Odoo equivalent. We export the full taxonomy and deliver a mapping table that the customer's admin uses to create mail.tag records in Odoo. Proton labels that represent CRM-relevant categories (e.g., Customer, Prospect, High Priority) map to Odoo tags on crm.lead if applicable. Folder structure is noted as a read-only reference rather than a functional Odoo feature.

Proton Mail supports up to 10 hide-my-email aliases on Mail Plus plans. We extract these as separate address objects. Odoo CRM uses mail.alias on res.partner for incoming email-to-record routing. We deliver a configuration table mapping each Proton alias to a recommended Odoo mail.alias pattern, noting that Odoo's alias routing requires the incoming email server to be configured and that Proton aliases tied to a specific inbox may need forwarding rules set up at the DNS or mail relay level.

Proton Drive files extract with end-to-end decryption client-side, preserving binary content and folder structure. They map to Odoo ir.attachment records. Folder structure maps to Odoo's document.model filesystem hierarchy if the Odoo deployment includes the Documents app; otherwise, files attach to the related res.partner or crm.lead record. Version history (up to 365 days on Workspace Standard and Premium) is included when within scope and migratable. Shared Proton Drive links become invalid at the destination and are documented in the handoff checklist.

Proton Workspace Standard supports up to 15 custom email domains; Workspace Premium supports up to 20. We extract the domain configuration and DNS records (MX, SPF, DKIM, DMARC) as a separate workstream. The customer updates DNS at their registrar to point to Odoo's mail server. Domain verification in Odoo requires TXT record confirmation. We deliver a domain cutover checklist and recommend running both Proton and Odoo email in parallel during the DNS propagation window to avoid message loss.

Proton organization members map to Odoo res.users. We extract user accounts, roles, and team membership and match by email address against the destination Odoo instance. Any Proton team without a matching Odoo user goes to a reconciliation queue for the admin to provision before the contact import phase. Proton's role-based access model (Admin, Member) maps partially to Odoo's internal and portal user types.

The deprecated Proton Mail Professional plan (no new sign-ups) supported multiple addresses per account. Existing Mail Professional subscribers migrate with their address inventory intact. We inventory every Proton address within scope and map each to a corresponding Odoo user or shared inbox alias. Any address that cannot map directly is flagged for the admin to resolve at the DNS level.

Proton Pass stores credentials in an end-to-end encrypted vault. We extract vault entries in a structured format and deliver them as a password inventory document. Odoo CRM does not have a native credential vault. The customer uses this document to provision credentials in their preferred password manager (1Password, Bitwarden, or similar). Proton's E2E encryption means the vault cannot be decrypted by any third party including FlitStack AI without the customer's key.

Proton does not have a CRM data model — there are no leads, deals, opportunity stages, or sales pipelines in the source platform. Odoo CRM's crm.lead object is the primary record type for the destination but has no source counterpart. We flag this clearly in the migration scope: crm.lead records are created as placeholder entries for the customer's admin to populate post-migration, or are seeded from a prospect list that the customer provides separately. We do not fabricate pipeline data that did not exist in Proton.