CRM migration
Field-level mapping, validation, and rollback between Zurple and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Zurple
Source
Nutshell
Destination
Compatibility
14 of 14
objects map 1:1 between Zurple and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Zurple is a real estate client-generation platform that combines CRM contacts, companies, and deals with built-in lead generation, automated nurturing sequences, and IDX website integration. Nutshell is a general-purpose CRM that tracks People (contacts), Companies, Leads, and Deals across customizable pipelines using a JSON-RPC API with rate limits on find operations and impersonation options for API keys. The core migration challenge is that Zurple's real estate-specific features — automated lead nurture drips, IDX website visitor tracking, MLS-based lead scoring — have no Nutshell equivalent and must be rebuilt or preserved as reference data. We extract Zurple data via their API or CSV export, map Zurple contacts to Nutshell People, companies to Nutshell Companies, and deals to Nutshell Deals. Activities (calls, emails, tasks, notes) transfer to Nutshell Tasks and Notes with original timestamps and owner links intact. Custom fields on any Zurple object become Nutshell custom fields on the matching entity. Because Nutshell's API rate-limits find operations with non-stub responses, we paginate large result sets and validate that the migrated record count matches the extracted total before closing the migration window.
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 Zurple 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.
Zurple
Contact
Nutshell
Person
1:1Zurple contacts map 1:1 to Nutshell People. Every standard field (name, email, phone, address) transfers directly. Nutshell People can have custom fields added via the settings UI — any Zurple contact property without a native equivalent becomes a Nutshell custom field on the Person record.
Zurple
Company
Nutshell
Company
1:1Zurple companies map to Nutshell Companies. Basic fields (name, domain, address) transfer directly. Nutshell Companies support custom fields, so any Zurple company property without a native equivalent migrates as a custom field. Parent-child company relationships transfer via the parent_company_id field mapped to Nutshell's parent_company reference.
Zurple
Deal
Nutshell
Deal
1:1Zurple deals map to Nutshell Deals with direct field mapping for name, amount, and close date. The deal stage name in Zurple maps to a Nutshell stage value — if stage names differ, we apply a value-mapping table during migration. Each Nutshell Deal is linked to a Pipeline that you configure in Nutshell before migration.
Zurple
Pipeline
Nutshell
Pipeline
1:1Zurple pipelines map to Nutshell Pipelines. You configure the Nutshell pipeline structure (stages, probabilities) before migration begins. We deliver a pipeline setup plan specifying the stage names and order that correspond to your Zurple pipeline configuration so the deal migration lands in the correct stages.
Zurple
Activity (Call)
Nutshell
Task
1:1Zurple call logs are imported as Nutshell Tasks with the Task type field set to 'Call'. The original call timestamp, duration in seconds, and the owner assignment are retained. During migration, the Person or Deal identifier is resolved and the task is linked to the corresponding record via the Nutshell API, ensuring that call history is attached to the correct contact or deal.
Zurple
Activity (Email)
Nutshell
Task
1:1Zurple email activity is migrated as Nutshell Tasks with the Task type set to 'Email'. The original subject line, message body, and timestamp are copied over, preserving the sender and recipient information. Email threads are stored as linked task sequences attached to the associated Person record, allowing the full conversation history to be viewed in Nutshell.
Zurple
Activity (Note)
Nutshell
Note
1:1Zurple notes are transferred as Nutshell Notes and attached to the relevant Person, Company, or Deal record. The original creation timestamp and owner assignment are kept to maintain audit history. Any rich-text formatting present in Zurple is stripped and converted to plain text, ensuring compatibility with Nutshell's note format while preserving the core content.
Zurple
Custom Property (Contact)
Nutshell
Custom Field (Person)
1:1Zurple custom contact properties (beyond standard fields) require Nutshell custom fields to be created on the Person object before migration. We generate a custom-field creation plan with field names, data types, and pick-list values from Zurple so your Nutshell admin can pre-create them.
Zurple
Custom Property (Company)
Nutshell
Custom Field (Company)
1:1Zurple custom company properties are migrated as Nutshell Company custom fields. We generate a field-specification document that lists each custom field’s name, data type, and any pick-list values sourced from Zurple. This document allows your Nutshell administrator to pre-create the fields in the Nutshell settings UI before the migration loads, ensuring that all custom data lands without post-migration field edits.
Zurple
Custom Property (Deal)
Nutshell
Custom Field (Deal)
1:1Zurple deal-level custom properties are mapped to Nutshell Deal custom fields. Because Nutshell exposes custom fields through its settings UI, we include these fields in the pre-migration custom-field plan and validate that each field exists before the deal records are loaded. This verification step prevents write errors and ensures the custom data appears correctly on the Deal entity after migration.
Zurple
Lead Source / Campaign
Nutshell
Campaign
1:1Zurple tracks lead source and campaign attribution as contact or deal properties. Nutshell has a Campaign object for marketing attribution, but it operates differently. We preserve Zurple lead source data as custom fields on the Person record and surface it as a mapping recommendation for your Nutshell admin to configure campaign tracking post-migration.
Zurple
Nurture Sequence / Automated Email
Nutshell
Email Sequence (Nutshell Pro)
1:1Zurple's automated nurture sequences and behavior-driven email drips tied to IDX website activity have no direct Nutshell equivalent. These must be rebuilt using Nutshell's Personal Email Sequences feature (Pro plan) or a third-party email marketing tool. We export the sequence names, trigger conditions, and email content as a rebuild reference document.
Zurple
IDX Website / Property Search Data
Nutshell
Custom Field (Person)
1:1Zurple captures IDX website visitor behavior, saved searches, and property interest as contact-level data. Nutshell has no IDX or MLS integration, so this real estate-specific data migrates as custom fields on the Person record for reference — your team decides whether to act on it manually or build a real estate-specific tool to replace this function.
Zurple
Owner / Agent
Nutshell
User
1:1Zurple owners (agents) map to Nutshell Users by email address match. We resolve each Zurple owner_id to a Nutshell user email. Unresolved owners are flagged before migration so you can invite them to Nutshell or assign their records to a fallback user.
| Zurple | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Activity (Call) | Task1:1 | Fully supported | |
| Activity (Email) | Task1:1 | Fully supported | |
| Activity (Note) | Note1:1 | Fully supported | |
| Custom Property (Contact) | Custom Field (Person)1:1 | Fully supported | |
| Custom Property (Company) | Custom Field (Company)1:1 | Fully supported | |
| Custom Property (Deal) | Custom Field (Deal)1:1 | Fully supported | |
| Lead Source / Campaign | Campaign1:1 | Fully supported | |
| Nurture Sequence / Automated Email | Email Sequence (Nutshell Pro)1:1 | Fully supported | |
| IDX Website / Property Search Data | Custom Field (Person)1:1 | Fully supported | |
| Owner / Agent | 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.
Zurple gotchas
No public API for bulk data export
Automated nurture sequences do not transfer
Data ownership after termination is ambiguous
Lead quality from paid advertising is inconsistent
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 planning
We connect to your Zurple account via API credentials and run a discovery export of all records: People, Companies, Deals, Activities, Notes, and Custom Properties. We profile record counts, field types, and pick-list values for every custom property. We identify duplicate records, records with missing email addresses, and any circular parent-company references. We deliver a Discovery Report that includes the exported record counts by object type, a list of custom fields to create in Nutshell before migration, and a recommended Nutshell pipeline configuration based on your Zurple deal stages.
Create Nutshell custom fields and pipeline
Before any data loads, you create the custom fields in Nutshell that correspond to Zurple custom properties with no native equivalent. We provide a field-specification document listing each custom field name, data type, and pick-list options sourced directly from Zurple. You also configure the Nutshell Pipeline with stages that correspond to your Zurple deal stages — we include the stage name list and recommended order in the setup plan. This step ensures that when deal records land, they can write to correctly configured stages without requiring post-migration field edits.
Run sample migration with field-level diff
We migrate a representative slice — typically 100–300 records spanning People, Companies, Deals, and Activities — and generate a field-level diff between the Zurple source values and the Nutshell destination fields. You review the diff to verify that Zurple stage names mapped to the correct Nutshell pipeline stages, custom field values transferred correctly, owner resolution by email matched the right Nutshell users, and timestamps preserved the original create dates rather than migration-clock timestamps. We iterate on the mapping until you sign off on the sample before proceeding to full migration.
Full migration with delta-pickup window
The full migration runs in dependency order: Companies first, then People, then Deals with pipeline and stage assignment, then Activities and Notes linked to their parent records. We run a post-migration reconciliation comparing extracted count to imported count for each object type. A delta-pickup window (typically 24–48 hours after initial load) captures any records modified in Zurple during the cutover period. All operations are logged in an audit trail, and one-click rollback reverts the Nutshell org to its pre-migration state if reconciliation fails.
Rebuild reference export
Alongside the data migration, we export your Zurple nurture sequence definitions (names, trigger conditions, email subject and body), IDX website visitor behavior records, and lead source attribution data as rebuild reference documents. These are structured as implementation briefs your team or a Nutshell specialist can use to configure Nutshell Pro email sequences, set up campaign tracking, and document which real estate lead gen tools you plan to use instead of Zurple's built-in features.
Platform deep dives
Zurple
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 Zurple 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
Zurple: Not publicly documented.
Data volume sensitivity
Zurple 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 Zurple to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Zurple 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 Zurple
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.