CRM migration

Migrate from The Real Estate Platform (REP) to Nutshell

Field-level mapping, validation, and rollback between The Real Estate Platform (REP) and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

The Real Estate Platform (REP) logo

The Real Estate Platform (REP)

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between The Real Estate Platform (REP) and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

The Real Estate Platform (REP) is an enterprise real estate platform built by Phoenix Software with deep configuration capabilities spanning CRM, websites, and marketing for global brokerages. REP stores data across Contacts, Companies, Listings, and Deals with custom properties per tenant. Nutshell is a small-to-mid-market CRM that organizes data into People, Companies, Leads, and Deals with pipeline stages. The migration carries everything REP stores natively — contacts, companies, deal records, activity history, and custom fields — into Nutshell's object model. The primary translation challenges are mapping REP's listing associations into Nutshell's deal records, preserving REP's agent ownership by resolving against Nutshell users by email, and translating REP's multi-stage pipeline into Nutshell's configurable pipeline stages. Nutshell's JSON-RPC API and bulk export tools power the migration with scoped read access — your team keeps working in REP throughout the cutover window. All original create dates, agent assignments, and pipeline stage history are maintained so your Nutshell pipeline views display the complete transaction lifecycle from the first day of use.

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

The Real Estate Platform (REP) logo

The Real Estate Platform (REP)

What's pushing teams away

  • Pricing is not publicly disclosed and follows a per-feature model, making it difficult to compare costs or predict expenses when scaling teams or adding modules.
  • Limited public documentation on the API and data export options creates dependency on the vendor for any data extraction or migration work.
  • Single-vendor lock-in risk increases as brokerage data, custom configurations, and integrations all accumulate within a proprietary white-labeled instance.

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 The Real Estate Platform (REP) objects map to Nutshell

Each row shows how a The Real Estate Platform (REP) 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.

The Real Estate Platform (REP)

Contact / Person

maps to

Nutshell

Person

1:1
Fully supported

REP contacts map directly to Nutshell People with no transformation required. All standard contact fields — name, email, phone, address — migrate 1:1. REP contacts without a primary company attach as standalone People records in Nutshell, preserving all contact information independently without requiring a company association.

The Real Estate Platform (REP)

Company / Brokerage

maps to

Nutshell

Company

1:1
Fully supported

REP company records including brokerages, franchise offices, and agency names map to Nutshell Companies. Company addresses, websites, and industry classifications migrate as standard Nutshell Company fields. Parent-child company hierarchies in REP map to Nutshell's parent company association, maintaining organizational structure and reporting relationships in the new system.

The Real Estate Platform (REP)

Listing / Property

maps to

Nutshell

Deal

1:1
Fully supported

REP listings do not have a direct Nutshell equivalent — Nutshell has no native property-listing object. We transform each REP listing into a Nutshell Deal record, populating Deal name with the property address, Deal amount with the listing price, and Deal stage with a mapped pipeline stage. Listing-specific fields (MLS number, property type, status) migrate as Nutshell custom fields on the Deal.

The Real Estate Platform (REP)

Deal / Transaction

maps to

Nutshell

Deal

1:1
Fully supported

REP deal records (if REP is used with deal tracking alongside listings) map directly to Nutshell Deals. The deal amount, stage, close date, and owner migrate as standard Nutshell Deal fields. REP deal pipelines map to Nutshell pipeline stages with value-by-value translation.

The Real Estate Platform (REP)

Agent / Representative

maps to

Nutshell

User

1:1
Fully supported

REP agent records do not map to Nutshell contacts — they map to Nutshell Users. We resolve REP agent email addresses against Nutshell user accounts by email match. Unmatched agents are flagged for your team to create Nutshell user accounts before migration or assign to a fallback owner.

The Real Estate Platform (REP)

Activity / Engagement Log

maps to

Nutshell

Activity

1:1
Fully supported

REP activity logs (calls, emails, meetings, notes attached to contacts or listings) migrate as Nutshell Activities. Original timestamps and activity type are preserved. Activity owners are resolved by email match to Nutshell users — unresolved activities are assigned to the migration owner.

The Real Estate Platform (REP)

Custom Field (all objects)

maps to

Nutshell

Custom Field

1:1
Fully supported

REP's tenant-specific custom fields on any object require Nutshell custom field creation before migration. We enumerate all REP custom fields during the planning phase, create matching Nutshell custom fields for People, Companies, and Deals, then map values during migration. REP custom field data types (text, number, pick-list, date) map to equivalent Nutshell custom field types.

The Real Estate Platform (REP)

Pipeline / Stage

maps to

Nutshell

Pipeline Stage

1:1
Fully supported

REP pipeline stages (e.g., Lead, Showing Scheduled, Offer Made, Under Contract, Closed) map to Nutshell Deal stages. Each REP stage name maps to a corresponding Nutshell stage name you configure. Stage order and probability percentages are preserved from REP if available, otherwise set to Nutshell defaults.

The Real Estate Platform (REP)

Attachment / Document

maps to

Nutshell

File

1:1
Fully supported

REP file attachments on contacts, companies, or listings migrate to Nutshell's file storage on the corresponding record. Files are downloaded from REP's storage and re-uploaded to Nutshell's file attachment system with original filenames preserved. File size limits follow Nutshell's standard attachment constraints.

The Real Estate Platform (REP)

Lead / Prospect

maps to

Nutshell

Lead

1:1
Fully supported

REP records flagged as leads or prospects (not yet converted to contacts) migrate as Nutshell Leads. Lead status, source, and owner resolve by email match to Nutshell users. REP lead scores and rating values migrate as Nutshell custom fields on the Lead record.

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.

The Real Estate Platform (REP) logo

The Real Estate Platform (REP) gotchas

High

White-label customization creates non-portable schema

Medium

Marketing campaign drip state does not transfer

Medium

Mobile app offline data is not exportable

Low

Syndication channel configurations do not export

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

  • REP listings have no native Nutshell equivalent — requires deal transformation

    Nutshell has no native property-listing object. REP listings must be transformed into Nutshell Deal records. The property address becomes the Deal name, the listing price becomes the Deal value, and listing-specific fields (MLS number, property type, listing status) become Nutshell custom fields on the Deal. If REP stores multiple listings per transaction (e.g., buy-side and sell-side for the same client), each listing becomes a separate Deal in Nutshell — your team decides during planning whether to link them via a custom field or treat them independently. This transformation is manual during migration planning and must be confirmed before the sample run.

  • REP agent records do not map to Nutshell contacts — they are Nutshell users

    In REP, agents are primary records with their own profiles, permissions, and activity logs. In Nutshell, agents who need CRM access must be Nutshell Users (assigned via email). REP agent records that are also clients (e.g., referral partners who are both agents and contacts) need two records: one Nutshell User for CRM login and one Nutshell Person for the contact relationship. We handle the dual-record creation during migration, but your team confirms the rule during planning. Agents in REP who have no CRM access needs become only Person records.

  • REP multi-region pipelines require Nutshell pipeline stage planning

    If REP uses separate pipelines per region, office, or property type, these must be mapped to Nutshell pipeline stages. Nutshell supports one active pipeline per account in standard tiers, with stages configurable per pipeline. We create a mapping table during planning that assigns each REP pipeline stage to a Nutshell stage name and probability percentage. Stage names that exceed Nutshell's character limit are truncated. This mapping is validated during the sample migration run before the full cutover.

  • Custom fields require pre-migration creation in Nutshell

    REP's tenant-specific custom fields do not auto-create Nutshell equivalents. Before migration, we enumerate all REP custom fields on each object, create matching Nutshell custom fields (via Settings > Custom Fields for People, Companies, and Leads, or via Deal custom fields), and confirm the data types align. REP pick-list fields with custom values require manual value creation in Nutshell's custom field options before migration — we provide the value list as part of the migration plan.

  • REP attachments re-upload to Nutshell's file storage

    REP file attachments on contacts, companies, or listings are downloaded from the source system and re-uploaded to Nutshell's file attachment system. The original filename and upload date are preserved for audit trail continuity. Files that exceed Nutshell's attachment size limits are flagged for your team to store externally and link via URL. Inline images embedded in REP notes are extracted and re-hosted as Nutshell file attachments on the relevant record. This ensures all documentation stays associated with the correct record in Nutshell after migration.

Migration approach

Six steps for a successful The Real Estate Platform (REP) to Nutshell data migration

  1. Enumerate REP custom fields and plan Nutshell schema

    We extract the complete list of REP custom fields across all objects, identify data types, and create corresponding Nutshell custom fields for People, Companies, Leads, and Deals. We also map REP pipeline stages to Nutshell stages and confirm whether REP listings will create Deal records. This produces a migration schema document your team reviews and approves before any data moves.

  2. Resolve agent and owner records by email

    REP agent records and deal owners are matched against Nutshell Users by email address. Unmatched agents are flagged in a pre-migration report — your team creates Nutshell user accounts for them or designates a fallback owner. No deal or contact migrates without a resolved owner. This step also identifies REP agents who need dual records (User + Person) for cases where they are also clients.

  3. Migrate companies and people first, then leads and deals

    Nutshell requires Accounts (Companies) to exist before People can link to them via company association. We sequence the migration: Companies first, then People and Leads with company resolution, then Deals with contact-role linking and owner resolution. Activities attach to their parent records after the parent records exist. This sequencing ensures referential integrity in Nutshell from the moment records land, preventing orphaned data and maintaining proper relationships throughout the migration.

  4. Run sample migration with field-level diff

    A representative slice — typically 100–300 records spanning contacts, companies, deals, and activities — migrates first. We generate a field-level comparison showing every REP field, its Nutshell destination, and the migrated value. You verify listing-to-deal transformation, custom field population, and owner resolution before we commit to the full run. Any mapping adjustments are documented and applied before the production migration starts, ensuring accuracy.

  5. Full migration with delta-pickup window

    The full dataset migrates to Nutshell. A delta-pickup window (typically 24–48 hours) captures any records created or modified in REP during the cutover — your team keeps working in REP throughout this period. Audit log records every operation. If reconciliation fails, one-click rollback reverts the Nutshell instance to its pre-migration state so you can correct the mapping and retry. This approach protects your data and minimizes risk throughout the migration process.

Platform deep dives

Context on both ends of the pair

The Real Estate Platform (REP) logo

The Real Estate Platform (REP)

Source

Strengths

  • White-label deployment aligns the entire platform with brokerage branding and local market configurations.
  • Multi-currency and multi-lingual support handles global brokerage operations without separate instances.
  • Integrated lead, listing, and transaction management reduces data silos across brokerage operations.
  • Hierarchical structure maps naturally to real-world brokerage org charts of regions, offices, and agents.

Weaknesses

  • No public pricing transparency makes cost planning and vendor comparison difficult.
  • Limited external API documentation restricts third-party integrations and self-service migration tooling.
  • Each instance is uniquely configured, making schema discovery and migration mapping project-specific and time-intensive.
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. 3 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 The Real Estate Platform (REP) and Nutshell.

  • Object compatibility

    B

    3 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

    The Real Estate Platform (REP): Not publicly documented.

  • Data volume sensitivity

    B

    The Real Estate Platform (REP) doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your The Real Estate Platform (REP) 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 The Real Estate Platform (REP) to Nutshell data migrations

Answers to the questions buyers ask most during The Real Estate Platform (REP) to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your The Real Estate Platform (REP) to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most REP-to-Nutshell migrations complete in 48–72 hours of clock time for under 25,000 records. REP setups with complex custom field configurations or multi-region pipeline mapping extend to 5–7 days. The longest planning step is enumerating REP's custom fields and mapping them to Nutshell equivalents — this happens before any data moves and typically takes 1–3 business days of your team's review time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from The Real Estate Platform (REP).
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