Migrate from Teamwork CRM to Odoo CRM

Teamwork CRM Contacts map to Odoo Partner records with is_company=False. The Partner record inherits the contact name, email, phone, and address fields directly. We resolve the parent Company by matching the Teamwork Contact's companyId against the previously migrated Company Partner with is_company=True, then set parent_id on the Contact Partner. Tag names from Teamwork migrate to critical field on the Partner record. Active/inactive status maps to active boolean in Odoo.

Teamwork CRM Companies map to Odoo Partner records with is_company=True. We migrate company name, domain/website, industry, phone, address, and any custom Company fields as Odoo Partner fields or pre-created custom fields on res.partner. Companies are loaded first in the migration sequence so that parent_id references on Contact Partner records are satisfied at the time of Contact insert.

Teamwork CRM Leads map directly to Odoo crm.lead records. The Teamwork Lead's stage name, probability weight, assigned owner (mapped to Odoo res.users by email), and any custom Lead fields migrate. We preserve lead source and lead score if the customer has those fields configured. The Teamwork Leads pipeline becomes an Odoo Sales Team with a dedicated stage sequence. If the customer runs separate Leads and Opportunities pipelines simultaneously, we map each to its own Sales Team in Odoo.

Teamwork CRM Opportunities are distinct records in a separate pipeline from Leads. In Odoo, Opportunities are crm.lead records at an advanced pipeline stage rather than a separate object type. We map each Teamwork Opportunity to a crm.lead record in the corresponding Odoo Sales Team pipeline, preserving the deal name, monetary value, probability, close date, and stage label. The stage-to-Sales-Team mapping is defined during scoping so that each Teamwork pipeline resolves to a named Odoo Sales Team and stage order.

Each named Teamwork CRM pipeline becomes an Odoo Sales Team. Odoo Sales Teams group leads by sales unit and provide team-level assignment rules and dashboards. We configure the team name, member list (from Odoo res.users mapped from Teamwork owners), and team-specific stage sequence. Stage order within each team maps from Teamwork's pipeline stage configuration.

Teamwork CRM pipeline stages (with custom names, sort order, and probability percentages) map to Odoo crm.stage records scoped to the relevant Sales Team. Probability percentages migrate to the stage's projected_revenue percentage field in Odoo. Stage name, sequence, and fold (whether the stage collapses in the Kanban view) are configured. We flag any deprecated or inactive Teamwork stages that the customer wishes to archive rather than import.

Teamwork CRM supports custom fields of type short text, integer, and dropdown only. We pre-create equivalent Odoo custom fields on the target model (res.partner for contact/company fields, crm.lead for deal fields) before any data import. Text custom fields map to Odoo Char or Text; integer maps to Integer; dropdown maps to Selection with the customer's option labels as the selection values. Multi-select, date, or boolean custom fields that the customer uses via Teamwork workarounds require manual Odoo field creation before migration begins.

Teamwork CRM Users (owners) map to Odoo res.users records resolved by email address match. Before migration begins, the customer provisions Odoo user accounts for every Teamwork user referenced on Contact, Company, Lead, Opportunity, or Activity record. Any Teamwork Owner without a matching Odoo User is held in a reconciliation queue. Active/inactive status in Teamwork maps to active boolean in Odoo res.users.

Teamwork CRM Activities (calls, meetings, tasks) linked to Contacts or Opportunities map to Odoo mail.activity records. Activity type (call, meeting, task) maps to activity_type_id in Odoo; subject and description transfer as activity's summary and note fields. Date, due date, duration, and completion status preserve. Assignee maps from Teamwork owner_id to Odoo res.users via the User lookup. The related Odoo Partner or crm.lead record is set as res_id with the correct model.

Teamwork CRM notes attached to Contacts or Opportunities migrate as Odoo mail.message records with message_type=comment. The message body carries the note text. We link the message to the correct Partner or crm.lead record via res_id and model. Note author maps to Odoo res.users via email lookup. Internal notes in Teamwork map to Odoo internal message subtype.

Teamwork CRM tags on Contacts and Opportunities map to Odoo crm.tag records. Tags are created once and linked via crm.lead.tag_ids on crm.lead records. For tags on Teamwork Contacts (mapped to Partner), Odoo does not have a native Partner tag model in standard CRM — we map those to a custom Char field partner_tag__c or to a Note record for searchability. The customer selects the preferred strategy during scoping.

Teamwork CRM saved custom filters are workspace-level view configurations, not business data. We capture filter definitions (field conditions, operators, sort order) as a reference document delivered alongside the migration. The customer's Odoo admin rebuilds applicable filters in Odoo Studio. Custom filters do not carry as migratable data records.