CRM migration
Field-level mapping, validation, and rollback between IDX Broker and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
IDX Broker
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between IDX Broker and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
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.
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 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)
Nutshell
Person
1:1IDX 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
Nutshell
Custom field on Person
1:1IDX 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
Nutshell
Custom field on Person
1:1IDX 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
Nutshell
Person source field
1:1IDX 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)
Nutshell
Company
many:1Some 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
Nutshell
Nutshell User
1:1IDX 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
Nutshell
Custom datetime field on Person
1:1Nutshell'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
Nutshell
Custom datetime field on Person
1:1Modified 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)
Nutshell
No equivalent in Nutshell
1:1IDX 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
Nutshell
Person notes or custom field
1:1Free-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.
| IDX Broker | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (Website Lead) | Person1:1 | Fully supported | |
| Saved Search | Custom field on Person1:1 | Fully supported | |
| Property Interest / Listing View | Custom field on Person1:1 | Fully supported | |
| Lead Source Attribution | Person source field1:1 | Fully supported | |
| Company Name (if present) | Companymany:1 | Fully supported | |
| IDX Broker User / Agent Account | Nutshell User1:1 | Fully supported | |
| Contact Creation Timestamp | Custom datetime field on Person1:1 | Fully supported | |
| Contact Modified Timestamp | Custom datetime field on Person1:1 | Fully supported | |
| MLS Listing Data (display data) | No equivalent in Nutshell1:1 | Fully supported | |
| IDX Broker Lead Form Submissions | Person notes or custom field1: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.
IDX Broker gotchas
Subdomain-based IDX page hosting affects SEO
MLS board approval requires paper agreements before data access
Wrapper-page system causes theme conflicts
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
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.
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.
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.
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.
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
IDX Broker
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 IDX Broker and Nutshell.
Object compatibility
1 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
IDX Broker: Not publicly documented.
Data volume sensitivity
IDX Broker 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 IDX Broker to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave IDX Broker
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.