CRM migration

Migrate from Real Estate 7 to Nutshell

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 logo

Real Estate 7

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between Real Estate 7 and Nutshell.

Complexity

BStandard

Timeline

48–96 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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 Estate 7 logo

Real Estate 7

What's pushing teams away

  • Agents outgrow the WordPress plugin model when they need a full-featured cloud CRM with mobile-first apps, advanced automation, and team collaboration tools.
  • The yearly-only license model frustrates agents who want a one-time purchase with permanent access to current features without subscription renewals.
  • Real Estate 7 lacks a robust public API, making it difficult to export data programmatically or build custom integrations beyond Follow Up Boss.
  • Brokers managing multiple agents find the per-site licensing and WordPress-centric architecture harder to scale compared to multi-tenant SaaS CRMs.

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

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

maps to

Nutshell

Nutshell Person

1:1
Fully supported

Real 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

maps to

Nutshell

Nutshell Company

1:1
Fully supported

Real 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

maps to

Nutshell

Nutshell Deal

1:1
Fully supported

Each 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

maps to

Nutshell

Nutshell Deal Stage

1:1
Fully supported

Real 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

maps to

Nutshell

Nutshell Person / Company (custom fields)

1:1
Fully supported

Real 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

maps to

Nutshell

Nutshell Person (custom field)

1:1
Fully supported

Real 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

maps to

Nutshell

Nutshell Activity

1:1
Fully supported

Real 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

maps to

Nutshell

Nutshell User (email match)

1:1
Fully supported

Real 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

maps to

Nutshell

Nutshell Attachment

1:1
Fully supported

Files 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

maps to

Nutshell

Not migrated — export-for-rebuild only

1:1
Fully supported

Real 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

maps to

Nutshell

Not migrated — must be re-established

1:1
Fully supported

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

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 Estate 7 logo

Real Estate 7 gotchas

High

No documented public API for data export

High

CRM access locked to yearly subscription tier

Medium

WordPress plugin state affects migration integrity

Medium

Follow Up Boss integration is one-directional sync

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

  • Real Estate 7 has no standard REST API for CRM records — database access is required

    Real Estate 7 is a WordPress plugin, not a SaaS platform with a documented API endpoint. CRM records (contacts, leads, deals) are stored as WordPress post types and postmeta in the MySQL database. FlitStack AI requests read-only database credentials and builds the extraction query from the WordPress schema — specifically the wp_posts and wp_postmeta tables where CT Leads Pro stores its data. If the database uses a custom table prefix or the plugin tables have been renamed, the extraction query must be adjusted during discovery. API-based migration tools will not work against Real Estate 7 because no public API endpoint exists for CRM record export.

  • Property and listing records require custom field provisioning in Nutshell before migration

    Real Estate 7 stores property address, listing price, MLS number, and listing status as custom WordPress postmeta fields. Nutshell does not have a native real estate property object, so this data must be mapped to custom fields on the Person or Deal record. FlitStack AI provisions these custom fields in Nutshell via the API before the migration run — but Nutshell's API limits custom field creation to one call per field, and each field must be typed (text, number, pick-list, currency, datetime) at creation time. If Real Estate 7 stores a property address as a single long-text field and you need it split into street/city/state/zip in Nutshell, a transformation step is required before the API write. We build this transformation logic during the sample migration phase.

  • WordPress plugin conflicts can silently corrupt Real Estate 7 CRM data

    Real Estate 7 reviews on G2 document a recurring pain point: third-party plugins that ship with or are installed alongside the theme (specifically the miniOrange Social Login plugin) cause data inconsistencies in the CRM records. The plugin conflict does not necessarily delete records — it may corrupt postmeta values, reset deal stages to default, or break contact-to-deal associations silently. Before migration, FlitStack AI runs a data integrity scan against the WordPress database to identify records with null required fields, orphaned deal associations, and stage values that do not match the configured pipeline. Records flagged by this scan are surfaced to your team for resolution before migration begins.

  • IDX and MLS connections cannot be migrated and must be re-established post-migration

    Real Estate 7's IDX/MLS integration — which pulls live listing data into the WordPress website — is a plugin-level connection that has no equivalent in Nutshell's standalone CRM. Nutshell does not have a native IDX or MLS feed consumer. After migration, your team must select and configure a new IDX provider (such as Follow Up Boss, Realtyna, or iHomeFinder) and reconnect it directly to your WordPress website or a separate property search tool. The CRM data migration does not affect your existing IDX setup, but the two systems will be disconnected until the IDX is reconnected to the new website.

  • Real Estate 7 drip campaigns and automation rules have no export format

    Real Estate 7's drip campaign logic — including trigger conditions, delay intervals, enrollment rules, and email content — is stored in the WordPress database in a format specific to the plugin's internal state machine. There is no documented export format, API endpoint, or third-party tool that can read these rules. FlitStack AI cannot migrate automation rules in working form. We do offer a structured export of the automation rule definitions as a reference document (rule name, trigger type, step sequence, delay duration, and associated contact lists) that your team can use to rebuild equivalent sequences in Nutshell Pro's personal email sequences feature. This export is delivered as part of the standard migration package.

Migration approach

Six steps for a successful Real Estate 7 to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

Real Estate 7 logo

Real Estate 7

Source

Strengths

  • Bundles IDX website builder and CRM in a single WordPress install, reducing vendor count and monthly costs.
  • Strong G2 ratings for ease of use, setup speed, and admin simplicity versus competitors.
  • Includes SMS alerts, 200+ Elementor design blocks, and marketing automation without per-seat pricing.
  • Direct Follow Up Boss integration for agents who already use that lead management tool.
  • Yearly license includes lifetime support and ongoing feature updates as part of the subscription.

Weaknesses

  • No public API documented, limiting programmatic data export and custom integration options.
  • Yearly subscription required for CRM access and updates; one-time license only includes 6 months of support.
  • Self-hosted WordPress plugin means the customer is responsible for hosting, security, backups, and performance.
  • Limited multi-agent collaboration features compared to standalone cloud CRMs with advanced team permissions and shared workspaces.
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 Real Estate 7 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

    Real Estate 7: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most Real Estate 7 to Nutshell migrations complete in 48–96 hours of clock time for under 30,000 records. The WordPress database extraction and custom field provisioning in Nutshell are the longest steps. Setups with more than 30,000 records, heavy custom property field usage, or significant data integrity issues extend to 5–10 days. The delta pickup window adds an additional 24–48 hours after the full run starts.

Adjacent paths

Related migrations to explore

Ready when you are

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