Migrate from BrightDoor to HighLevel

BrightDoor Contacts migrate directly to HighLevel Contacts. HighLevel requires contacts to have an email or phone for import deduplication. BrightDoor contacts without either are flagged for manual review before migration — they will import with a contact record but may not trigger workflow automations in HighLevel.

BrightDoor Companies map to HighLevel Companies. If a BrightDoor Contact has a primary Company association, we create the HighLevel Company first and link the Contact via the Company Name lookup. Contacts without a BrightDoor company association import without a Company link and can be associated manually or via a post-migration workflow.

BrightDoor Deals map to HighLevel Opportunities. The deal name, amount, close date, and owner all migrate directly. The BrightDoor pipeline stage name maps to a HighLevel Opportunity Stage value — if multiple BrightDoor pipelines exist, we create a corresponding pipeline in HighLevel and map stages within each.

BrightDoor stage names (e.g., Prospect, Reserved, Contract Sent, Closed Won) map value-by-value to HighLevel stage names. Stage probabilities and forecast categories are reapplied based on HighLevel's stage configuration defaults — your team can adjust probabilities after migration in Settings > Opportunities > Pipelines.

BrightDoor's real estate-specific contact properties — buyer type, property interest, budget range, community preference, move-in timeline, financing type, referral source, last community toured, last agent note — have no native HighLevel equivalent. We create a HighLevel custom field for each one, preserving the original field label and data type (text, number, pick-list, or date) so reporting continuity is maintained.

BrightDoor company-level custom fields (development name, community type, total lots, available inventory, HOA fee range) carry real estate operational context. We create matching HighLevel custom fields on the Company object and populate them during migration, ensuring inventory and community data is visible alongside company records.

Deal-level BrightDoor custom fields — lot or unit number, model type, upgrade package, concession amount, contingencies — are essential for real estate transaction tracking. We create HighLevel custom fields on the Opportunity object for each one, preserving data type and any pick-list values so your team can report on deal attributes in HighLevel's opportunity views.

BrightDoor activity history (calls, emails, meetings, and notes) migrates as HighLevel Notes. Each note preserves the original timestamp, the recording agent or owner, and the related contact or deal as a link. Activity exports from BrightDoor arrive as a separate Microsoft Excel spreadsheet — we parse the rows and reformat them for HighLevel's Notes import structure.

BrightDoor file attachments on contacts or deals are downloaded and re-uploaded to HighLevel's file storage associated with the corresponding contact or opportunity record. HighLevel's default per-file upload limit applies (25MB). Files without a valid linked contact or opportunity are attached to a default placeholder record and flagged for manual reassignment.

BrightDoor workflows and email sequences tied to buyer registration, follow-up reminders, and lifecycle stage changes have no export or migration path to HighLevel. We provide a structured workflow audit — documenting each BrightDoor trigger, condition, and action — as a reference for rebuilding in HighLevel's Workflow Builder. This audit is delivered as part of the migration plan before data moves.

BrightDoor users (agents, admins) are resolved by email match against HighLevel users. Unmatched owners are flagged before migration — your team either creates HighLevel user accounts for them first or assigns their records to a fallback owner. No record lands in HighLevel without a valid user ID.