CRM migration
Field-level mapping, validation, and rollback between Exsalerate and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Exsalerate
Source
Nutshell
Destination
Compatibility
7 of 8
objects map 1:1 between Exsalerate and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Exsalerate to Nutshell is primarily a schema redesign. Exsalerate uses Accounts as the central entity with a flat Opportunities-tied-to-stages model, while Nutshell uses the standard Account-Contact-Opportunity triangle with a separate Pipeline object. We map Exsalerate's colour-coded stage labels to Nutshell stage names, preserving the colour value in a custom field where available. Email history migrates as Activity records against the correct Account and Contact. The WorkflowMax quote-to-opportunity linkage is not a standard CRM field in either system — we document the cross-reference in a custom property or note for the customer's admin to rebuild in Nutshell. Exsalerate has no documented public bulk API, so migration relies on CSV export from Exsalerate paired with Nutshell's REST API for import. Workflows, automations, Xero sync rules, and WorkflowMax integrations do not migrate; we deliver a written inventory of these for the customer to rebuild manually in Nutshell or through a third-party integration tool.
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 Exsalerate 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.
Exsalerate
Account
Nutshell
Account
1:1Exsalerate Accounts map directly to Nutshell Accounts using Account Name as the dedupe key. The Account-Contact relationship is preserved at migration time. Exsalerate's flat model makes Accounts the primary entity — Nutshell uses the same structure, so no schema redesign is required at the Account level. Custom fields on Accounts migrate with type-aware field mapping (picklist values, date formats, numeric precision normalised at import).
Exsalerate
Contact
Nutshell
Contact
1:1Exsalerate Contacts map directly to Nutshell Contacts with the Account-Contact lookup preserved. We run duplicate detection on email address before import to flag potential overlaps. Nutshell Contacts inherit the Account relationship so that the Account-Contact-Opportunity triangle is intact in the destination. Owner resolution by email match against Nutshell users is applied before insert.
Exsalerate
Opportunity
Nutshell
Opportunity
1:1Exsalerate Opportunities map to Nutshell Opportunities with the Account link preserved and the Exsalerate pipeline stage mapped to the Nutshell stage name. Opportunity value, expected close date, and owner migrate as-is. Closed-won and closed-lost reasons from Exsalerate custom properties migrate to Nutshell custom fields if configured, or are flagged as fields requiring manual entry post-migration.
Exsalerate
Pipeline
Nutshell
Pipeline
1:1Exsalerate Pipelines map to Nutshell Pipelines using Pipeline Name as the identifier. Nutshell Pipelines contain ordered Stages and are the top-level container for Opportunity view. We preserve the Exsalerate pipeline sequence so that the Nutshell Kanban board reflects the original sales process order.
Exsalerate
Pipeline Stage
Nutshell
Stage
lossyExsalerate stage labels and their ordering map directly to Nutshell Stage values within the corresponding Pipeline. The colour-coding metadata attached to stages in Exsalerate has no native equivalent in Nutshell — we store the hex colour value in a custom text field on the Pipeline or in a custom field on the Stage if the Nutshell plan supports it, and we flag the limitation during scoping.
Exsalerate
To-Do Item
Nutshell
Task
1:1Exsalerate colour-coded activity tiles map to Nutshell Tasks with Status, Priority, and due date preserved. The tile colour value is stored in a custom field if the Nutshell plan exposes custom Task fields; otherwise it is appended to the Task description. Completed status and overdue flags are mapped to Nutshell Task Status values (Not Started, In Progress, Completed).
Exsalerate
Email Activity
Nutshell
Activity (Task)
1:1Exsalerate email history migrates to Nutshell Activities (stored as Tasks with a linked email reference). We preserve subject, body, timestamp, sender, and recipients. The email is linked to the target Account and Contact by email-address matching. Attachments require a separate file migration pass and are documented as an out-of-scope item for the customer's IT team to handle independently.
Exsalerate
WorkflowMax Cross-Reference
Nutshell
Custom Field or Note
1:1Exsalerate allows WorkflowMax quotes to be imported as Opportunities, creating a cross-reference that is stored as a custom attribute rather than a standard CRM field. This linkage has no direct equivalent in Nutshell. We store the WorkflowMax reference value in a custom text field on the Opportunity record if the Nutshell plan supports custom fields on Opportunities; otherwise we create a Note attached to the Opportunity with the cross-reference string. We flag the limitation and document the complete cross-reference list in a CSV delivered with the migration package.
| Exsalerate | Nutshell | Compatibility | |
|---|---|---|---|
| Account | Account1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Opportunity | Opportunity1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Pipeline Stage | Stagelossy | Fully supported | |
| To-Do Item | Task1:1 | Fully supported | |
| Email Activity | Activity (Task)1:1 | Fully supported | |
| WorkflowMax Cross-Reference | Custom Field or Note1: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.
Exsalerate gotchas
WorkflowMax quote-to-opportunity linkage is not a standard CRM field
Exsalerate has no publicly documented bulk export or API endpoint
Colour-coded to-do tiles do not map to standard CRM task priorities
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 export method confirmation
We audit the Exsalerate account to identify every object that needs to migrate: Accounts, Contacts, Opportunities, Pipelines, Pipeline Stages, To-Do Items, Email Activities, custom fields, and user accounts. We confirm the available export mechanism — CSV export via the Exsalerate UI or direct database access for specific deployments. If the CSV export does not cover all required objects, we plan for a multi-file reconciliation step. We also identify any WorkflowMax quote-to-opportunity cross-references that require explicit preservation.
Schema design in Nutshell
We design the Nutshell destination schema to accommodate Exsalerate's data model. This includes creating any custom fields required on Accounts, Contacts, and Opportunities (for WorkflowMax cross-references and Exsalerate custom properties), configuring Pipelines and Stages to match the Exsalerate pipeline sequence, and setting up Nutshell users matched to Exsalerate owners by email. We deploy into a Nutshell trial or sandbox environment first for mapping validation before any production data is touched.
Sandbox migration and reconciliation
We run a sandbox migration using production-like data volume extracted from Exsalerate. The customer reconciles record counts and spot-checks 20-30 records against the Exsalerate source. We verify that colour-coding metadata is stored correctly, that Opportunity-to-Account links are intact, and that the WorkflowMax cross-reference list is complete in the output. Any mapping corrections are applied before the production migration begins.
User provisioning in Nutshell
We extract every distinct Exsalerate owner referenced on Accounts, Contacts, Opportunities, and Tasks and match by email against the Nutshell destination user list. Any Exsalerate owner without a matching Nutshell user goes to a reconciliation queue for the customer's admin to provision. Owner resolution is required before record import can proceed because Nutshell Activity records require an assigned owner.
Production migration in dependency order
We run the production migration in the correct dependency sequence: Accounts first (stand-alone), Contacts second (with AccountId resolved), Opportunities third (with AccountId and OwnerId resolved), then Tasks and Activities last. Each phase emits a row-count reconciliation report before the next phase begins. Email history migrates against the resolved Account and Contact records. The WorkflowMax cross-reference list is written to the custom field or Note on each affected Opportunity as the final step of the Opportunities phase.
Cutover, validation, and integration handoff
We freeze Exsalerate writes during cutover and run a final delta migration of any records modified during the migration window. We deliver a written inventory of Exsalerate automations, Xero sync rules, and WorkflowMax connections that require manual rebuild in Nutshell or via a third-party integration. We provide a one-week hypercare window to resolve reconciliation issues raised by the customer's team. We do not rebuild automations or integrate Nutshell with Xero or WorkflowMax as part of the migration scope — those are separate engagements.
Platform deep dives
Exsalerate
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Exsalerate and Nutshell.
Object compatibility
2 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
Exsalerate: Not publicly documented..
Data volume sensitivity
Exsalerate 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 Exsalerate to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Exsalerate 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 Exsalerate
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.