CRM migration
Field-level mapping, validation, and rollback between Proton and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Proton
Source
Nutshell
Destination
Compatibility
7 of 8
objects map 1:1 between Proton and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Proton is an end-to-end encrypted email and productivity suite; Nutshell is a CRM designed for small and mid-market sales teams. These are fundamentally different platforms, so the migration scope centers on extracting your contact records, calendar events, and email activity history from Proton and mapping them into Nutshell's People, Accounts, Companies, and Activities objects. Proton Contacts (with name, email, phone, address, and custom fields) map to Nutshell People with optional Company linkage. Calendar events map to Nutshell Activities of type Meeting or Task. Email history from Proton Mail migrates as Activity records linked to the corresponding Nutshell People record. Proton Drive files and Proton Pass credentials do not have direct CRM equivalents; we extract Drive files as downloadable packages and flag Pass entries for migration to a dedicated password manager. We do not migrate Proton Workflows or automations because Proton is not a CRM and does not use the same automation model as Nutshell. We deliver a written inventory of Proton aliases, custom domains, and label taxonomy as a checklist for your admin to configure in Nutshell.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Proton object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Proton
Contact
Nutshell
People
1:1Proton Contacts (name, email, phone, physical address, and any custom fields) map to Nutshell People records. The primary email address from Proton becomes People.Email, phone numbers map to People.Phones, and physical address maps to People.Address. Custom fields from Proton Contacts migrate to custom People fields in Nutshell. If the Proton Contact's organization name is populated, we create a corresponding Nutshell Account and link the People record via AccountId lookup.
Proton
Contact organization
Nutshell
Account
1:1When Proton Contacts include an organization name, we extract the company as a Nutshell Account. The Account captures company name, domain, and any available firmographic data. If no organization is specified on the Contact, the Account is skipped and the People record stands alone. The Account is created before People import to satisfy the lookup relationship.
Proton
Calendar Event
Nutshell
Activity (Meeting or Task)
1:1Proton Calendar events map to Nutshell Activities. Events with attendees map to Activities of type Meeting linked to the relevant Nutshell People records via ActivityRelateds. Events without attendees map to Activities of type Task. Start time, end time, location, description, recurrence rules, and reminders preserve. Recurrence series from Proton Calendar are flattened into individual Activity records in Nutshell because Nutshell Activities do not support native recurrence patterns.
Proton
Email message (business email history)
Nutshell
Activity (Email)
1:1If Proton Mail is used for business correspondence, email history (subject, body, sender, recipient, timestamp) migrates as Nutshell Activities of type Email linked to the corresponding People record via ActivityRelateds. Email attachments from Proton Mail are downloaded as files and reattached to the Nutshell Activity record. Nutshell does not host email; the Activity captures the communication context and content.
Proton
Label and Folder taxonomy
Nutshell
Tag
lossyProton Mail labels (tag-style with color coding) and folder hierarchy (up to three levels) are extracted as a flat Tag taxonomy in Nutshell. Nutshell Tags apply to People, Accounts, and Deals. We map the label and folder names to Tags and apply the most relevant Tag to each migrated record. Tags do not carry color metadata from Proton because Nutshell Tags do not support color assignment.
Proton
Email alias and hide-my-email
Nutshell
Alias or forwarding rule
1:1Proton aliases and hide-my-email addresses are extracted as a list. Nutshell does not have a native email alias feature. We deliver a written inventory of every Proton alias with its associated People record and recommended action: configure forwarding in Nutshell's email settings, update DNS MX records to route alias traffic, or document the alias for re-creation in the customer's DNS provider and Nutshell settings.
Proton
Custom email domain
Nutshell
Domain configuration checklist
1:1Proton custom domains (up to 15 on Workspace Standard, 20 on Premium) are extracted and mapped to a domain handover checklist. The checklist specifies the current MX, SPF, DKIM, and DMARC records. After migration, the customer updates these records at their DNS registrar to route email to Nutshell. We recommend running both Proton and Nutshell in parallel during DNS cutover to avoid email loss.
Proton
User and organization member
Nutshell
User
1:1Proton workspace users map to Nutshell Users by email match. Team membership and role information from Proton (if available) is preserved in a custom Nutshell field for reference. Nutshell User provisioning is coordinated with the customer's admin because Nutshell requires manual user creation and role assignment within the platform's admin settings.
| Proton | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | People1:1 | Fully supported | |
| Contact organization | Account1:1 | Fully supported | |
| Calendar Event | Activity (Meeting or Task)1:1 | Fully supported | |
| Email message (business email history) | Activity (Email)1:1 | Fully supported | |
| Label and Folder taxonomy | Taglossy | Fully supported | |
| Email alias and hide-my-email | Alias or forwarding rule1:1 | Fully supported | |
| Custom email domain | Domain configuration checklist1:1 | Fully supported | |
| User and organization member | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Proton gotchas
Storage quota enforcement blocks all write operations at limit
End-to-end encryption keys must be available at extraction time
Mail Professional plan deprecated — no new sign-ups, migration requires plan upgrade
Large mailbox migration via Easy Switch is slow and non-streaming
Custom domain DNS migration requires manual re-verification
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and source data audit
We audit the Proton account scope including contact count, calendar event volume, email message count, Drive storage footprint, custom fields on Contacts, label and folder taxonomy, custom domains, and alias inventory. We identify any deal data stored in Proton Notes or Drive files and flag it for re-creation planning in Nutshell. We also confirm Proton plan tier, storage usage against quota, and account recovery status for E2E key availability. The discovery output is a written migration scope with record counts, a mapping specification, and a storage pre-validation report.
Nutshell account provisioning and schema design
We coordinate with the customer's Nutshell admin to set up the destination account including user provisioning, role assignments, and any custom fields on People, Accounts, and Activities that match Proton custom field names and types. We configure Nutshell Tags to receive the Proton label taxonomy. If custom domains are in scope, we plan the DNS cutover sequence and MX record update timeline. The Nutshell account is validated for API access before migration begins.
Contact and Account extraction and mapping
We extract all Proton Contacts as a structured dataset including name, email addresses, phone numbers, physical address, organization name, and any custom fields. Organization names are extracted as a separate Account dataset. We resolve any missing Account linkages and deduplicate contacts by email address. The extracted data is validated against Proton's Contact export for completeness before loading into Nutshell.
Calendar and email history migration
Proton Calendar events are extracted with full event details and attendee email addresses. We resolve attendee emails to Nutshell People records to establish ActivityRelateds linkage. Events with no attendees map to Tasks. Recurrence rules are flattened into individual Activity records. Email history from Proton Mail is extracted as Activity records of type Email linked to People. Attachments are downloaded and re-attached to the Nutshell Activity record. Each Activity receives the original Proton timestamp for timeline ordering.
Drive file extraction and alias-domain handoff
Proton Drive files are extracted as encrypted packages and re-attached to the relevant Nutshell records (People, Account, or Deal) based on manifest mapping. Drive version history is not migrated; the current file version is extracted. We deliver a written inventory of Proton aliases, hide-my-email addresses, and custom domains with recommended configuration steps for Nutshell's admin settings and the customer's DNS registrar. DNS cutover is coordinated as a separate workstream with a parallel-running window to avoid email loss.
Cutover, validation, and admin handoff
We perform a final delta migration of any Proton records modified during the migration window, validate record counts in Nutshell against the Proton source, and spot-check 25-50 random People and Activity records against the source. We deliver the alias and domain configuration checklist, the Drive file manifest, and a note on any Proton-based deal data that requires manual re-creation in Nutshell. We do not configure Nutshell automations, email sequences, or sales workflows as part of the standard migration scope; these are documented separately for the customer's admin team.
Platform deep dives
Proton
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Proton and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Proton: Not publicly documented in official documentation.
Data volume sensitivity
Proton doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Proton to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Proton to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Proton
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
