CRM migration
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)
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between The Real Estate Platform (REP) and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1REP 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
Nutshell
Company
1:1REP 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
Nutshell
Deal
1:1REP 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
Nutshell
Deal
1:1REP 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
Nutshell
User
1:1REP 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
Nutshell
Activity
1:1REP 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)
Nutshell
Custom Field
1:1REP'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
Nutshell
Pipeline Stage
1:1REP 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
Nutshell
File
1:1REP 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
Nutshell
Lead
1:1REP 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.
| The Real Estate Platform (REP) | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person | Person1:1 | Fully supported | |
| Company / Brokerage | Company1:1 | Fully supported | |
| Listing / Property | Deal1:1 | Fully supported | |
| Deal / Transaction | Deal1:1 | Fully supported | |
| Agent / Representative | User1:1 | Fully supported | |
| Activity / Engagement Log | Activity1:1 | Fully supported | |
| Custom Field (all objects) | Custom Field1:1 | Fully supported | |
| Pipeline / Stage | Pipeline Stage1:1 | Fully supported | |
| Attachment / Document | File1:1 | Fully supported | |
| Lead / Prospect | Lead1: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.
The Real Estate Platform (REP) gotchas
White-label customization creates non-portable schema
Marketing campaign drip state does not transfer
Mobile app offline data is not exportable
Syndication channel configurations do not export
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
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.
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.
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.
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.
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
The Real Estate Platform (REP)
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 The Real Estate Platform (REP) and Nutshell.
Object compatibility
3 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
The Real Estate Platform (REP): Not publicly documented.
Data volume sensitivity
The Real Estate Platform (REP) 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 The Real Estate Platform (REP) to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave The Real Estate Platform (REP)
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.