CRM migration

Migrate from Zurple to Nutshell

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

Zurple logo

Zurple

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

14 of 14

objects map 1:1 between Zurple and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Zurple logo

Zurple

What's pushing teams away

  • Lead quality is inconsistent — agents sourced through Zurple's paid traffic describe conversion rates as low, with leads described as cheap but unresponsive.
  • No documented public API means customers cannot self-serve data export, creating dependency on the vendor for any migration or backup.
  • A negative review alleges that after account termination, Zurple sent unsolicited messages to the departing agent's existing client contacts, raising concerns about data ownership.
  • Pricing is opaque — there is no publicly listed price on the website, requiring a sales call, which frustrates agents who want to compare cost before committing.

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 Zurple objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Zurple 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

maps to

Nutshell

Company

1:1
Fully supported

Zurple 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

maps to

Nutshell

Deal

1:1
Fully supported

Zurple 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

maps to

Nutshell

Pipeline

1:1
Fully supported

Zurple 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)

maps to

Nutshell

Task

1:1
Fully supported

Zurple 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)

maps to

Nutshell

Task

1:1
Fully supported

Zurple 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)

maps to

Nutshell

Note

1:1
Fully supported

Zurple 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)

maps to

Nutshell

Custom Field (Person)

1:1
Fully supported

Zurple 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)

maps to

Nutshell

Custom Field (Company)

1:1
Fully supported

Zurple 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)

maps to

Nutshell

Custom Field (Deal)

1:1
Fully supported

Zurple 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

maps to

Nutshell

Campaign

1:1
Fully supported

Zurple 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

maps to

Nutshell

Email Sequence (Nutshell Pro)

1:1
Fully supported

Zurple'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

maps to

Nutshell

Custom Field (Person)

1:1
Fully supported

Zurple 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

maps to

Nutshell

User

1:1
Fully supported

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

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.

Zurple logo

Zurple gotchas

High

No public API for bulk data export

Medium

Automated nurture sequences do not transfer

Medium

Data ownership after termination is ambiguous

Low

Lead quality from paid advertising is inconsistent

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

  • Zurple nurture sequences and IDX website behavior tracking have no Nutshell equivalent

    Zurple's core value-add is automated lead nurturing tied to real estate behavior — IDX website visits, saved property searches, and drip emails triggered by lead activity. Nutshell has no native IDX integration and its Personal Email Sequences are triggered by pipeline stage changes, not website behavior. These automations cannot migrate and must be rebuilt. We export Zurple sequence names, trigger logic, and email content as a rebuild reference document so your team can reconstruct the logic in Nutshell Pro or a dedicated real estate marketing tool. This is the largest functional gap in the migration and should be scoped before you commit to the switch.

  • Nutshell API rate limits on find operations require paginated extraction

    Nutshell's API documentation explicitly states that find operations — specifically findLeads() and equivalent search methods with non-stub responses — are rate-limited. The degree of rate limiting may vary based on current conditions. For Zurple migrations with large record sets, we paginate extraction requests and add retry logic for 429 responses. We validate that the extracted record count matches the imported total before closing the migration window. This is a migration-engineering constraint, not a data-loss risk, but it extends the extraction clock time for databases over 50,000 records.

  • Duplicate contact detection across lead sources requires pre-migration merge decision

    Zurple agents often create multiple contact records for the same person when leads come from different sources (IDX website, Facebook ads, referrals). Nutshell has built-in de-duplication on email, but if the same person appears with different email addresses across Zurple records, they will land as separate Nutshell People. We run a pre-migration duplicate analysis and surface potential matches by name, phone, and address similarity so you can decide whether to merge before or after migration. Unmerged duplicates post-migration require manual Nutshell merge operations.

  • Real estate lead source attribution becomes a reference field, not a tracking dimension

    Zurple captures lead source (which AdWords campaign, IDX search, or referral generated the contact) as a contact property. Nutshell's Campaign object is designed for marketing email attribution, not paid ad lead source tracking. We migrate the Zurple lead source value as a custom field on the Person record. You can use it for filtering and reporting in Nutshell, but you lose the native campaign attribution model that would track which ads generated the lead over time. Rebuilding this requires connecting Nutshell to your ad platform via a third-party integration or a separate real estate CRM tool.

Migration approach

Six steps for a successful Zurple to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Zurple logo

Zurple

Source

Strengths

  • Bundled IDX website with MLS integration removes the need for a separate real estate website vendor.
  • Behavior-driven automated nurture (Conversations™) handles lead follow-up without manual agent input.
  • Exclusive lead delivery model means leads in a target market are not shared with other Zurple agents in that same area.
  • Single dashboard combining lead generation, CRM pipeline, and automated nurture reduces tool fragmentation for solo agents.
  • Measurable revenue attribution — agents can track closings back to Zurple-sourced clients.

Weaknesses

  • No publicly documented API or bulk export mechanism, making data portability dependent on vendor cooperation.
  • Lead quality from paid advertising channels is inconsistent; some agents report poor conversion rates.
  • Pricing is opaque with no public tier listing, requiring a sales call for any cost evaluation.
  • Post-termination data handling is unclear; one negative review alleges unsolicited contact harvesting after account cancellation.
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. 1 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 Zurple and Nutshell.

  • Object compatibility

    B

    1 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

    Zurple: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Zurple 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 Zurple to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Zurple-to-Nutshell migrations complete in 48–72 hours for databases under 50,000 records. The fastest steps are standard field transfers (names, emails, addresses) that map directly. The longest planning step is creating Nutshell custom fields for Zurple properties with no native equivalent — this must be done before data lands. Larger databases with 500k+ records or many custom properties extend to 5–7 days, especially if the Nutshell API rate limits on find operations require paginated retries during extraction.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Zurple.
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