Migrate from Proton to HighLevel

Proton Contacts with name, email addresses, phone numbers, physical addresses, and custom fields map directly to GoHighLevel Contacts. We export in vCard format and transform each vCard into a GoHighLevel contact record via the Contacts API, preserving the primary email as the contact Email field and any additional email addresses as custom fields. Tags and label associations from Proton migrate as GoHighLevel Tags on the contact record. Any Proton contact with a missing or invalid email address is held in a reconciliation queue for the customer to resolve before import completes.

Proton Calendar events include title, description, location, start and end time, reminders, attendees, and recurrence rules. GoHighLevel has no native calendar object, so we map events to GoHighLevel Tasks with the event title as Task name, description as notes, start time as due date, and location preserved. For business-specific event types (appointments, classes, consultations), we create a Custom Object with event fields matching the Proton schema so that historical appointment data is queryable alongside Contact records. Attendee lists from Proton events are stored as custom text fields since GoHighLevel Tasks do not have native attendee objects.

Each Proton user account email address becomes the primary email field on a corresponding GoHighLevel Contact record. For Proton accounts with multiple encrypted email addresses or hide-my-email aliases, we map the primary address to the contact email and store aliases as a custom multi-select field so that the full communication history is preserved at the contact level. Aliases used for transactional versus marketing communication do not migrate as GoHighLevel campaign-send addresses; the customer configures sending domains separately in GoHighLevel.

Proton Mail uses both hierarchical Folders and tag-style Labels with color coding. We extract the full label taxonomy and folder hierarchy and map them to GoHighLevel Tags on the associated Contact record. Folder hierarchy does not map directly since GoHighLevel Tags are flat; we preserve the full folder path as the tag name (e.g., 'Clients/Active/Q1-2025') to retain the organizational context. Color coding from Proton labels does not migrate because GoHighLevel Tags do not have a native color attribute.

Proton Workspace supports up to 15 custom domains on Standard and 20 on Premium. Migrating domains to GoHighLevel requires adding the domain in GoHighLevel Settings and completing TXT and MX record verification at the DNS registrar before the domain can send from GoHighLevel. We map DNS configuration as a separate workstream and recommend running both Proton and GoHighLevel in parallel with routing rules during the DNS cutover window to avoid email loss. SPF, DKIM, and DMARC records must be updated at the registrar after GoHighLevel verification completes.

Proton Drive files encrypted with E2E keys do not map to any GoHighLevel object. GoHighLevel has no native file storage for document attachments; appointments and emails with attachments can reference external URLs but cannot host files. We extract a file manifest (file names, sizes, folder paths, and modification dates) as a CSV delivered to the customer for manual re-upload to Google Drive, Dropbox, or a GoHighLevel-integrated document storage tool. Shared links from Proton Drive become invalid at the destination and are documented for the customer to re-create.

Proton VPN configuration profiles are platform-specific and tied to Proton's server infrastructure. GoHighLevel has no VPN functionality. VPN tunnel configurations cannot be meaningfully mapped to any GoHighLevel feature. We exclude VPN from migration scope and document this clearly in the scope agreement so the customer understands that VPN setup must be configured independently post-migration.

Proton Pass stores credentials in an encrypted vault with client-side keys. We do not migrate Proton Pass entries because they are encrypted with keys that never leave the user's control and cannot be extracted in plaintext by any platform including Proton itself. If the customer needs to migrate credentials, Proton recommends using a Proton Pass export in unencrypted mode before account closure. We document this requirement and recommend the customer perform the Pass export separately before the migration window.