Migrate from Proton to Microsoft Dynamics 365 Sales

Proton Contacts with a company or organization name map to a Dynamics 365 Account first, then a Contact linked to that Account. Proton Contacts without an organization name map directly to a standalone Contact. The Proton contact's email address becomes the Contact Email field and is used as the dedupe key. Phone, physical address, and custom fields map to equivalent Dynamics 365 typed fields. Proton's contact birthday and anniversary fields map to custom Date fields in Dynamics 365.

Proton Calendar events map to Salesforce-style Task records for to-dos and Event records for meetings. All-day events become Task records; events with start and end times become Event records. Title, description, location, recurrence rules, reminders, and attendees migrate. Attendees resolve to Dynamics 365 Contact or User records via email match where possible. Proton recurrence series expand into individual Event records at migration time.

Proton email history migrates as Salesforce EmailMessage records (the content) linked to an Activity Task record (the timeline entry) attached to the corresponding Dynamics 365 Contact or Account. This requires first resolving the recipient and sender email addresses to Dynamics 365 Contact IDs at migration time. Proton attachments migrate as ContentDocument records linked to the EmailMessage. Proton's E2E encryption means decryption keys must be available during extraction; Proton Mail Bridge access is required.

Proton Mail's label taxonomy (tag-style with color coding) and folder hierarchy (hierarchical) do not have direct Dynamics 365 equivalents. We map labels to Salesforce Topics with TopicAssignment records and folders to Tags, preserving the hierarchy as a dot-notation naming convention. The customer chooses the preferred approach during scoping. Email routing rules built around Proton folders are flagged for rebuild as Dynamics 365 inbox rules or Power Automate flows.

Proton workspace users (paid plan members) map to Dynamics 365 Users. Each Proton user's encrypted email address becomes the Dynamics 365 User's Email field, and their display name maps to the Full Name. We reconcile Proton team membership against the customer's intended Dynamics 365 security roles during scoping. A Proton user without a corresponding Microsoft 365 Entra ID account requires provisioning before migration.

Proton alias addresses and hide-my-email aliases do not have a direct Dynamics 365 object equivalent. We extract all alias addresses and document them in a routing-rules inventory. The customer's admin rebuilds alias forwarding as Microsoft 365 mail flow rules or Dynamics 365 inbox rules post-migration. This is noted as an out-of-scope task requiring admin action.

Proton Drive files (E2E encrypted binary storage) have no native Microsoft Dynamics 365 Sales equivalent because Microsoft Dynamics 365 Sales does not include a file store. We extract file metadata (name, path, size, modification date, version count) and generate a SharePoint migration guide with folder structure mapping. Files requiring preservation migrate manually to SharePoint via the customer's Microsoft 365 SharePoint admin. Proton shared links become invalid at the destination and are documented for replacement.

Proton custom domains (up to 15 on Workspace Standard, 20 on Premium) migrate as DNS configuration records documented for Microsoft 365 admin center re-verification. MX, SPF, DKIM, and DMARC records must be updated at the DNS registrar after Proton's infrastructure is decommissioned. We produce a domain cutover checklist with both Proton and Microsoft 365 DNS record values. Parallel-operation routing during DNS propagation is recommended.