Migrate from BrightDoor to Odoo CRM

BrightDoor registrants map directly to Odoo crm.lead records. The registrant name becomes the lead's display name (partner_name field); email, phone, and address map to standard contact fields on the lead. Original registration date is preserved as x_studio_registration_date for reporting continuity.

BrightDoor registrants who have progressed to 'Buyer' lifecycle stage map to res.partner (Odoo's contact record) since they represent a contracted customer. The crm.lead is marked as 'won' before creation of the partner record, maintaining the lead history trail and preserving the complete lifecycle progression for reporting purposes.

BrightDoor communities map to Odoo sales teams (crm.team). Each community becomes its own sales team so stage pipelines, team-specific users, and community-level reporting can be scoped correctly in Odoo. Team members are assigned by email match against Odoo users, ensuring proper lead ownership and visibility across the organization.

BrightDoor's registrant-to-community association migrates as a tag on crm.lead (e.g., 'Community: Cedar Ridge'). Odoo tags are many2many, allowing registrants assigned to multiple communities to receive multiple tags for comprehensive tracking. Tag names preserve the community code from BrightDoor for accurate reporting segmentation.

BrightDoor lot numbers have no native Odoo equivalent. FlitStack creates x_studio_lot_number (Char) on crm.lead during migration setup. Lot availability status (available, under contract, sold) can map to a second custom selection field x_studio_lot_status for complete property tracking within the lead record.

BrightDoor stores design-center selections (e.g., kitchen package, elevation type) as registrant properties. These migrate to Odoo custom selection fields on crm.lead (x_studio_design_package, x_studio_elevation_type). Options with free-text values become Char fields for maximum flexibility in data capture.

BrightDoor tour requests map to Odoo calendar.event records attached to the crm.lead. Original visit date, host user, and community are preserved in the event record. Events are created as 'Tour' type with a custom description field carrying BrightDoor's complete tour metadata for reference.

BrightDoor activity history (call logs, follow-up reminders) migrates as mail.message records on the crm.lead. Odoo displays these in the lead's chatter for unified communication tracking. Timestamps and assigned user are preserved accurately; unassigned activities map to a fallback Odoo user flagged during owner resolution.

Any BrightDoor custom registrant properties not covered by standard mapping receive corresponding Odoo custom fields. FlitStack creates Char fields for text values and Selection fields for pick-list values to maintain data integrity. Field definitions are generated as a comprehensive setup manifest before migration runs.

BrightDoor owner IDs resolve to Odoo res.users by matching email addresses. Unmatched owners are flagged before migration begins to prevent data loss; records are assigned to a fallback user or placed in an unassigned queue for manual review. This prevents orphan records in Odoo post-migration.

BrightDoor file attachments on registrants migrate to Odoo's ir.attachment model, linked to the corresponding crm.lead record. File metadata including filename, create_date, and create_uid is preserved throughout the transfer. Large files are handled within Odoo's configured attachment size limits to ensure system stability.

BrightDoor automations including lifecycle transition triggers, community assignment rules, and email sequences do not migrate directly. FlitStack exports workflow definitions as a JSON reference file for Odoo admin review and planning. Odoo Automations are rebuilt using Studio or server actions targeting the migrated crm.lead model and custom fields.