CRM migration
Field-level mapping, validation, and rollback between Rezora and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Rezora
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Rezora and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Rezora 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
Nutshell
Company
1:1Rezora 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
Nutshell
Custom List / Custom Field
1:1Rezora 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
Nutshell
Saved Filter / Campaign Reference
1:1Rezora 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
Nutshell
Personal Email Sequence (Nutshell Pro)
1:1Rezora 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
Nutshell
User
1:1Rezora 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)
Nutshell
Activity / Custom Field
1:1Rezora 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)
Nutshell
Lead
1:1Rezora 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
Nutshell
Note
1:1Rezora 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
Nutshell
Custom Field / External Archive
1:1Rezora'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)
Nutshell
Note Attachment / External Storage
1:1Rezora 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
Nutshell
Custom Field on Person / Company
1:1Rezora 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.
| Rezora | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company / Brokerage | Company1:1 | Fully supported | |
| Distribution Group | Custom List / Custom Field1:1 | Fully supported | |
| Campaign | Saved Filter / Campaign Reference1:1 | Fully supported | |
| Drip Campaign Sequence | Personal Email Sequence (Nutshell Pro)1:1 | Fully supported | |
| Agent / User | User1:1 | Fully supported | |
| Contact Activity (Email Open, Click, Property View) | Activity / Custom Field1:1 | Fully supported | |
| Lead (Marketing-Generated) | Lead1:1 | Fully supported | |
| Note / Comment | Note1:1 | Fully supported | |
| Social Media Post | Custom Field / External Archive1:1 | Fully supported | |
| Attachment / File (Listing Materials, Templates) | Note Attachment / External Storage1:1 | Fully supported | |
| Property / Listing Reference | Custom Field on Person / Company1: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.
Rezora gotchas
Rezora's per-feature pricing creates migration scope ambiguity
Template HTML carryover requires merge-field reformatting
Agent-level distribution lists do not map to standard CRM groups
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
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.
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.
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.
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.
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
Rezora
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 Rezora 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
Rezora: Not publicly documented — no published numeric rate limits..
Data volume sensitivity
Rezora 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 Rezora to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Rezora 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 Rezora
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.