Migrate from BrightDoor to Pipedrive

BrightDoor's Visitor record (prospective home buyer who registers at a model home) maps directly to Pipedrive's Person object. Email, name, phone, and address fields map straightforwardly. Visitor-specific properties like registration_source or referral_channel migrate as Pipedrive custom fields. These custom fields are created in Pipedrive prior to migration to ensure no data loss.

BrightDoor records when a visitor first registered at a community. Pipedrive has no native registration-date concept on Person — we create Registration_Date__c as a custom date field on the Person object to preserve this timestamp for follow-up sequencing. The field is populated using the original registration timestamp from BrightDoor's export file, ensuring accurate lead age calculations in Pipedrive.

BrightDoor's Community (master planned development or subdivision) maps to Pipedrive's Organization object. Community name becomes Organization name, and community-level address information maps to the Organization address fields. This is the primary grouping entity in BrightDoor. All related Lots and Deals reference this Organization, providing a unified view of each community's pipeline and performance.

BrightDoor's Lot is a first-class object representing a specific parcel within a Community. Pipedrive has no lot object — each BrightDoor lot becomes a Pipedrive Deal with Lot_ID__c and Community_Name__c custom fields set from the parent BrightDoor lot record. The deal's Organization links to the corresponding Community record.

Where BrightDoor links a visitor's purchase interest to a specific lot, that intent record maps to a Pipedrive Deal. The Deal's Person is the visitor-turned-lead, the Organization is the community, and the lot context lives in custom fields (Lot_ID__c, Lot_Status__c). Stage names require value mapping.

BrightDoor's sales pipeline stages (Prospect, Tour Scheduled, Contract Sent, Under Contract, Closed) map to Pipedrive stage names per pipeline. We map each stage label value-by-value and carry forward stage-entry timestamps as custom datetime fields for reporting continuity. This mapping preserves historical stage progression data, allowing managers to run pipeline reports without re‑creating the original sales process timeline.

BrightDoor's Agent or Builder records represent the sales agent or builder associated with a community or lot. These map to Pipedrive Users by email match. If an agent has no Pipedrive user account, their records are assigned to a designated fallback owner and flagged for admin review.

BrightDoor activity records (calls, meetings, notes, tour interactions) map to Pipedrive Activities and Notes. Original timestamps, activity type, and owner are preserved. Touchscreen-storytelling events that lack a standard Pipedrive activity type migrate as Notes with a custom activity-type label. Custom activity-type labels are defined in Pipedrive's activity type settings prior to migration, ensuring consistent categorization across all imported records.

BrightDoor custom fields (e.g., financing_type, builder_name, HOA_fees, model_home_number) map to Pipedrive custom fields on the corresponding object (Person, Organization, or Deal). Pipedrive custom fields use key-value hashes in the API; we generate the field definitions before migration so target fields exist during import.

BrightDoor's HomeRover live-tour feature and its associated tour requests are not represented in Pipedrive's standard schema. Tour request data (requester name, scheduled time, property address) is preserved as a Note on the relevant Deal or Person record. The scheduling workflow must be rebuilt using Pipedrive Activities or a Calendly integration.