Migrate from Breakcold to Odoo CRM

Breakcold Contacts with lifecycle stage of prospect or unqualified lead map to Odoo CRM Lead. Contacts with lifecycle stage of qualified lead, customer, or evangelist map to Odoo CRM Contact tied to a Partner record. The original Breakcold lifecycle stage is preserved as a custom field (x_breakcold_lifecycle__c) on both the Lead and Contact for audit and reporting continuity. We apply the split at migration time using Breakcold's lifecycle_stage property.

Breakcold's distinct Lead object (separate from Contact) maps directly to Odoo CRM Lead. Lead status, source attribution, and any lead scoring value from Breakcold migrate as custom fields on the Odoo Lead. Owner assignment (Breakcold user) maps to Odoo CRM Salesperson (user) by email match.

Breakcold Company records map to Odoo CRM Partner records. The Breakcold company domain becomes the Partner's website field and serves as the deduplication key during import. Partner records are created before any Lead or Contact import so that the contact-company relationship (Breakcold's contact-company link) is satisfied at the moment of Contact insert. Industry, company size, and custom Properties translate to Odoo Partner custom fields or tags.

Breakcold Pipelines map to Odoo CRM Sales Teams. Each Breakcold pipeline name becomes an Odoo Sales Team with its own member assignment and pipeline visibility. Odoo supports multiple Sales Teams, matching Breakcold's unlimited pipeline model. We preserve pipeline ordering and color metadata from Breakcold as custom fields or tags on the Odoo team.

Breakcold Pipeline Stages map to Odoo CRM Stage records within each Sales Team. Stage name, order, and probability percentage migrate from Breakcold to Odoo stage probability. Breakcold's custom stage colors are preserved as stage description or a custom field. Odoo's stage Lost/Won flags are set based on Breakcold stage type if the source pipeline includes terminal stages.

Breakcold Activities across all channels (Email, LinkedIn, WhatsApp, Telegram, Call) map to Odoo mail.message records for email and internal messaging, and to crm.phonecall for call records. Channel metadata (the source channel) is preserved in a custom field x_channel__c on the Odoo message. Activity body content, timestamp, and author map directly. LinkedIn-specific metadata (profile URL, connection date) migrates to Contact custom fields rather than as Odoo messages. Note: Odoo does not have a native multichannel inbox equivalent to Breakcold's unified social inbox; channel context is preserved as data but the unified thread view requires Odoo Discuss configuration or a third-party integration.

Breakcold unlimited custom Objects map to Odoo custom models created via developer access or Odoo Studio. We pre-create the destination schema including model name, fields, field types, and any lookup relationships to standard models (Contact, Partner, Lead). Text, number, date, boolean, and multi-select field types translate directly. Multi-select values serialize as comma-separated strings in Odoo char fields unless the customer has developer access to create proper many2many or selection fields. Custom Object data imports after the parent Contact and Company records are in place.

Breakcold custom Properties on standard objects migrate to Odoo CRM custom fields. We create fields via Odoo Studio (if available in the customer's Odoo edition) or via XML data migration. Field types translate: text to char or text, number to float or integer, date to date, boolean to boolean, multi-select to char with serialized values. Required fields in Breakcold may need to be set as optional in Odoo during initial load to avoid rejection on incomplete records.

Breakcold's LinkedIn integration data—profile URL, connection date, post engagement data, Sales Navigator prospects—stores as Contact properties in Breakcold. These migrate as Odoo Contact custom fields: x_linkedin_url (char), x_linkedin_connected_date (date), x_linkedin_posts_engaged (integer). The raw scraped LinkedIn metadata (profile fields beyond URL) is flag-stamped as stale or fresh during migration scoping based on the last confirmed sync date. Stale LinkedIn data is migrated as-is with a note for the customer to re-enrich post-migration if needed.

Breakcold flat string tags on Contacts and Leads map to Odoo CRM tags on the Lead or Contact record. Odoo's mail.thread tag system supports multiple tags per record. We apply tags at migration time by resolving the tag name against Odoo's tag vocabulary, creating any missing tags in the destination. Tags used for content classification (rather than lead routing) map to Odoo CRM tags with no structural transformation.

File attachments on Breakcold Contact records and Activities migrate as Odoo IrAttachment records linked to the corresponding Lead, Contact, or Partner via res_model and res_id. Attachments are downloaded from Breakcold (if accessible via API) and uploaded to Odoo's filestore during migration. We do not guarantee attachment rendering fidelity in Odoo since Breakcold and Odoo use different attachment storage backends.

Breakcold workspace Users and their role assignments (Admin, Member) map to Odoo CRM User records by email match. Owner assignment on Breakcold Contacts and Leads maps to Odoo CRM Salesperson (user_id field) during migration. Any Breakcold Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission parity is documented but not enforced during migration since Odoo access rights require separate configuration.