Migrate from TeamWave to Odoo CRM

TeamWave Contacts with lifecycle stage indicating a qualified prospect or customer (Stage = Customer, Evangelist, or other post-sale state) map to Odoo res.partner. Contacts with lifecycle stage = Lead, Subscriber, or Marketing Qualified map to Odoo crm.lead. We compute the split using TeamWave's lifecycle_stage export field, create crm.lead records for unqualified prospects and res.partner records for qualified contacts, and preserve the original TeamWave lifecycle stage as a custom Char field tw_original_lifecycle__c on both record types for audit.

TeamWave Company records map to Odoo res.partner with is_company = True. The company name, domain, website, and address fields migrate directly. We create the Company partner record before any Contact import so that the child_contact.parent_id foreign key is satisfied at insert time. TeamWave's company_id foreign key on Contact is preserved as a cross-reference column in the migration manifest.

TeamWave Deals map to Odoo crm.lead records. The dealstage property maps to crm.lead stage_id (a Many2one to crm.stage). Pipeline assignment maps to crm.lead.team_id, which we pre-create in Odoo during schema setup. Deal value maps to crm.lead.planned_revenue, and expected close date maps to crm.lead.date_deadline. Closed-Won and Closed-Lost reasons from custom TeamWave fields become crm.lead.lost_reason if the Odoo version supports it, or a custom Char field tw_lost_reason__c.

TeamWave pipeline stages are extracted from the Deal export and mapped to crm.stage records within the target CRM team. We configure stage names, sequence order, and probability percentages (probability field) in Odoo before Deals are loaded. For Odoo versions 14 and above, the kanban_color field on stage is also migrated if TeamWave uses pipeline color coding.

TeamWave Project records do not map to Odoo CRM objects; they belong to the Odoo Project app, which is a separate installation and licensing scope. We transfer project records as a structured manifest (project name, client association, start/end dates, status, and description) for the customer's Odoo administrator to create project.project records post-migration. The TeamWave project_id foreign key on Task is preserved in the manifest for reassignment in Odoo Project.

TeamWave Tasks linked to Projects map to Odoo project.task records. Tasks linked to Contacts or Deals without a Project map to crm.lead activity records (crm.activity) or project.task with project_id left null, depending on the customer's Odoo setup. Assignee (hubspot_owner_id equivalent) resolves via email match to res.users.

TeamWave User records (name, email, role, department) map to Odoo res.users. We match by email address during migration. Any TeamWave Owner referenced on a Deal or Contact without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before the import resumes. Active/inactive status in TeamWave maps to Odoo active = True/False.

TeamWave Calendar Events (event title, date/time, linked entity type and ID, attendees) map to Odoo calendar.event records. We resolve the linked entity reference (Deal, Project, or Contact) to the migrated Odoo crm.lead.id or res.partner.id and set calendar.event.res_id and res_model accordingly. Attendees migrate as calendar.attendee records linked to the event.

TeamWave employee records map to Odoo hr.employee if the Odoo HR app is installed, or to res.partner records with internal = True if only CRM is deployed. Name, role, department, and contact information migrate directly. If the customer runs TeamWave HR alongside CRM and moves only CRM to Odoo, we recommend a separate HR migration engagement for the Odoo HR app scope.

TeamWave custom fields on Contacts and Deals are exported alongside standard fields. We create matching custom fields in Odoo via the Settings > Technical > Custom Fields interface (or programmatically via XML data migration) before loading data. Char, Integer, Float, Date, and Selection field types migrate directly; multi-select and complex custom field types require case-by-case review during scoping.

TeamWave stores attachments linked to Contacts, Deals, and Projects but provides no bulk download mechanism. We extract attachment metadata (filename, size, linked object type, and TeamWave record ID) and produce a re-upload manifest. The customer manually downloads from TeamWave and re-uploads to Odoo ir.attachment records linked to the migrated res.partner or crm.lead. Binary attachment files do not migrate programmatically.

TeamWave tags on Contacts and Deals migrate to Odoo crm.tag records via crm.lead.tag_ids (many2many). Tags used for content classification or project categorization are separated from CRM tags and listed in the project-structure manifest for Odoo Project tag configuration.