Migrate from Tango CRM to Odoo CRM

Tango CRM Contact records migrate to Odoo crm.lead with type='lead' to preserve the unqualified prospect status. Standard fields (name, email, phone, address) map to Odoo's partner_name, email_from, phone, and street/city/country fields. Since Odoo's crm.lead model uses a partner_id linked to res.partner rather than embedding contact fields directly, we create a res.partner record for each Contact first, then link the crm.lead. The email address serves as the merge key. Custom Contact properties map to custom fields on crm.lead that we pre-create via ir.model.fields before migration.

Tango CRM Company records map to Odoo res.partner with is_company=True. Industry, size, website, and address fields translate to Odoo's industry_id, company_size, website, and address fields respectively. We create Company records before Contact records so that Contact imports can resolve the parent partner_id at insert time. If a Tango Contact has an associated Company, we link via partner_id on the Odoo Contact (crm.lead with type='lead'). Custom Company properties require explicit field-level mapping to pre-created Odoo custom fields.

Tango CRM Deal records migrate to Odoo crm.lead with type='opportunity'. Deal name maps to Odoo's name field, deal value maps to planned_revenue, expected close date maps to date_deadline, and owner maps to user_id by email-matching against Odoo res.users. The Tango pipeline stage name is preserved in a custom field tango_stage_name__c on the Odoo crm.lead so the customer can remap to Odoo stage labels post-migration. Stage probability percentages migrate as a reference note in the migration worksheet.

Tango CRM Pipeline definitions (stage order, stage labels) migrate as Odoo crm.stage records ordered by sequence. Each pipeline in Tango becomes a crm.team (sales team) in Odoo with its own stage sequence. We pre-create the stage structure in the destination Odoo database before Deal migration begins so that Opportunity records reference valid stage_id values at insert time. Stage automation hooks (auto-assignment, auto-close) are flagged as configuration items requiring rebuild in Odoo's server actions.

Tango CRM Activities (calls, emails, meetings, tasks) migrate to Odoo mail.activity records linked to the parent crm.lead via res_id and model='crm.lead'. Activity type maps to Odoo's activity_type_id, summary maps to note, and date maps to date_deadline. Without a confirmed Tango API, large activity volumes require CSV export confirmation or browser-based extraction; we flag activity record counts during scoping. Activity history volume above 50,000 records may require batch chunking and multiple import passes to avoid Odoo session timeouts.

Tango CRM Notes attached to Contacts or Deals migrate to Odoo mail.message records with message_type='comment', linked to the parent crm.lead via res_id and model='crm.lead'. Note body text migrates as the message body. HTML-formatted notes are stripped to plain text unless the destination Odoo instance has rich-text messaging enabled. Notes without a parent record are linked to the corresponding res.partner if the note references a contact.

Tango CRM Tags applied to Contacts or Deals migrate to Odoo crm.tag records. Each distinct tag value becomes a crm.tag entry with a generated name and color. On the crm.lead, tags migrate as crm.lead.tag.rel many2many records. Multi-select tag fields from Tango are split into individual tag values during the transformation step and consolidated into Odoo's tag association table.

Tango CRM custom properties on Contacts, Companies, and Deals require explicit field-level mapping to Odoo ir.model.fields records created before migration. Field types (dropdown, date, number, text) map to Odoo field types (selection, date, float, char/text). Dropdown fields need explicit value translation from Tango option labels to Odoo selection key-value pairs. Custom field creation requires the destination Odoo database's technical settings access; we coordinate with the customer's Odoo admin during the schema design phase.

Tango CRM Owners referenced on Contact, Company, and Deal records resolve by email match against Odoo res.users. We extract every distinct owner email from the source data during discovery and cross-reference against the destination Odoo user roster. Any owner without a matching Odoo user goes to a reconciliation queue; the customer's Odoo admin provisions the missing user before record migration resumes. Owner role and permission sets do not transfer and are rebuilt in Odoo post-migration.

File attachments stored within Tango CRM records (uploaded documents, signed contracts, images) cannot be extracted without a confirmed API endpoint or download mechanism. We do not migrate attachments to avoid silent data loss. We document the attachment count and record association during scoping and deliver a post-migration checklist itemizing attachments for manual re-upload to the corresponding Odoo crm.lead or res.partner records.

Tango CRM pipeline stage labels (e.g., Qualified, Proposal Sent, Negotiation) do not map 1:1 to Odoo crm.stage names. We preserve the original Tango stage label in a custom field on each Opportunity record during migration and deliver a stage mapping worksheet that lists each Tango stage alongside the Odoo stage_id the customer should assign. Stage order and probability percentages migrate as reference data in the mapping worksheet for the customer's Odoo admin to configure in the Pipeline settings UI.

Tango CRM Deal values migrate to Odoo crm.lead.planned_revenue. If Tango stores currency as a text field (e.g., 'USD', 'EUR'), we resolve it to the corresponding res.currency record in Odoo and store the currency_id on the crm.lead. If the Tango instance stores numeric values without currency context, we default to the Odoo database's default company currency and flag this assumption in the mapping worksheet for confirmation.