Migrate from Tubular CRM to Odoo CRM

Tubular Contacts map to Odoo CRM Contacts. We extract Contact name, email, phone, company association, owner, and custom fields from Tubular CSV exports. Because Odoo requires an existing Company record before a Contact's company_id field can be set, we import Companies first, then Contacts, resolving the company_id reference at migration time. If a Tubular Contact has no associated Company, we create a minimal Odoo Company record or attach the Contact to a designated catch-all company based on customer preference during scoping.

Tubular Companies map to Odoo CRM Companies (res.partner records with company_type = company). Company name, address, domain, and custom fields migrate directly. The company domain becomes the Website field on the Odoo partner record. We create all Companies before any Contact insert to satisfy Odoo's partner dependency chain. Duplicate Companies detected by domain match are flagged in a reconciliation report for the customer to resolve.

Tubular Deals map to Odoo CRM Opportunities. Deal name, value, stage assignment, owner, associated Contact, associated Company, and deal-level notes transfer directly. Payment terms from Tubular map to Odoo's payment_term_id on the Opportunity. We resolve the owner to an Odoo User by email match and the associated Contact and Company to their Odoo partner IDs before Opportunity insert. Closed-won and closed-lost status from Tubular map to Odoo's stage configuration, with the probability percentage preserved as a custom field if the customer requires it for reporting.

Tubular's custom pipeline stages (stage names, order, and color) map to Odoo CRM Stage records within the relevant Sales Team. Probability percentages configured per stage in Tubular map to Odoo stage probability values. Stage-specific triggers (Deal Stage Triggers on Enterprise) are documented separately as they require manual rebuild in Odoo Action Rules; we do not migrate them as automation logic.

Tubular Leads (distinct from Contacts in Tubular's data model) map directly to Odoo CRM Leads. Lead source, status, owner, and custom Lead Builder fields transfer. The Lead-to-Contact conversion workflow is a manual step in Odoo post-import; we flag all Tubular Leads with a conversion-ready flag in a dedicated Odoo custom field so the sales team can process conversions in the correct sequence. Any AI-scored lead ratings from Tubular's DNA Credits feature are preserved in a custom field for the customer's admin to reference during conversion.

Tubular Tags applied to Deals and Contacts migrate to Odoo Tags (mail.message.mttag records). Tags stored as flat label arrays in Tubular are matched by name to existing Odoo tags or created as new tag records during migration. Because Odoo's tag model is object-agnostic (tags can apply across multiple object types), we preserve the full tag set with a reference to which object each tag was originally attached to. We flag any tag naming conflicts (e.g., identically named tags on Deals vs Contacts) for customer resolution.

Tubular Tasks linked to Leads and Deals map to Odoo CRM Tasks (crm.activity records). Task title, due date, owner, completion status, and description transfer. Recurring task patterns do not have an export equivalent in Tubular and are flagged as a manual rebuild item in Odoo. Incomplete tasks are imported as open Odoo activities; completed tasks import with their completion date preserved. Owner resolution uses email matching to Odoo Users.

Tubular email logs, call logs, and notes attached to Deals and Contacts migrate as Odoo CRM activities. Email subject and body transfer as a Note activity on the Odoo Opportunity or Lead. Call logs transfer as Call activities with duration preserved. Because Tubular's activity export format varies between UI CSV and API (Enterprise), we normalize the output into Odoo's activity schema before import, mapping the original activity timestamp to the Odoo activity's date field.

Tubular Owner records map to Odoo Users by email address match. We extract every distinct owner referenced across Contacts, Companies, Deals, and Leads. Owners without a matching Odoo User are placed in a reconciliation queue for the customer's admin to provision before record import resumes. The customer's admin decides whether inactive Tubular owners become inactive Odoo users or are reassigned to active users during migration.

Files attached within Tubular deal flows are extracted via UI scraping or API where available. We preserve file names and link them to the correct Odoo Opportunity or Lead record via ir.attachment records. The file binary content transfers where extractable; files stored in Tubular's hosted attachment system with no direct download URL are flagged for manual download before migration cutoff.

Tubular generates MoM/QoQ reports, Lead Source reports, and Task reports that are view-only with no export endpoint. These cannot be programmatically extracted. We advise customers to screenshot or manually export any critical reports before migration cutoff. In Odoo, we recreate the equivalent report logic using Odoo's reporting views and CSV export capability on the migrated data, but historical data points embedded in Tubular's reports do not transfer.

DNA Credits power Tubular's AI enrichment features, which assign lead ratings and enriched company profiles. These credits have no Odoo equivalent and do not transfer. We document the credit count and any enriched data (AI-scored lead ratings, enriched company profiles) generated by Tubular before migration, and we store that data as custom fields on the migrated Lead or Contact records so the enrichment signal is not lost when credits are exhausted in the old platform.