Migrate from BoldTrail to Odoo CRM

BoldTrail contacts map directly to Odoo res.partner records. First name, last name, email, phone, mobile, job title, and address fields migrate as direct field-to-field mappings. BoldTrail's N:N company associations collapse to the primary company link on the partner record, with secondary associations stored via partner_id relations.

BoldTrail company records map to Odoo res.partner with type='company'. Company name becomes partner name, domain becomes website, industry maps via value_mapping to Odoo's selection list, and employee count and annual revenue migrate as integer and monetary fields respectively. Additional fields such as tax ID and shipping address are handled as optional custom fields if present in BoldTrail.

BoldTrail deals migrate as Odoo crm.lead records with type='opportunity'. Deal name becomes crm.lead name, amount maps to expected_revenue, close date maps to date_deadline, and pipeline stage maps to stage_id via a value-mapping table built from Odoo's stage sequence. Any custom deal properties such as listing ID or referral source are mapped to custom fields on crm.lead to preserve context.

BoldTrail pipeline stages map to Odoo crm.stage records by matching the stage name and applying the Odoo stage's sequence number and probability percentage. Each BoldTrail pipeline maps to a separate Odoo sales team, so stage sequences are scoped to team_id.

BoldTrail tags on contacts map to res.partner.category (contact tags) in Odoo. Deal tags map to crm.tag. Tags are resolved by exact name match; tags that do not exist in Odoo are created before the migration run commits any records. If duplicate tags appear with different capitalisation, we normalise them to match Odoo's tag name case-insensitively.

BoldTrail lead_source property maps to Odoo's source_id field on crm.lead. Source values (Website, Referral, MLS, etc.) map to existing Odoo utm.source records by name. New sources are created in Odoo during the migration plan phase. The mapping ensures that Odoo's reporting dashboards reflect the original lead acquisition channels, enabling accurate ROI analysis.

BoldTrail custom property fields on contacts — such as preferred_location, buyer_type, or mortgage_status — require Odoo custom field creation. We create these via an Odoo custom module or Studio before migration runs, matching the field type (char, selection, many2one) to BoldTrail's type definition.

BoldTrail links contacts to MLS listings via listing_id and listing_status properties. Odoo has no native listing object, so we create a custom char field (x_listing_mls_id) on res.partner to store the MLS identifier, and a selection field (x_listing_status) for the listing lifecycle status.

BoldTrail Smart Campaigns do not have a direct Odoo equivalent. We export the campaign definition (triggers, conditions, and action sequence) as a structured JSON document that your Odoo administrator or developer uses as a rebuild reference for Odoo Server Actions and Automated Actions. No campaign logic migrates automatically.

BoldTrail IDX websites and the MLS listing integration are BoldTrail-specific infrastructure with no Odoo CRM equivalent. We do not migrate IDX websites or website configuration. The MLS listing data (listing IDs, addresses, statuses) migrates as contact and deal properties. We recommend documenting the IDX site URLs in a separate spreadsheet for future reference and potential manual integration.

BoldTrail logged activities (calls, emails, notes, SMS) migrate as Odoo mail.activity records attached to the parent res.partner or crm.lead. Activity type maps to Odoo's activity_type_id, date maps to date_deadline, and the note content maps to note. Owner resolves by email match to Odoo res.users.

BoldTrail owner_id on contacts and deals resolves to Odoo res.users by email address match. Unmatched owners are flagged before the migration runs — your team either creates the Odoo user account first or assigns those records to a designated fallback user to avoid orphaned ownership.