CRM migration
Field-level mapping, validation, and rollback between Real Properties and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Real Properties
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Real Properties and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Real Properties stores real estate CRM data across contacts, companies, deals, and a dedicated property/listings object — each with platform-specific fields for listing status, property type, square footage, bedrooms, and transaction phase. Nutshell is a SMB sales CRM built around Companies, People (contacts), Leads, and Pipelines. It has no native property object, so real estate listings migrate as custom fields on the Company record or as a linked custom object, created in Nutshell before any data arrives. We map contacts directly to Nutshell People and companies directly to Nutshell Companies. Deals migrate to Nutshell Pipelines with stage-by-stage value mapping. The property listing data — fields like listing status, property type, square footage, bedroom/bathroom counts, and transaction phase — moves into custom fields that your Nutshell admin pre-creates or that FlitStack creates as part of the schema setup. Owner resolution runs by email match against Nutshell users, with unmatched owners flagged before migration commits. Activity history (calls, emails, meetings, notes) migrates as Nutshell tasks with original timestamps and parent-record links preserved. Real Properties workflows, automations, and sequence triggers do not migrate — they must be rebuilt in Nutshell using Nutshell's workflow engine and email sequence tools. We export your workflow definitions as a rebuild reference for your admin. Pricing for Real Properties to Nutshell migrations runs $500–$3,800 depending on record count, custom field count, and data-model divergence between the platforms.
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 Real Properties 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.
Real Properties
Contact
Nutshell
Person
1:1Direct map. Real Properties contacts with an email address and at least one deal association migrate as Nutshell People. People records retain the original create date and owner assignment resolved by email match. Contacts without deal history and no email may route to Nutshell Leads depending on your chosen split rule.
Real Properties
Contact (prospect-only, no deal history)
Nutshell
Lead
1:manyReal Properties contacts with no deal association and no pipeline activity split into Nutshell Leads rather than People. The split rule applies at migration time — your admin selects the threshold (e.g., zero deals, no email sent, or a specific Real Properties lifecycle stage value). Unsplit records default to People and can be recategorized in Nutshell after migration.
Real Properties
Company
Nutshell
Company
1:1Direct map. Real Properties company records migrate as Nutshell Companies with all standard fields preserved (name, website, industry, employee count, address components). A Real Properties company with multiple linked contacts creates one Nutshell Company with multiple related Person records via the people array.
Real Properties
Deal
Nutshell
Pipeline (Deal)
1:1Direct map. Real Properties deals become Nutshell Pipeline entries with deal name, amount, stage, and close date preserved. Stage names map value-by-value from Real Properties stages to the Nutshell pipeline stages your admin has configured. Deal owner resolves by email match. Historical stage-entered timestamps migrate as custom datetime fields if needed for reporting continuity.
Real Properties
Property (Listing)
Nutshell
Custom fields on Company
1:1Nutshell has no native Property or listing object. Real Properties property records — fields like listing status, property type, price, square footage, bedrooms, bathrooms, and transaction phase — migrate as custom fields on the linked Company record. FlitStack creates these custom fields in Nutshell before data lands. Your admin specifies field names and pick-list values during the planning phase.
Real Properties
Property (Listing) — multi-listing companies
Nutshell
Linked custom object
1:1If a Real Properties company has multiple active listings (common for brokerages), the listings migrate as a linked custom object in Nutshell rather than as a flat set of custom fields on the Company. Each listing record links to its Company via a lookup field. This structure keeps listing data normalized and allows each property to have its own stage, price history, and agent assignment.
Real Properties
Activity (calls, emails, meetings, notes)
Nutshell
Task / Note
1:1Real Properties call logs, email records, meeting logs, and notes migrate as Nutshell Tasks with Type = Call, Email, or Meeting. Original timestamps and owners are preserved. Notes containing file attachments or inline images are downloaded from Real Properties and re-uploaded to Nutshell's file storage, with the note body updated to reference the re-uploaded file URL.
Real Properties
User / Owner
Nutshell
Person (owner field)
1:1Owner resolution runs by email match: each Real Properties owner email is matched against Nutshell user emails. Matched owners link to the record via Nutshell's owner field. Unmatched owners (agents no longer active in Real Properties) are flagged in the pre-migration audit — your team either creates their Nutshell account or assigns their records to a fallback owner before the migration runs.
Real Properties
Custom field (Real Properties-specific)
Nutshell
Custom field
1:1Any custom fields defined in Real Properties — beyond the standard listing fields — migrate as Nutshell custom fields on the appropriate record type (Company, Person, or Lead). Pick-list values map value-by-value; text fields migrate as-is. Nutshell's custom field UI (Settings → Customize → Fields) handles field creation, or FlitStack creates them via API.
Real Properties
Attachment / File
Nutshell
File (attached to Company or Person)
1:1Real Properties file attachments on records are downloaded, then re-uploaded to Nutshell and attached to the corresponding Company or Person record. Nutshell's file storage handles the attachment, and the original filename and upload date are preserved. File size limits apply — files over Nutshell's limit are flagged and surfaced for manual handling.
| Real Properties | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Contact (prospect-only, no deal history) | Lead1:many | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Pipeline (Deal)1:1 | Fully supported | |
| Property (Listing) | Custom fields on Company1:1 | Fully supported | |
| Property (Listing) — multi-listing companies | Linked custom object1:1 | Fully supported | |
| Activity (calls, emails, meetings, notes) | Task / Note1:1 | Fully supported | |
| User / Owner | Person (owner field)1:1 | Fully supported | |
| Custom field (Real Properties-specific) | Custom field1:1 | Fully supported | |
| Attachment / File | File (attached to Company or Person)1: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.
Real Properties gotchas
Catalog entry is mismatched — realproperties.com is a brokerage, not a CRM
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
Audit Real Properties schema and build the migration map
FlitStack connects to Real Properties via API and inventories all objects, fields, custom properties, and association relationships. We identify every custom listing field (property type, sq footage, bedrooms, bathrooms, transaction phase) and every workflow definition for rebuild reference. The output is a field-level mapping document that names every source field and its destination equivalent in Nutshell, including the custom fields your admin must approve before creation. This audit typically takes 1–3 business days depending on record count.
Set up Nutshell schema: custom fields, pipelines, and stage mapping
Before any data migrates, your Nutshell admin (or FlitStack via API) creates the custom fields that will hold Real Properties listing data. FlitStack delivers a custom-field creation checklist naming each field, its type (pick-list, number, currency, date), and its parent record type (Company, Person, Lead). Pipeline stages are aligned to Real Properties deal stages value-by-value. This step runs in parallel with the source audit and typically takes 2–4 business days of admin time.
Resolve owners and run a sample migration with field-level diff
Owner resolution runs by email match: every Real Properties owner email is matched against Nutshell user emails. Unmatched owners are listed with their unassigned record count — your team invites them to Nutshell or selects a fallback owner before the migration runs. A representative sample (100–500 records spanning contacts, companies, deals, and a few property listings) migrates first. FlitStack generates a field-level diff comparing source and destination values so you can verify listing-field mapping, stage value mapping, and owner resolution before the full run commits.
Execute full migration with delta-pickup window and audit log
The full migration runs against Nutshell's JSON-RPC API. FlitStack sequences the load in dependency order: Companies first (so they exist as lookup targets), then People and Leads, then Pipeline deals, then property listing custom fields. A delta-pickup window (typically 24–48 hours after the full load starts) captures any records created or modified in Real Properties during the cutover. Every operation is logged — you receive a full audit report of records migrated, records updated in delta, and any records that failed with reason codes. One-click rollback reverts the Nutshell org to its pre-migration state if reconciliation uncovers unexpected data issues.
Platform deep dives
Real Properties
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 Real Properties 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
Real Properties: Not applicable.
Data volume sensitivity
Real Properties 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 Real Properties to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Real Properties 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 Real Properties
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.