CRM migration

Migrate from Real Properties to Nutshell

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

Real Properties logo

Real Properties

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between Real Properties and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Real Properties logo

Real Properties

What's pushing teams away

  • Not applicable — there is no platform to leave. realproperties.com is a brokerage marketing site.
  • If the catalog intended to reference Lone Wolf's CRM product (the technology platform powering this site), users would migrate away for the typical reasons Lone Wolf customers cite (cost, support, integration depth) — but that is a separate product not at this URL.

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

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

maps to

Nutshell

Person

1:1
Fully supported

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

maps to

Nutshell

Lead

1:many
Fully supported

Real 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

maps to

Nutshell

Company

1:1
Fully supported

Direct 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

maps to

Nutshell

Pipeline (Deal)

1:1
Fully supported

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

maps to

Nutshell

Custom fields on Company

1:1
Fully supported

Nutshell 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

maps to

Nutshell

Linked custom object

1:1
Fully supported

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

maps to

Nutshell

Task / Note

1:1
Fully supported

Real 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

maps to

Nutshell

Person (owner field)

1:1
Fully supported

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

maps to

Nutshell

Custom field

1:1
Fully supported

Any 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

maps to

Nutshell

File (attached to Company or Person)

1:1
Fully supported

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

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.

Real Properties logo

Real Properties gotchas

High

Catalog entry is mismatched — realproperties.com is a brokerage, not a CRM

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

  • Nutshell has no native Property object — real estate listings must be custom fields

    Nutshell's data model is built for general B2B sales. It has no Property or Listing object, so every field that represents a real estate listing — listing status, property type, price, square footage, bedrooms, bathrooms, and transaction phase — must be created as custom fields in Nutshell before data lands. If your Real Properties account has a high number of listing fields per property, this adds a schema-creation step to the migration plan. FlitStack delivers a Nutshell custom-field creation checklist before the migration runs, so your admin can pre-create the fields or approve FlitStack creating them via API.

  • Real Properties workflows and automations do not migrate to Nutshell

    Any workflows, triggers, email sequences, or automation rules defined in Real Properties will not transfer to Nutshell. This is a universal limitation of CRM migrations — automation logic is destination-platform-specific. In Real Properties to Nutshell migrations, the impact is particularly noticeable for teams that built extensive lead-nurture sequences tied to listing-status changes or transaction-phase transitions. FlitStack exports your Real Properties workflow definitions as a reference document your Nutshell admin can use to rebuild equivalent logic using Nutshell's workflow engine and email sequence tools. Plan 1–3 weeks for a thorough rebuild of critical automations.

  • Contact-to-Lead split requires a defined rule before migration runs

    Nutshell separates People (active contacts with deal history) from Leads (early-stage prospects). Real Properties uses a unified Contact object with a lifecycle or status property. If your Real Properties data uses a status field to distinguish prospects from clients, that value drives the split: contacts meeting the 'active client' rule become Nutshell People; everyone else becomes Leads. If no split rule is defined, all Real Properties contacts land as Nutshell People and your admin can manually recategorize prospects as Leads afterward. The split decision must be made before migration starts — it affects record counts per object and downstream reporting.

  • Multi-listing companies require a linked custom object structure in Nutshell

    Brokerages managing multiple listings per company in Real Properties face a structural mismatch in Nutshell. One Real Properties company record can link to multiple Property/listing records. In Nutshell, without a native Property object, the migration must either flatten all listings into custom fields on the Company (works for 1–2 listings per company) or create a linked custom object in Nutshell to represent listings with a lookup back to the Company. FlitStack identifies multi-listing companies in the pre-migration audit and recommends the appropriate strategy (custom object vs. custom fields) based on the listing density per account.

  • Real Properties to Nutshell API rate limits affect large migration throughput

    Nutshell's JSON-RPC API (app.nutshell.com/api/v1/json) has per-account rate limits. During a large Real Properties export, pagination and request throttling can extend the data extraction phase. FlitStack handles rate-limit backoff automatically and falls back to bulk CSV export where the source platform supports it. For Real Properties accounts with more than 100,000 records, the extraction phase may add 6–12 hours to the timeline. The full migration (extraction, transformation, load) still completes within the 5–7 day window for large datasets.

Migration approach

Six steps for a successful Real Properties to Nutshell data migration

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

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

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

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

Context on both ends of the pair

Real Properties logo

Real Properties

Source

Strengths

  • Not applicable — no software product exists at the catalog URL.

Weaknesses

  • Catalog mismatch — the listed website is a brokerage marketing site, not a CRM platform.
  • No data model, API, or migration path exists at this URL.
  • Buyers seeking the underlying Lone Wolf platform should look up Lone Wolf directly (lwolf.com).
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 Real Properties 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

    Real Properties: Not applicable.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most Real Properties to Nutshell migrations complete in 24–72 hours of clock time for datasets under 5,000 records. Larger setups with 100,000+ records, multiple listing custom fields per company, or multi-listing custom object structures extend to 5–7 days. The longest planning step is Nutshell custom field setup — your admin approving or creating the listing-specific fields (property type, sq footage, bedrooms, bathrooms, transaction phase) before data lands. Actual data movement is typically the shortest phase once schema is confirmed.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Real Properties.
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