CRM migration
Field-level mapping, validation, and rollback between Real Estate 7 and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Real Estate 7
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between Real Estate 7 and Nutshell.
Complexity
BStandard
Timeline
48–96 hours
Overview
Real Estate 7 bundles a WordPress theme with CT Leads Pro CRM functionality — contact management, lead capture, deal pipelines, and listing analytics are all part of the same plugin ecosystem. There is no standard REST API; data lives in the WordPress database and must be extracted via direct query or WP-CLI export. Nutshell is a standalone CRM with a JSON-RPC API, standard objects for People, Companies, Leads, and Deals, and custom fields for industry-specific data that does not fit the default schema. The migration maps Real Estate 7 contacts and leads to Nutshell People and Leads, maps deal pipelines to Nutshell's standard Deals module with stage mapping, and maps the property address and listing metadata that Real Estate 7 stores as custom WordPress postmeta into Nutshell custom fields on the relevant Person or Company record. The WordPress database export requires read-only database credentials; we use the MySQL export to build the record set, then transform and load via Nutshell's API. We do not migrate workflows, drip campaigns, or email automation logic from Real Estate 7 — those must be rebuilt as Nutshell personal email sequences after migration. We also do not migrate IDX/MLS integration connections; those must be re-established with your preferred IDX provider post-migration. The migration does carry activity history (notes, tasks, completed activities) and file attachments where those are stored in WordPress media. The typical Real Estate 7 to Nutshell migration runs in 48–96 hours of clock time for under 30,000 records, with a 24–48 hour delta pickup window capturing any new leads or deals created during cutover.
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 Estate 7 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 Estate 7
Real Estate 7 Contact / Lead
Nutshell
Nutshell Person
1:1Real Estate 7 stores contacts and leads as WordPress users and CRM entries. FlitStack AI extracts these records and loads them into Nutshell People, mapping the full name, email, phone, and address fields directly. Active deals associated with each contact are linked via Nutshell's Person-Deal association after the deals object is populated.
Real Estate 7
Real Estate 7 Company / Brokerage Record
Nutshell
Nutshell Company
1:1Real Estate 7 stores brokerage and company associations as separate records in the CRM module. These map to Nutshell Company records, preserving the company name, domain, address, and industry fields. Contacts without a primary company association are attached to a placeholder 'Unassigned' Company record in Nutshell.
Real Estate 7
Real Estate 7 Deal / Transaction Record
Nutshell
Nutshell Deal
1:1Each Real Estate 7 deal record — representing a transaction, listing, or sales opportunity — maps to a Nutshell Deal. The deal name, amount, stage, and close date are mapped directly. Real Estate 7 stage values are mapped to Nutshell stage names via a value-mapping table we build during the discovery phase.
Real Estate 7
Real Estate 7 Deal Stage
Nutshell
Nutshell Deal Stage
1:1Real Estate 7 pipeline stages (e.g., New Lead, Showing Scheduled, Offer Made, Under Contract, Closed) map to Nutshell deal stages on a value-by-value basis. We preserve the stage-entered timestamp as a custom field in Nutshell so reporting continuity is maintained. If Nutshell's default stages do not match Real Estate 7's labels, we create custom stage names before migration.
Real Estate 7
Real Estate 7 Property / Listing Record
Nutshell
Nutshell Person / Company (custom fields)
1:1Real Estate 7's property and listing records have no direct Nutshell equivalent since Nutshell lacks a native real estate object. FlitStack AI extracts property address, listing price, property type, MLS number, and listing status from WordPress postmeta and maps these as custom fields on the Nutshell Person record associated with the seller or buyer, and on the Nutshell Company record for the brokerage listing the property.
Real Estate 7
Real Estate 7 Lead Source
Nutshell
Nutshell Person (custom field)
1:1Real Estate 7 tracks where leads originate — website form, IDX search, referral, agent introduction. Nutshell does not have a native lead source field on People. We create a Lead_Source__c custom field on Nutshell People and populate it from Real Estate 7's lead source property, preserving attribution data for post-migration marketing analysis.
Real Estate 7
Real Estate 7 Note / Activity
Nutshell
Nutshell Activity
1:1Real Estate 7's internal notes and logged activities (showing feedback, offer notes, client communication) map to Nutshell Activities attached to the relevant Person or Deal. Original timestamps and the agent who logged the note are preserved. Nutshell Activities are displayed inline on the Person record timeline.
Real Estate 7
Real Estate 7 Owner / Agent Assignment
Nutshell
Nutshell User (email match)
1:1Real Estate 7 assigns each contact, lead, and deal to a WordPress user. FlitStack AI resolves these assignments by matching the WordPress user email address to an active Nutshell user account. Unmatched owners are flagged before migration — the team either creates a Nutshell user for them or assigns their records to a fallback owner. No record lands in Nutshell without an assigned owner.
Real Estate 7
Real Estate 7 Attachment / File
Nutshell
Nutshell Attachment
1:1Files attached to Real Estate 7 contact or deal records — such as offer documents, property disclosures, or client agreements stored in WordPress Media — are downloaded and re-uploaded as Nutshell Attachments linked to the corresponding Person or Deal record. Nutshell's 25MB per-file limit is enforced; files exceeding this threshold are flagged for manual handling.
Real Estate 7
Real Estate 7 Workflow / Drip Campaign
Nutshell
Not migrated — export-for-rebuild only
1:1Real Estate 7 automation rules and drip campaign sequences cannot be migrated in structure. FlitStack AI exports the rule definitions — trigger conditions, delay intervals, and action steps — as a formatted reference document your team can use to rebuild equivalent personal email sequences in Nutshell Pro or Business. This is delivered as a structured export alongside the data migration.
Real Estate 7
Real Estate 7 IDX / MLS Connection
Nutshell
Not migrated — must be re-established
1:1Real Estate 7's IDX and MLS integrations are WordPress-plugin-level connections that have no equivalent in Nutshell's standalone CRM. These must be re-established with your preferred IDX provider (such as Follow Up Boss, Realtyna, or iHomeFinder) after the CRM migration is complete. Nutshell supports third-party integrations via Zapier and its native integration marketplace.
| Real Estate 7 | Nutshell | Compatibility | |
|---|---|---|---|
| Real Estate 7 Contact / Lead | Nutshell Person1:1 | Fully supported | |
| Real Estate 7 Company / Brokerage Record | Nutshell Company1:1 | Fully supported | |
| Real Estate 7 Deal / Transaction Record | Nutshell Deal1:1 | Fully supported | |
| Real Estate 7 Deal Stage | Nutshell Deal Stage1:1 | Fully supported | |
| Real Estate 7 Property / Listing Record | Nutshell Person / Company (custom fields)1:1 | Fully supported | |
| Real Estate 7 Lead Source | Nutshell Person (custom field)1:1 | Fully supported | |
| Real Estate 7 Note / Activity | Nutshell Activity1:1 | Fully supported | |
| Real Estate 7 Owner / Agent Assignment | Nutshell User (email match)1:1 | Fully supported | |
| Real Estate 7 Attachment / File | Nutshell Attachment1:1 | Fully supported | |
| Real Estate 7 Workflow / Drip Campaign | Not migrated — export-for-rebuild only1:1 | Fully supported | |
| Real Estate 7 IDX / MLS Connection | Not migrated — must be re-established1: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 Estate 7 gotchas
No documented public API for data export
CRM access locked to yearly subscription tier
WordPress plugin state affects migration integrity
Follow Up Boss integration is one-directional sync
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
Establish WordPress database access and extract the CRM record set
FlitStack AI requests read-only MySQL credentials for the WordPress database. We query the wp_posts table for CT Leads Pro post types (contacts, leads, deals) and the wp_postmeta table for all associated custom field values. We also extract WordPress user accounts to build the owner-email-to-Nutshell-user resolution table. The extracted record set is validated against the WordPress schema version to handle plugin updates that may have altered table structure. This step produces a structured JSON dataset ready for transformation.
Run a data integrity scan and flag records with corrupted or null required fields
Before any transformation logic runs, FlitStack AI scans the extracted dataset for records with missing email addresses, orphaned deal associations, null required fields, and stage values that do not match the configured pipeline. Records flagged by this scan are documented in a remediation report delivered to your team. We recommend resolving these records in WordPress before migration begins to prevent invalid data from landing in Nutshell.
Provision Nutshell custom fields for property, deal, and person extensions
FlitStack AI provisions all required custom fields in Nutshell via the API before the migration run begins. This includes property address fields, listing status pick-lists, MLS number fields, commission rate fields, and lead score fields on the Person and Deal objects. Each custom field is typed at creation time (text, number, pick-list, currency, datetime) to match the data in Real Estate 7. This step ensures Nutshell's schema is complete before any data is written.
Resolve WordPress users to Nutshell user accounts by email match
The WordPress user table is matched against active Nutshell user accounts by email address. Each Real Estate 7 contact, lead, and deal owner assignment is mapped to a Nutshell user ID. Any WordPress user without a corresponding Nutshell account is flagged on the resolution report — your team either creates the Nutshell user before migration or assigns those records to a fallback owner. No record is written to Nutshell without a confirmed owner assignment.
Execute a sample migration with field-level diff and verify key mappings
A representative slice of 100–300 records — covering contacts, companies, deals, and a sample of custom property fields — is migrated first. FlitStack AI generates a field-level diff showing the source value, mapped value, and any transformation applied for each field. Your team reviews the diff to confirm stage mapping, custom field population, and owner resolution before the full run commits. Any mapping adjustments are applied before the full migration.
Run full migration with delta pickup and post-migration reconciliation
The full migration writes all validated records to Nutshell via the API. A delta pickup window (typically 24 hours after the full run starts) captures any new contacts, leads, or deals created or modified in Real Estate 7 during the cutover period. FlitStack AI generates a reconciliation report comparing record counts, field completeness, and owner assignments between the source and destination. One-click rollback is available if the reconciliation fails to meet the agreed threshold.
Platform deep dives
Real Estate 7
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 Real Estate 7 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
Real Estate 7: Not publicly documented.
Data volume sensitivity
Real Estate 7 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 Estate 7 to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Real Estate 7 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 Estate 7
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.