Migrate from Teamgate to Odoo CRM

Teamgate People records with no Deal association and no conversion history map to Odoo CRM Lead. People with active Deals or a completed stage progression map to Odoo CRM Contact. We compute the split during migration using Teamgate's deal association count and stage history. Odoo Lead converts to Contact linked to a Partner (the Odoo company/contact record), and Contact can also attach directly to Partner. We preserve the original Teamgate created_at timestamp in a custom field teamgate_created_at__c on both Lead and Contact for audit trail integrity.

Teamgate Company records map 1:1 to Odoo CRM Partner records with company_type = 'company'. The Odoo Partner object serves dual roles (as an account/company and as a contact holder), so we map Teamgate Company name to Partner name and Company domain to Partner website. Company address data maps to Partner address fields (street, city, country). Partner must be created before any Contact import that references it as parent.

Teamgate Deals map directly to Odoo CRM Opportunity (crm.lead). The deal value, expected close date, loss reason, and owner assignment migrate as Opportunity expected_revenue, date_deadline, lost_reason, and user_id. Pipeline assignment from Teamgate maps to Odoo's crm_case_section (sales team/pipeline) field. We resolve the section ID during migration using a name-match lookup against Odoo's configured pipelines.

Each Teamgate Pipeline's ordered Stages become Odoo CRM Stage records within a crm_case_section. Stage name, sequence order, and probability percentage migrate. Odoo's stage probability is stored as a float (0.0-1.0) rather than an integer percentage. We also map win/loss stage flags: Teamgate's closed-won stage maps to Odoo's won_state, and closed-lost maps to lost_state. Stages are configured in Odoo via Settings > CRM > Pipelines > Stages before data import begins.

Teamgate's named Pipelines map to Odoo's CRM Case Sections (sales teams), which define the pipeline context for Opportunities and control team-level assignment rules, alias emails, and shared planning. We export each Teamgate pipeline name and recreate it as an Odoo Section with the same sequence order. Multi-pipeline teams in Teamgate Enterprise map cleanly to multiple Odoo Sections.

Teamgate custom fields on People (text, number, date, dropdown, checkbox) map to Odoo custom fields on the Lead and Contact models. Text fields map to char or text depending on length; number to float or integer; date to date; dropdown to selection; checkbox to boolean. We pre-create the Odoo custom fields via XML or Studio before any data import. Dropdown values are created as selection options matching the Teamgate allowed values.

Teamgate custom fields on Deals map to Odoo custom fields on crm.lead (the Opportunity model). The same type-mapping logic applies as for People. Loss reason dropdown values from Teamgate migrate as selection options in Odoo's lost_reason field if the standard field is used, or to a custom field if the customer uses a custom loss reason schema.

Teamgate tags (flat string labels on People, Companies, and Deals) map to Odoo CRM Tags. Odoo stores tags as a many2many relation on the crm.lead model (the Tag model is shared across CRM and other apps). We export tags as a normalized set per record and create Odoo CRM Tag records during migration, then link via crm.tag.rel. Teams migrating from Teamgate Starter retain tag functionality in Odoo without tier restriction.

Teamgate Activities (calls, emails, meetings, tasks) tied to People or Deals migrate to Odoo CRM Activities linked to the corresponding Lead, Contact, Partner, or Opportunity. Odoo uses the mail.activity model with type区分 (call, email, meeting, to_do). Activity body, timestamp, and duration transfer. The original Teamgate created_at timestamp is preserved in Odoo's create_date. We link activities to the resolved Odoo record (Lead or Opportunity) using the external ID we assigned during record creation.

Teamgate Owner records map to Odoo CRM Salesperson Users. We match by email address during migration. Owners without a matching Odoo User are held in a reconciliation queue; the customer's Odoo admin provisions the missing Users (and optionally activates them as Teamgate owners) before record import resumes. Inactive Odoo Users can own records if the Use Record Locking setting allows it.

Teamgate file attachments (stored under the account's storage tier) are exported as binary files via the Teamgate API. We download files, rename them with the target Odoo record's model and ID reference, and re-upload to Odoo as ir.attachment records linked to the corresponding Lead, Contact, Partner, or Opportunity. Storage tier limits on the source side are scoped during discovery; files exceeding the source tier are flagged for selective migration or tier upgrade before export begins.

Teamgate loss reasons are a dropdown tied to Deals. We export all active loss reason values and map them to Odoo CRM's lost_reason selection field on crm.lead. New values are created as selection options during the Odoo custom field schema phase. Loss reason assignment migrates with the Deal-to-Opportunity record.