CRM migration

Migrate from Exsalerate to Nutshell

Field-level mapping, validation, and rollback between Exsalerate and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Exsalerate logo

Exsalerate

Source

Nutshell

Destination

Nutshell logo

Compatibility

88%

7 of 8

objects map 1:1 between Exsalerate and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Exsalerate logo

Exsalerate

What's pushing teams away

  • Reporting depth does not match enterprise CRMs — Exsalerate's built-in analytics are limited compared to platforms like Salesforce or HubSpot, and customers requiring multi-touch attribution, forecasting models, or custom dashboards eventually outgrow what the platform surfaces.
  • Scalability concerns for teams above 20–30 users — several reviewers note that the platform was adequate at small scale but became slower and harder to manage as headcount and record volume grew, particularly on the pipeline view with large deal counts.
  • Limited third-party integrations beyond Xero and WorkflowMax — firms that need to connect to marketing automation, telephony, ERP, or other tools report significant friction, and the integration ecosystem is described as underdeveloped relative to major CRM platforms.
  • Support responsiveness varies — a subset of reviews mention slower response times from the Exsalerate support team, particularly when handling edge cases or technical questions about the WorkflowMax sync.
  • No native mobile app with full feature parity — field sales teams note that the mobile experience lacks the desktop pipeline view and some activity logging features, reducing utility for users who are frequently off-site.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Exsalerate objects map to Nutshell

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

maps to

Nutshell

Account

1:1
Fully supported

Exsalerate 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

maps to

Nutshell

Contact

1:1
Fully supported

Exsalerate 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

maps to

Nutshell

Opportunity

1:1
Fully supported

Exsalerate 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

maps to

Nutshell

Pipeline

1:1
Fully supported

Exsalerate 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

maps to

Nutshell

Stage

lossy
Fully supported

Exsalerate 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

maps to

Nutshell

Task

1:1
Fully supported

Exsalerate 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

maps to

Nutshell

Activity (Task)

1:1
Fully supported

Exsalerate 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

maps to

Nutshell

Custom Field or Note

1:1
Fully supported

Exsalerate 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.

Gotchas + challenges

What specifically takes care here

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 logo

Exsalerate gotchas

Medium

WorkflowMax quote-to-opportunity linkage is not a standard CRM field

High

Exsalerate has no publicly documented bulk export or API endpoint

Low

Colour-coded to-do tiles do not map to standard CRM task priorities

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Exsalerate has no documented public bulk API

    Unlike most major CRM platforms, Exsalerate does not publish a public REST API or bulk export endpoint in its documentation. Our migration path for Exsalerate sources relies on its built-in CSV export capability. We confirm the export method during discovery and plan for multi-file reconciliation if the export does not include all required objects in a single download. If no export mechanism is accessible, we flag this as a migration blocker before scoping begins. This constraint directly affects timeline because CSV reconciliation adds manual review steps that API-driven migrations do not require.

  • Nutshell does not have native Xero or WorkflowMax integration

    Exsalerate's primary value for ANZ professional services firms is its native Xero and WorkflowMax bi-directional sync. Nutshell has no native connector for either tool. Teams migrating from Exsalerate to Nutshell lose the Xero and WorkflowMax integration as a built-in feature and must evaluate third-party alternatives (Zapier, Make, or a custom API integration) or rebuild the accounting and project management connection outside of Nutshell. This is a workflow-level gotcha — it does not block data migration but does require the customer to plan an alternative integration strategy post-migration.

  • Colour-coded stage metadata has no native Nutshell equivalent

    Exsalerate uses colour-coded stage tiles to signal urgency and context in the pipeline board. Nutshell's stage columns use a single colour per pipeline that applies to the entire pipeline, not per-stage. We store the Exsalerate colour value in a custom field on the Pipeline or Stage object where the Nutshell plan allows, but this is cosmetic metadata that does not drive any Nutshell workflow. If the customer relies on stage colours to prioritise daily activity, they need to establish an alternative visual tagging method in Nutshell post-migration.

Migration approach

Six steps for a successful Exsalerate to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Exsalerate logo

Exsalerate

Source

Strengths

  • Built-in WorkflowMax and Xero integration for service-industry workflows
  • Drag-and-drop pipeline board with colour-coded stage tiles
  • Account-centric model with explicit retention focus
  • Simple setup with minimal consultant involvement required for basic deployments
  • Purpose-built for ANZ small-to-mid professional services firms

Weaknesses

  • Limited reporting and analytics compared to enterprise CRM platforms
  • Shallow third-party integration ecosystem beyond accounting tools
  • Performance degrades at scale with large record volumes
  • No mobile app with full feature parity for field sales users
  • Support responsiveness inconsistent for complex technical scenarios
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Exsalerate and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Exsalerate: Not publicly documented..

  • Data volume sensitivity

    B

    Exsalerate doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Exsalerate to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Exsalerate to Nutshell data migrations

Answers to the questions buyers ask most during Exsalerate to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Exsalerate to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between two and three weeks for accounts with up to 5,000 Contacts and 2,000 Opportunities and a clean CSV export from Exsalerate. Migrations with large email history sets, complex custom field picklist mappings, or a multi-file CSV reconciliation requirement move to three to five weeks. The primary variable is the export method from Exsalerate — if CSV export is available in a single consolidated file, timeline stays short; if multi-file reconciliation is required, the timeline extends.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Exsalerate.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day