CRM migration

Migrate from Rezora to Nutshell

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

Rezora logo

Rezora

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Rezora and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Rezora is a real-estate-specific digital marketing and CRM platform built around multi-agent campaign distribution, drip campaign sequences, and contact-level engagement tracking tied to property listings. Its data model centers on Contacts linked to Distribution Groups and Campaigns, with engagement metrics (opens, clicks, property views) stored per contact per campaign. Rezora's deprecated REST API and its proprietary contact-group hierarchy present the primary migration challenge — there is no native export format that preserves campaign attribution without post-processing. Nutshell is an SMB-focused CRM that tracks People (contacts), Companies (accounts), Leads, Deals (pipeline stages), Tasks, and Notes. It uses a JSON-RPC API with HTTPS authentication and rate limits on find operations. Nutshell does not have native equivalents for Rezora's drip campaign sequences, marketing campaign attribution models, or agent-group distribution hierarchies — these must be archived as reference data and rebuilt in Nutshell's automation tools or external tooling. FlitStack AI extracts Rezora contact records via their REST API using CSV/JSON export, resolves Rezora owner IDs by email match against Nutshell user accounts, maps Rezora contact properties to Nutshell People fields (creating custom fields for Rezora-specific attributes), maps Rezora company records to Nutshell Companies, and migrates activity history (notes, tasks) with original timestamps. Engagement metrics from Rezora campaigns are preserved as custom fields or JSON blobs for historical reference. A delta-pickup window captures any records modified during cutover before the final handoff.

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

Rezora logo

Rezora

What's pushing teams away

  • Interface is described as clunky and dated — creating sleek templates is harder than modern drag-and-drop builders.
  • Browser compatibility issues cause sporadic rendering problems that frustrate agents who switch between Chrome, Firefox, and Safari.
  • Scalability concerns emerge at high agent counts, with the platform feeling designed for boutique brokerages rather than large franchises.
  • Limited CRM depth means brokerages that grow past basic contact management and email marketing outgrow the feature set.

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

Each row shows how a Rezora 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.

Rezora

Contact

maps to

Nutshell

Person

1:1
Fully supported

Rezora contacts map directly to Nutshell People. The contact's primary company resolves to a Nutshell Company record by domain or explicit company field match. Contacts without a resolved company land as standalone People records. Original Rezora contact create timestamps are preserved as a custom datetime field in Nutshell since Nutshell's CreatedDate is set at import time.

Rezora

Company / Brokerage

maps to

Nutshell

Company

1:1
Fully supported

Rezora brokerage and company records map to Nutshell Companies. Parent-child company hierarchies in Rezora (brokerage with office locations) map to Nutshell's Company hierarchy where supported, or are flattened to sibling Company records with a custom Parent_Company__c field for manual re-linkage in Nutshell after migration.

Rezora

Distribution Group

maps to

Nutshell

Custom List / Custom Field

1:1
Fully supported

Rezora distribution groups are N:N contact groupings used for agent-level and team-level campaign targeting. Nutshell has no native equivalent grouping object. We export the group memberships as a JSON custom field (Distribution_Groups__c) on each Nutshell Person record, preserving the full group list per contact. For active segmentation needs, Nutshell's Saved Filters serve as the operational replacement.

Rezora

Campaign

maps to

Nutshell

Saved Filter / Campaign Reference

1:1
Fully supported

Rezora campaigns store the email template, send schedule, property linkage, and engagement metrics per campaign. Nutshell has no campaign object at the CRM level — its email sequences are triggered by pipeline stage entry (Pro+). We preserve Rezora campaign names, send dates, and aggregate open/click rates as a Campaign_Archive__c custom field on the People records that received the campaign. Rebuild reference exported as a CSV.

Rezora

Drip Campaign Sequence

maps to

Nutshell

Personal Email Sequence (Nutshell Pro)

1:1
Fully supported

Rezora drip campaigns are multi-step email sequences with timing rules tied to contact actions or calendar triggers. Nutshell Pro offers personal email sequences triggered by pipeline stage entry. The structural mapping is not 1:1 — Rezora's event-based drip logic (contact viewed property, contact clicked link) does not map to Nutshell's stage-entry triggers. We export drip campaign definitions as a structured rebuild reference document for your team to reconstruct in Nutshell Pro.

Rezora

Agent / User

maps to

Nutshell

User

1:1
Fully supported

Rezora agents are the owners of contacts and campaign sends. They are matched to Nutshell users by email address. Unmatched Rezora agents are flagged before migration — teams either invite them to Nutshell or assign their records to a fallback Nutshell user. Rezora agent roles and distribution-group permissions do not map to Nutshell's role model and must be reconfigured in Nutshell Settings.

Rezora

Contact Activity (Email Open, Click, Property View)

maps to

Nutshell

Activity / Custom Field

1:1
Fully supported

Rezora tracks per-contact engagement events tied to campaigns and property listings. Nutshell stores activity as Tasks and Events (calls, meetings, emails). We map Rezora engagement events as a custom Engagement_History__c field on each Nutshell Person record, stored as a JSON array of {event_type, campaign_name, timestamp} objects. This preserves the data for reporting but does not replicate Nutshell's native activity log format.

Rezora

Lead (Marketing-Generated)

maps to

Nutshell

Lead

1:1
Fully supported

Rezora contacts that arrived via a marketing campaign (form fill, listing inquiry) and are not yet assigned to an agent map directly to Nutshell Leads. Rezora lead status values are mapped to Nutshell Lead status values value-by-value. Rezora's lead scoring based on campaign engagement is preserved as a custom Engagement_Score__c field on the Nutshell Lead.

Rezora

Note / Comment

maps to

Nutshell

Note

1:1
Fully supported

Rezora contact notes map to Nutshell Notes on the corresponding Person record. Original author and timestamp are preserved. Notes attached to campaigns (internal agent notes) are attached to the Person record with a 'Campaign Note' prefix in the note title for identification after migration.

Rezora

Social Media Post

maps to

Nutshell

Custom Field / External Archive

1:1
Fully supported

Rezora's Social Media Management module (separate paid add-on) schedules and tracks social posts. Nutshell has no social media management capability. We export social post history as a CSV archive. Teams that rely on Rezora's social posting tool must retain access to Rezora for this function or select a dedicated social management tool post-migration.

Rezora

Attachment / File (Listing Materials, Templates)

maps to

Nutshell

Note Attachment / External Storage

1:1
Fully supported

Rezora files attached to contacts (listing flyers, contract templates) are re-uploaded to Nutshell Notes where the file size is within Nutshell's supported limits. Files exceeding Nutshell's attachment size limits are archived with a link reference to your designated cloud storage bucket. File-to-contact associations are preserved in the migration audit log.

Rezora

Property / Listing Reference

maps to

Nutshell

Custom Field on Person / Company

1:1
Fully supported

Rezora links contacts to specific property listings via the campaign model. Nutshell has no native property or listing object. We preserve listing associations as a Custom_Listing_IDs__c field on the Person record containing the Rezora listing IDs the contact has been associated with through campaigns. Manual relinking to a property management system of your choice is required post-migration.

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.

Rezora logo

Rezora gotchas

Medium

Rezora's per-feature pricing creates migration scope ambiguity

Medium

Template HTML carryover requires merge-field reformatting

Medium

Agent-level distribution lists do not map to standard CRM groups

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

  • Rezora's legacy API requires extraction path through data.rezora.com and may return stale contact records

    Rezora officially deprecated its original REST API (api.rezora.com) and directs developers to data.rezora.com/docs. The new API may return records in a different JSON structure than the legacy endpoint. Additionally, Rezora's contact records can lag MLS listing updates by up to 72 hours according to Rezora's own support documentation — this means contacts tied to recently-updated listings may carry stale property association data at extraction time. We validate record freshness against Rezora's updatedAt timestamp and flag records with potential staleness before writing to Nutshell.

  • Nutshell's contact-people terminology split in the API vs. UI causes field name mismatches

    Nutshell's UI refers to contacts as 'People' and companies as 'Companies', but the API consistently uses 'Contacts' and 'Accounts'. Custom field creation via the API requires using the entityType names from Nutshell's JSON-RPC schema — attempting to create a custom field on 'People' via API will fail because the API entity type is 'Contacts'. We target the correct API entity names (Contacts, Accounts, Leads) in all Nutshell API calls, but teams configuring fields manually in the Nutshell UI should use the UI labels. Custom field limits vary by Nutshell plan and must be verified before migration begins.

  • Rezora distribution groups have no Nutshell equivalent — N:N contact groupings collapse to a JSON custom field

    Rezora's distribution groups let agents and teams segment contacts for targeted campaign sends. A single contact can belong to multiple distribution groups simultaneously (N:N relationship). Nutshell has no native grouping object — Saved Filters provide list-based segmentation but not the same N:N membership model. We preserve all distribution group memberships as a JSON array on each Nutshell Person record (Distribution_Groups__c), but the operational segmentation workflow (agent sends from Rezora to a group) cannot be replicated in Nutshell without rebuilding the logic as a Nutshell Pro email sequence triggered by pipeline stage.

  • Rezora drip campaign event-based triggers have no Nutshell Pro equivalent

    Rezora drip campaigns are triggered by contact actions: opened email, clicked link, viewed a specific property listing, or calendar-date trigger. Nutshell Pro email sequences are triggered only by pipeline stage entry — there is no event-based trigger model in Nutshell. Contacts that enrolled in Rezora drip sequences based on property-view behavior cannot automatically re-enroll in equivalent Nutshell sequences without manual rule definition in Nutshell Pro. We export drip sequence definitions with step names, delays, and enrollment triggers as a structured rebuild reference document.

  • Nutshell's API rate limits on find operations affect large-scale delta and re-run validation

    Nutshell's API rate-limits find operations (e.g., findContacts()) with non-stub responses. During large migrations (50,000+ records), our validation re-runs against Nutshell to confirm record counts can encounter rate-limit backoff. We implement exponential backoff with retry logic on 429 responses and schedule validation passes during off-peak hours. For migrations exceeding 200,000 records, we partition the validation into batches to avoid sustained rate-limit exposure that could extend the migration timeline. Additionally, we maintain a fallback retry queue that re-attempts rate-limited requests after configurable cool-down intervals to ensure complete data validation without manual intervention.

Migration approach

Six steps for a successful Rezora to Nutshell data migration

  1. Extract Rezora data via the current API endpoint and audit custom contact properties

    FlitStack AI connects to Rezora using your current API credentials at data.rezora.com/docs. We pull contacts, companies, distribution groups, campaign records, drip campaign definitions, notes, and social post history in a single pass. Before mapping begins, we audit every custom contact property in your Rezora account to build the complete field inventory. Rezora's deprecated API endpoint (api.rezora.com) is checked for any records not present in the current API's response — discrepancies are logged and the union set is used as the migration source of truth.

  2. Resolve Rezora agents by email match to Nutshell users and flag orphaned records

    Rezora agent IDs are resolved against Nutshell user accounts by matching the agent's email address to the Nutshell user's email. Any Rezora agent without a corresponding Nutshell user account is flagged in the pre-migration report with the option to create the Nutshell user first or assign the agent's records to a designated fallback Nutshell user. This step ensures no migrated record lands without a valid owner reference in Nutshell.

  3. Migrate companies first, then people, preserving distribution-group membership as custom fields

    Nutshell requires Companies to exist before People can be linked via the company_id field. We sequence the migration: Companies (Accounts) first, then People (Contacts) with Rezora distribution-group memberships serialized into the Distribution_Groups__c custom field as a JSON array. Rezora campaign engagement metrics (open rates, click rates, listing IDs) are mapped to per-contact custom fields (Campaign_Archive__c, Engagement_Score__c, Listing_IDs__c) during the People migration pass. Notes and attachments are migrated in a final pass linked to their parent Person records.

  4. Run a sample migration with field-level diff against Nutshell

    A representative slice — typically 200–500 records spanning contacts across different Rezora distribution groups, companies, and campaign engagement levels — migrates first. We generate a field-level diff report showing source Rezora values alongside their Nutshell counterparts, flagging any truncation (e.g., Rezora industry values with no Nutshell pick-list match), any custom fields that exceeded Nutshell's plan limit, and any distribution-group JSON that was trimmed. You review the diff before the full run commits.

  5. Execute full migration with delta-pickup window and rollback readiness

    The full migration runs against Nutshell's JSON-RPC API. A delta-pickup window (typically 24–48 hours after the full run begins) captures any records created or modified in Rezora during the cutover period. An audit log records every operation — record created, updated, skipped, or flagged. If reconciliation between the Nutshell state and the source Rezora export shows discrepancies exceeding your defined threshold, one-click rollback reverts the Nutshell environment to its pre-migration state so the run can be corrected and restarted.

Platform deep dives

Context on both ends of the pair

Rezora logo

Rezora

Source

Strengths

  • Purpose-built for the brokerage-sponsor-agents data model that general CRMs do not handle natively.
  • Automated listing email triggers reduce manual follow-up for agents with active inventory.
  • Template system enables brand-controlled mass personalisation across large agent networks.
  • AI writing assistance embedded in the agent workflow reduces content creation overhead.
  • Brokerage-level analytics give franchise operators visibility into aggregate agent engagement.

Weaknesses

  • Template editor is described as clunky, limiting design quality compared to modern email builders.
  • Browser compatibility issues create inconsistent agent experience across desktop environments.
  • Limited CRM depth — no native pipeline, deal tracking, or transaction management.
  • Social media management is a separate paid tier, fragmenting the marketing stack for agents.
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 Rezora 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

    Rezora: Not publicly documented — no published numeric rate limits..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Rezora-to-Nutshell migrations complete in 48–72 hours of clock time for under 25,000 contact records. Larger accounts with 200,000+ records, extensive distribution-group hierarchies, or heavy engagement history that requires per-contact custom field creation extend to 5–8 days. Rezora's API response time and any rate-limiting from Nutshell's find operations are the longest variable in the migration timeline. Mapping Rezora distribution groups to the Distribution_Groups__c custom field adds modest processing time but does not materially extend the timeline.

Adjacent paths

Related migrations to explore

Ready when you are

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