Migrate from BrightDoor to Mailchimp

BrightDoor contacts land as Mailchimp subscribers within a single audience. Email address is the unique key — duplicates detected and flagged before import, ensuring a clean subscriber list. BrightDoor's primary company association maps to a company-name merge field on the subscriber record; secondary company associations are noted in the migration report for manual review if needed.

Mailchimp has no company object. BrightDoor company name, industry, website, and annual revenue collapse to contact-level merge fields (COMPANY, INDUSTRY, WEBSITE, REVENUE). For contacts linked to multiple companies, the most‑recently‑modified company becomes the primary, and any additional company links are recorded in a secondary text field for reference.

BrightDoor's contact status pick-list values (e.g., Prospect, Active Buyer, Closed, Follow-Up) generate Mailchimp tags applied at import. Tags enable segment creation in Mailchimp that mirrors BrightDoor's status-based views without requiring additional merge field logic. Each status value maps to a distinct tag, allowing you to filter contacts instantly by their original lifecycle stage.

BrightDoor pipeline membership or deal association generates a tag on each contact — for example, 'Pipeline: New Home' or 'Pipeline: Move-Up Buyer'. Tags are applied per deal association, not per deal record. Contacts with multiple active deals receive multiple tags.

BrightDoor deal name and amount migrate to Mailchimp merge fields (DEALNAME, DEALAMOUNT) as text values on the contact record. Deal stage maps to a separate tag rather than a merge field, preserving the stage as a segmentable attribute. Owner and close date optionally stored as additional custom fields.

BrightDoor's custom contact properties — such as community interest, lot preference, financing type, or referral source — are evaluated by data type. Text and number properties become text merge fields; date properties become date merge fields; pick-list properties generate both a merge field and a tag for dual segmentation capability.

BrightDoor's SiteTrack data (page visit counts, last visit date, pages visited) has no Mailchimp equivalent. We migrate the most recent visit date and total visit count as text custom fields (LAST_VISIT_DATE, VISIT_COUNT). Full session history is not importable into Mailchimp's contact model.

Mailchimp's built-in subscriber timestamp reflects the import date, not the original BrightDoor create date. We preserve the original create date as a custom datetime merge field (ORIGINAL_CREATE_DATE__c) so campaign recency reporting reflects actual contact history. This field remains static after migration, enabling you to sort or segment contacts based on when they were first added to BrightDoor.

BrightDoor contact attachments (buyer agreements, pre-qualification letters, model-home waivers) have no Mailchimp equivalent. We flag these items in the migration plan as requiring a separate document management solution. Mailchimp's file attachments are campaign-level assets, not contact-level records, so any buyer documents should be stored in a dedicated repository such as Google Drive, Dropbox, or a CRM‑linked document system.

BrightDoor activity history (logged calls, emails, showing appointments) does not migrate. Mailchimp tracks email engagement (opens, clicks) per subscriber — this begins fresh at go-live. We flag BrightDoor activity records in the migration plan as needing review if a full CRM is required downstream.

BrightDoor's contact automation rules (e.g., 'if status changes to Closed, add to Mailchimp sync') do not migrate. Mailchimp Customer Journeys must be rebuilt. We export BrightDoor rule definitions as a structured reference document for your Mailchimp admin to use during rebuild.

BrightDoor property associations tied to contacts (community name, lot number, floor plan type, move-in target) have no Mailchimp native equivalent. We store these as text custom fields (COMMUNITY, LOT_NUMBER, FLOOR_PLAN) on each subscriber record for reference and personalization in email copy.