CRM migration
Field-level mapping, validation, and rollback between BrightDoor and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
BrightDoor
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between BrightDoor and Nutshell.
Complexity
BStandard
Timeline
3–5 days
Overview
BrightDoor was built specifically for residential builders, developers, and brokerages — it tracks homes, lots, communities, and buyer registrations alongside standard CRM objects. Nutshell uses a conventional People/Companies/Leads/Deals model without native real estate concepts. The migration challenge is threefold: first, translating BrightDoor's property-community-registration data into Nutshell's custom fields and associations; second, mapping BrightDoor agent records to Nutshell People with role designations; third, preserving the activity timeline (calls, emails, meetings, notes) with original timestamps and owner attribution. We extract BrightDoor data via its API using scoped read access, stage it with field-level transformation, then load into Nutshell via its JSON-RPC API. Custom fields are provisioned in Nutshell before the first record lands, and each record's original create date, owner assignment, and activity timestamp are transferred to preserve audit continuity. During staging, value mappings align BrightDoor's phase-based pipeline stages with Nutshell's global pipeline stages, and agent roles are stored in a custom pick-list field on the Person record. After the initial load, a delta‑pickup window captures any records created or modified in BrightDoor while the cutover is in progress. Automation rules, buyer portal configurations, and community‑specific workflows cannot migrate because they are platform‑specific; we export their definitions as a structured rebuild reference for your Nutshell admin.
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 BrightDoor 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.
BrightDoor
Person / Contact (Buyer)
Nutshell
Person
1:1BrightDoor buyers map directly to Nutshell People. Name, email, phone, address, and custom buyer-profile fields migrate as standard and custom Person fields. Owner assignment resolves by email match to a Nutshell user — unmatched owners flag before the full run.
BrightDoor
Person / Contact (Agent)
Nutshell
Person
1:1BrightDoor agent records map to Nutshell People with a custom Agent_Role__c pick‑list field that records the agent’s role (Listing Agent, Buyer Agent, Closing Coordinator, etc.). The license number, brokerage affiliation, and contact method are stored in custom fields on the Person record. During migration, license numbers are validated for format and missing values are flagged for manual review. Agents without a buyer association are created as isolated Nutshell People records.
BrightDoor
Company / Brokerage
Nutshell
Company
1:1BrightDoor company records (brokerages, developer entities, builder firms) map to Nutshell Companies. Company name, address, website, and industry classification migrate as standard Company fields. Multi-office brokerages may create multiple Company records with a custom Parent_Company__c field if Nutshell's plan supports hierarchy.
BrightDoor
Lead (Prospect Buyer)
Nutshell
Lead
1:1BrightDoor leads representing early-stage prospects map to Nutshell Leads. Lead source, status, and interest-level fields migrate as standard Lead fields or custom fields depending on Nutshell plan tier. BrightDoor's lead-stage progression (Inquiry → Tour → Registration) translates to a custom pick-list field in Nutshell.
BrightDoor
Deal (Sale / Lot Contract)
Nutshell
Deal
1:1BrightDoor deals (lot contracts, home sales) map to Nutshell Deals. Deal name, amount, stage, close date, and owner migrate as standard Deal fields. BrightDoor's phase-based stages (e.g., Under Contract, Contingent, Closing) require value-mapping to Nutshell's pipeline stages since Nutshell stages are global across the single pipeline.
BrightDoor
Community / Subdivision
Nutshell
Company or Custom Object
1:1BrightDoor's community and subdivision records have no direct Nutshell equivalent. We create a Community_Name__c custom field on the Deal object and map community associations as field values. For teams with heavy community reporting, we propose a custom Communities__c object in Nutshell Enterprise.
BrightDoor
Lot / Unit Inventory
Nutshell
Custom Field on Deal
1:1BrightDoor lot or unit tracking migrates as custom fields on the Nutshell Deal: Lot_Number__c, Unit_Address__c, HOA_Fee__c, and Community_Name__c. Lot status (Available, Under Contract, Sold) becomes a custom pick-list value that maps to the Deal stage. Additional fields such as Lot_Size__c and Zoning__c are created if present in BrightDoor, preserving all property details. The lot status field also retains the original BrightDoor status timestamp, enabling historical analysis of inventory progression.
BrightDoor
Registration / Buyer Profile
Nutshell
Custom Field Group on Person
many:1BrightDoor's buyer registration data (pre-qualification status, financing type, trade partner, closing coordinator) merges into a group of custom fields on the Nutshell Person record. Registration date and event source (portal, show, event) migrate as custom datetime and pick-list fields. The pre-qualification status captures the buyer’s financial readiness, and financing type records the loan product selected. Trade partner and closing coordinator details are preserved as custom contact reference fields.
BrightDoor
Activity (Call, Email, Meeting, Note)
Nutshell
Task / Event / Note
1:1BrightDoor activity logs map to Nutshell Tasks (calls, emails) and Events (meetings). Notes map to Nutshell Notes. Original timestamps, owner attribution, and parent record links (person, deal, or company) are preserved. Nutshell's activity log keeps the full context for handoff conversations.
BrightDoor
Custom Field (object-level)
Nutshell
Custom Field
1:1BrightDoor custom fields on People, Companies, Leads, and Deals create corresponding custom fields in Nutshell before migration begins. Field types (text, number, pick-list, date, currency) are translated to Nutshell equivalents. Multi-select pick-lists in BrightDoor map to Nutshell's choice-based custom fields.
BrightDoor
Attachment / Document
Nutshell
File
1:1BrightDoor file attachments (floor plans, community brochures, contract PDFs) are downloaded and re-uploaded to Nutshell Files, linked to the parent Person, Company, or Deal record. File size limits follow Nutshell's plan limits. During migration, file metadata including creation date and uploader identity are preserved. If a file exceeds Nutshell's size allowance, we split the upload or store a reference link in the record. All attachments retain their original file names.
BrightDoor
Buyer Portal Configuration
Nutshell
Not Migrated
1:1BrightDoor's buyer portal, HomeRover tour scheduling, and community-specific portal settings are platform-native and cannot migrate. We export portal configuration settings as a structured PDF so your Nutshell admin can evaluate which features to rebuild using Nutshell's engagement tools or third-party integrations.
| BrightDoor | Nutshell | Compatibility | |
|---|---|---|---|
| Person / Contact (Buyer) | Person1:1 | Fully supported | |
| Person / Contact (Agent) | Person1:1 | Fully supported | |
| Company / Brokerage | Company1:1 | Fully supported | |
| Lead (Prospect Buyer) | Lead1:1 | Fully supported | |
| Deal (Sale / Lot Contract) | Deal1:1 | Fully supported | |
| Community / Subdivision | Company or Custom Object1:1 | Fully supported | |
| Lot / Unit Inventory | Custom Field on Deal1:1 | Fully supported | |
| Registration / Buyer Profile | Custom Field Group on Personmany:1 | Fully supported | |
| Activity (Call, Email, Meeting, Note) | Task / Event / Note1:1 | Fully supported | |
| Custom Field (object-level) | Custom Field1:1 | Fully supported | |
| Attachment / Document | File1:1 | Fully supported | |
| Buyer Portal Configuration | Not Migrated1: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.
BrightDoor gotchas
mybrightdoor.com serves two different businesses
No publicly documented API for data export
Activity history not exportable via standard tools
HomeRover tour data isolated from CRM 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
Audit BrightDoor schema and plan Nutshell custom fields
We read every BrightDoor object accessible via API — People, Companies, Leads, Deals, Activities, and custom fields — and produce a schema inventory. For each custom field, we propose a Nutshell equivalent: standard field match, custom field creation, or custom object. We also map BrightDoor's pipeline structure to Nutshell's pipeline stages and identify where multiple BrightDoor pipelines need consolidation or custom-field simulation. This inventory is the basis for the custom field creation checklist your Nutshell admin completes before data lands.
Resolve owner and agent assignments by email
BrightDoor owner IDs and agent records are matched to Nutshell users by email address. If a BrightDoor owner has no corresponding Nutshell user, the record lands with a fallback owner (designated by your team) and the original owner email is stored in a custom field for post-migration re-assignment. We flag unmatched owners in the sample migration report so your team can either invite them to Nutshell or confirm the fallback rule.
Run sample migration with field-level diff
A representative slice of 100–300 records migrates first — spanning buyers, agents, companies, leads, deals, and activities across your BrightDoor communities. We generate a field-level diff comparing source values to destination values so you can verify stage mapping, custom field population, owner resolution, and activity attribution before the full run commits. This is the last checkpoint to adjust value mappings or flag missing pick-list options in Nutshell.
Execute full migration with delta-pickup window
The full migration runs against Nutshell's JSON-RPC API with batched inserts. After the initial load completes, a 24–48 hour delta-pickup window captures any BrightDoor records created or modified during the cutover period. All operations are logged to an audit trail. One-click rollback is available if reconciliation identifies missing records or data integrity issues — FlitStack rolls back the Nutshell load without touching BrightDoor, which remains live and read-accessed throughout.
Deliver rebuild reference for buyer portal and automations
Alongside the migrated data, we deliver a structured export of BrightDoor's automation rules, pipeline phase definitions, buyer portal field structures, and HomeRover configuration summaries. The export is provided as a PDF and CSV package, detailing each rule's trigger, conditions, actions, and any associated custom field references. This document is formatted for your Nutshell admin or implementation partner to use as a rebuild specification for Nutshell sequences, workflow rules, and any buyer-facing forms your team chooses to implement post-migration.
Platform deep dives
BrightDoor
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 BrightDoor and Nutshell.
Object compatibility
2 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
BrightDoor: Not publicly documented.
Data volume sensitivity
BrightDoor 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 BrightDoor to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your BrightDoor 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 BrightDoor
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.