CRM migration

Migrate from IDX Broker to Nutshell

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

IDX Broker logo

IDX Broker

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between IDX Broker and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

IDX Broker is a real estate website and IDX platform — it captures leads through website forms, displays MLS listings, and stores saved-search metadata. It does not have a native pipeline, company object, or activity log. Nutshell is a structured CRM with People, Companies, Leads, Deals, and Activities. The migration carries IDX Broker contacts and leads into Nutshell People records, maps saved-search and property-interest metadata into custom fields, and resolves owner assignments by email match against Nutshell users. MLS listing data displayed through IDX Broker pages is not CRM data and does not migrate — the IDX platform continues to serve the public-facing listing site independently. We run a sample migration against a representative contact slice before the full cutover, generate a field-level diff, and capture any new records created during the delta window. During the sample phase, we validate field mapping, custom field population, and owner resolution across a representative slice, typically 50–200 records, generating a field-level diff for your review. Any discrepancies are corrected before the full cutover to ensure data integrity and minimize post-migration cleanup.

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

IDX Broker logo

IDX Broker

What's pushing teams away

  • The subdomain-based IDX page hosting (yourwebsite.idxbroker.com) can hurt SEO performance since search engines index the subdomain instead of the agent's own domain, causing some agents to lose organic search equity when switching providers.
  • The MLS approval process requires paper agreements and board sign-off before IDX data access is granted, adding 3-7 days of waiting time that frustrates agents who need quick onboarding.
  • Agents with complex lead management needs find IDX Broker limited compared to full CRM platforms, prompting moves toward solutions like Follow Up Boss, BoomTown, or BoldTrail that combine IDX with pipeline management.

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

Each row shows how a IDX Broker 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.

IDX Broker

Contact (Website Lead)

maps to

Nutshell

Person

1:1
Fully supported

IDX Broker contacts captured through website lead forms map directly to Nutshell Person records. Each contact record is a standalone Person. Original IDX Broker creation date is preserved as a custom field since Nutshell Created Date reflects the import timestamp.

IDX Broker

Saved Search

maps to

Nutshell

Custom field on Person

1:1
Fully supported

IDX Broker stores saved-search criteria (price range, neighborhood, bedrooms, property type) as structured metadata per contact. This data has no native equivalent in Nutshell. We create a Saved_Search_Criteria__c custom field on the Person object and stores the JSON or formatted string of the saved search parameters.

IDX Broker

Property Interest / Listing View

maps to

Nutshell

Custom field on Person

1:1
Fully supported

IDX Broker records which listings a contact viewed or favorited. We migrate this as a Property_Interest__c custom field (long text) on the Nutshell Person record so agents know what properties a lead was considering at the time of migration. The field captures listing IDs, addresses, and any notes, allowing agents to quickly see a prospect’s property preferences without reverting to the IDX system.

IDX Broker

Lead Source Attribution

maps to

Nutshell

Person source field

1:1
Fully supported

IDX Broker captures lead source — which webpage form, IDX page, or organic search — as a standard field. This maps to the Nutshell Person source field directly, preserving the attribution channel for lead quality analysis. Accurate source attribution helps marketing teams allocate budget effectively and enables sales to prioritize leads from high‑performing channels.

IDX Broker

Company Name (if present)

maps to

Nutshell

Company

many:1
Fully supported

Some IDX Broker contacts include a company name from the website form. We check each contact for a company field. If present, we create or match a Nutshell Company record and link the Person via the company relationship. Contacts without a company name land as standalone People.

IDX Broker

IDX Broker User / Agent Account

maps to

Nutshell

Nutshell User

1:1
Fully supported

IDX Broker agent user accounts are mapped to Nutshell users by email address match. Unmatched agents are flagged before migration. Their contacts can be assigned to a fallback owner or the Nutshell admin account during the migration run. If multiple IDX accounts share the same email domain, we verify each account’s contact set to avoid mixing ownership, and we log any ambiguous matches for manual review.

IDX Broker

Contact Creation Timestamp

maps to

Nutshell

Custom datetime field on Person

1:1
Fully supported

Nutshell's built-in Created Date reflects when the record was inserted during migration, not when the contact originally submitted through the IDX Broker website. We preserve the original timestamp as Original_Lead_Created_Date__c for reporting continuity. This ensures that historical lead age and time‑to‑first‑contact metrics remain accurate in Nutshell reports, supporting reliable trend analysis.

IDX Broker

Contact Modified Timestamp

maps to

Nutshell

Custom datetime field on Person

1:1
Fully supported

Modified date from IDX Broker is preserved as Original_Lead_Modified_Date__c on the Nutshell Person record. This is important for reconciliation and delta-pickup logic during the cutover window. By keeping the original modification timestamp, we can identify contacts that changed after the initial export, ensuring that any updates made in IDX Broker during the migration window are reflected in Nutshell without data loss.

IDX Broker

MLS Listing Data (display data)

maps to

Nutshell

No equivalent in Nutshell

1:1
Fully supported

IDX Broker serves live MLS listing data on the public website. This is website display data, not CRM data, and it remains in the IDX platform. Nutshell is a CRM and does not store MLS listings. The IDX site continues to operate independently post-migration.

IDX Broker

IDX Broker Lead Form Submissions

maps to

Nutshell

Person notes or custom field

1:1
Fully supported

Free-text responses submitted through IDX Broker lead forms (e.g., 'Tell us about your home search') are captured as note text or a custom field on the Nutshell Person record. The format depends on whether the response is a single short text or a longer narrative.

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.

IDX Broker logo

IDX Broker gotchas

High

Subdomain-based IDX page hosting affects SEO

High

MLS board approval requires paper agreements before data access

Medium

Wrapper-page system causes theme conflicts

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

  • IDX Broker has no pipeline, deal, or company object — schema is flatter than Nutshell's

    IDX Broker's data model is limited to contacts/leads, saved-search metadata, and listing-view records. It has no Companies, Deals, or Activity objects. When migrating to Nutshell, the schema gap means you start with People records only — the Nutshell pipeline, Deals, and Companies are not pre-populated from IDX Broker data. Your team needs to configure pipeline stages and decide how to model in-progress transactions before or during the migration. We deliver a schema-setup guide as part of the engagement so Nutshell's side is ready when data lands.

  • Saved-search metadata requires custom field creation in Nutshell before migration runs

    IDX Broker stores a contact's saved-search criteria — price range, neighborhood, bedroom count, property type — as structured metadata attached to the contact record. Nutshell has no native saved-search field. This metadata does not migrate automatically. We create Saved_Search_Criteria__c and related custom fields on the Nutshell Person object before the migration runs. If your team has many saved searches, each custom field counts toward the field-complexity factor in your quote. Custom field setup is the longest pre-migration step for IDX Broker migrations.

  • Owner resolution depends on email matching across IDX Broker and Nutshell user accounts

    IDX Broker does not assign explicit owners to contacts — ownership is implicit based on which agent's IDX account captured the lead. Nutshell requires an explicit Owner (user) on every record. We resolve owners by matching the IDX Broker agent's email to a Nutshell user email. If an IDX agent account email does not correspond to any Nutshell user, those contacts are flagged before migration and assigned to a fallback owner. Mismatched agent emails are the most common source of migration delays for this pair.

  • MLS listing data displayed on IDX Broker pages is not CRM data and does not migrate

    IDX Broker's core function is serving live MLS listing data on agent websites — listing addresses, photos, prices, and status updates. This is website display data stored in the IDX platform's MLS feed, not CRM data. It does not move to Nutshell. After the migration, the IDX Broker site continues to serve listing data independently. If your team needs to associate specific listings with Nutshell Person records (e.g., which listing a lead is interested in), that association is handled through the Property_Interest__c custom field using listing IDs or addresses from the saved-search metadata.

  • Contact quality from IDX Broker forms varies significantly — duplicate records are common

    IDX Broker lead forms on real estate websites often capture contacts who submitted partial information, used different email addresses for different property searches, or submitted through multiple IDX pages on the same website. Duplicate contacts are a known issue in IDX Broker exports. We run a de-duplication pass before migration: matching by email address is the primary key, with secondary matching on name + phone. We flag ambiguous duplicates for your team to resolve before the full run rather than importing duplicates into Nutshell.

Migration approach

Six steps for a successful IDX Broker to Nutshell data migration

  1. Audit IDX Broker contact records and custom metadata

    We connect to the IDX Broker account via API using scoped read access. We extract all contacts and leads, catalog every saved-search record, listing-view event, and lead-form submission, and identify the owner assignment pattern. We produce a data quality report flagging duplicates, missing required fields (e.g., contacts without a last name), and contacts without an owner email match in the Nutshell tenant.

  2. Create custom fields on Nutshell Person and Company objects

    Before any data moves, we create the custom fields required to hold IDX Broker metadata: Saved_Search_Criteria__c, Property_Interest__c, Listing_Saved_Date__c, Original_Lead_Created_Date__c, Original_Lead_Modified_Date__c, Source_System_ID__c, Webpage_Source__c, Budget_Range__c, and any other fields identified in the audit. We deliver a field-setup checklist so your Nutshell admin can pre-create these or grant us API access to create them directly. We also confirm field types match source data (text, date, datetime, long text) and run a quick validation to ensure fields appear correctly in Nutshell before the migration starts.

  3. Resolve owners and map contacts to People or Leads

    We match IDX Broker agent emails to Nutshell user emails. Unmatched agents are flagged and assigned to a fallback Nutshell user. Each contact is classified as a Nutshell Person (for known clients) or a Nutshell Lead (for early-stage prospects) based on the contact's status or lead score in IDX Broker. We generate a mapping plan and run a sample migration against 50–200 records to validate owner resolution, field mapping, and custom field population before the full run.

  4. Run sample migration with field-level diff

    A representative slice of contacts — including records with saved searches, contacts without company names, and contacts assigned to each agent — migrates first. We generate a field-level diff comparing the source IDX Broker record to the resulting Nutshell Person record. Your team reviews the diff and confirms the mapping is correct. We adjust field mappings, custom field formats, or owner assignments based on feedback before the full run commits.

  5. Full cutover with delta pickup and audit log

    The full contact migration runs against Nutshell. A delta-pickup window (typically 24–48 hours) captures any new contacts submitted through the IDX Broker website during the cutover. Every migration operation is logged to an audit trail. One-click rollback is available if reconciliation fails. We deliver a post-migration reconciliation report showing record counts, owner assignments, custom field population rates, and any records that failed to import with the reason for each failure.

Platform deep dives

Context on both ends of the pair

IDX Broker logo

IDX Broker

Source

Strengths

  • Dedicated IDX platform with broad MLS board coverage across US regions via standardized data feeds.
  • WordPress plugin and drag-and-drop search builder let non-technical agents configure IDX pages without code.
  • Three pricing tiers ($60-$149/month) offer a clear upgrade path as agent volume grows.
  • API access via middleware.idxbroker.com supports custom integrations and data extraction for migration.
  • G2 reviewers consistently rate the platform positively for ease of use and customizable design options.

Weaknesses

  • Subdomain-based IDX page hosting can dilute SEO equity since search engines index the IDX subdomain rather than the agent's own domain.
  • MLS data access requires paper agreement and board approval, adding friction to initial setup and any provider migration.
  • Limited CRM features beyond lead capture — agents needing pipeline management or transaction tracking will need a separate platform.
  • Lead and contact data export capabilities are not prominently documented, making self-service migration difficult.
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 IDX Broker 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

    IDX Broker: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your IDX Broker 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 IDX Broker to Nutshell data migrations

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

Can't find your answer?

Walk through your IDX Broker to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most IDX Broker to Nutshell migrations complete in 24–48 hours for under 5,000 contact records. The pre-migration steps — custom field creation and owner resolution — typically take 1–3 business days to coordinate. Larger datasets over 20,000 contacts or setups with many saved-search metadata fields extend to 3–5 days. The longest single step is custom field setup in Nutshell before data can be mapped.

Adjacent paths

Related migrations to explore

Ready when you are

Move from IDX Broker.
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