Migrate from BoomTown to Odoo CRM

BoomTown leads map directly to Odoo crm.lead records. The Odoo crm.lead model holds both leads and opportunities depending on the type field — we set type='lead' during migration and flag records with a BoomTown_Stage__c custom field for Odoo admin review to identify any stage-assignment logic that may require post-migration adjustment.

BoomTown contacts with an associated company map to res.partner with partner_type='contact'. Contacts without a company land as individual res.partner records. Odoo's res.partner serves as the unified contact and company model — we set parent_id to link to the associated company partner.

BoomTown companies become res.partner records with partner_type='company'. The company name maps to the name field, domain to the website field, and industry to a custom selection field. Odoo's res.partner has no separate Company object — the company-contact hierarchy is handled via parent_id links on individual contacts.

BoomTown deals map to Odoo crm.lead records with type='opportunity'. The deal name becomes the opportunity name, amount maps to Odoo's expected_revenue field, and close date maps to date_deadline. Pipeline and stage values require pre-created Odoo pipeline stages before the migration run.

Each BoomTown pipeline stage name maps to a corresponding Odoo crm.stage entry in the Pipeline. Stage probability percentages are stored on the Odoo stage record. If BoomTown uses a stage not yet defined in Odoo, we flag it for pre-migration stage creation and then apply the value mapping.

BoomTown owner IDs resolve by email match against Odoo res.users records. Unmatched owners are flagged before migration — teams either invite the user to Odoo first or assign their records to a fallback Odoo user. No record lands without a resolved OwnerId in Odoo.

BoomTown engagement events (logged calls, emails, meetings) migrate as Odoo mail.message records attached to the crm.lead. Original timestamps, subject lines, and owner IDs are preserved. Odoo's activity system (next activity date, summary) is set from BoomTown's last engagement date but requires manual Odoo workflow configuration.

BoomTown notes on leads or contacts migrate as Odoo mail.message records with subtype='comment'. The note body maps to the body field with HTML formatting preserved. Internal notes in BoomTown map to Odoo's 'Internal Note' subtype so the visibility stays restricted.

BoomTown file attachments are downloaded from source storage and re-uploaded to Odoo's ir.attachment model linked to the migrated crm.lead or res.partner via res_model and res_id. Each attachment gets associated with the parent Odoo record for traceability. Odoo file size limits apply with a default of 25MB per file, which can be adjusted per your Odoo instance configuration. Inline images embedded in notes are extracted, re-hosted, and URLs updated accordingly.

BoomTown custom properties on leads and contacts require Odoo custom fields to be pre-created via Odoo Studio or Python model definition before migration. We deliver a custom field manifest listing each BoomTown property name, data type, and recommended Odoo field definition so your Odoo admin can pre-create the schema.

BoomTown deal-level custom properties map to custom fields on the crm.lead model where type='opportunity'. Field data types are preserved — pick-lists in BoomTown become Odoo selection fields with manual value mapping. Numeric and date fields migrate directly once the custom field exists in Odoo.

BoomTown workflows, drip campaigns, lead-routing rules, and automated task sequences do not have a migration path to Odoo. Odoo's Automated Actions and Server Actions use a different event-trigger model. We export BoomTown workflow definitions as a rebuild reference document for your Odoo admin or implementation partner.

BoomTown's predictive lead score is stored as a numeric property on leads. Odoo CRM has an optional AI lead scoring module on the Enterprise plan; on Community or Standard, we migrate the numeric score to a custom integer field (lead_score) so the historical value is available even if scoring is rebuilt.

BoomTown links between contacts and deals are represented in Odoo via the contact_ids many2many field on crm.lead (opportunity). We preserve all contact associations against each deal so the full stakeholder picture is intact in Odoo after migration. Each deal record in Odoo retains its complete set of linked contacts, maintaining the relationship graph from the original BoomTown data.