Migrate from Teamleader to Odoo CRM

Teamleader Contacts map to Odoo res.partner records with partner_short_name carried as a custom field and the Teamleader contact ID preserved in external_id for reconciliation. The Teamleader Company association maps to the parent_partner_id on res.partner. Mobile and phone numbers map to mobile and phone fields respectively. Email maps to email. Custom fields defined under the Teamleader contact context map to ir.model.fields on res.partner.

Teamleader Companies map to Odoo res.partner records with type=contact (or type=false for the company record itself) and is_company=True. The Teamleader Company ID is preserved in external_id. Address components (street, city, country, zip) map to standard address fields on res.partner. Custom fields under the Teamleader company context map to ir.model.fields on res.partner. Contacts linked to this Company resolve parent_partner_id to the res.partner created from the Company.

Teamleader Deals map to Odoo crm.lead records with type=opportunity. The Teamleader deal title becomes the crm.lead name. Teamleader dealstage maps to stage_id on crm.lead via the Odoo CRM stage sequence. Probability percentage migrates from Teamleader's stage probability to crm.lead probability. Expected revenue and closing date map to planned_revenue and date_closed respectively. Custom fields under the deal context map to crm.lead custom fields.

Each Teamleader Pipeline with its Stages maps to an Odoo CRM stage sequence. We create stage records in Odoo matching the Teamleader stage names, ordered by Teamleader stage position, and set probability percentages on each stage. Teams with multiple Teamleader Pipelines that need separate pipeline views in Odoo require Record Type configuration or a team_id split; we document this requirement in the migration scope and configure if Odoo Studio is available.

Teamleader Projects map to Odoo project.project records. Project name, description, and deadline map to name, description, and date. The Teamleader Project status (active/archived) maps to active. Custom fields under the project context map to project.task custom fields if needed. We migrate Project records before Milestones so that the parent project_id reference is available at Milestone import time.

Teamleader Milestones map to Odoo project.task records with the parent Project linked via project_id. Teamleader Milestone due date maps to date_deadline, and the Milestone budget maps to a custom float field milestone_budget__c since Odoo task does not have a native budget field. Milestone custom fields map to ir.model.fields on project.task.

Teamleader Quotations map to Odoo sale.order records with state=mquotation (draft). Line items from Teamleader map to sale.order.line with product, quantity, and price. Teamleader quotation expiry dates map to validity_date. Teamleader margin and pricing data migrate to sale.order.line price_unit and discount fields. The linked Contact or Company resolves to res.partner id via the partner mapping.

Teamleader Invoices map to Odoo account.move records with move_type=out_invoice. Invoice number becomes name, line items map to invoice_line_ids with product, quantity, price_unit, and tax. Payment status from Teamleader maps to payment_state on account.move. Invoice date maps to invoice_date. Teamleader's QR-code payment state, automatic reminder triggers, and overdue flags do not transfer because they are tied to Teamleader's payment processor; we document this in the migration scope and flag it for post-migration reconfiguration of Odoo's payment provider.

Teamleader Subscriptions map to Odoo sale.subscription records. The subscription periodicity (monthly, quarterly, annually) maps to recurring_interval and recurring_rule_type on sale.subscription. Recurring price maps to recurring_monthly_total. Teamleader subscription status (active, paused, cancelled) maps to stage_id on sale.subscription. Line items map to sale.subscription.line. Custom fields under the subscription context map to custom fields on sale.subscription.

Teamleader Products map to Odoo product.product records with product_tmpl_id linking to product.template. Product name, SKU (hs_sku equivalent), and list price map to name, default_code, and list_price. Product type (service vs goods) maps to type. Custom fields under the product context map to product.template custom fields.

Teamleader Tickets map to Odoo helpdesk.ticket if the destination Odoo instance includes the Helpdesk app. Ticket subject, description, and status map to name, description, and stage_id. Teamleader assignee maps to user_id. Linked Company or Contact resolves to partner_id via the res.partner mapping. Custom fields under the ticket context map to helpdesk.ticket custom fields. If Helpdesk is not installed in the destination Odoo, Tickets are mapped as project.task under a dedicated support project.

Teamleader Time Entries map to Odoo account.analytic.line records. User, duration, billable flag, and date map to employee_id (resolved via User mapping), unit_amount, is_billable, and date. Project linkage maps to project_id via the project mapping. The linked Task or Milestone resolves to task_id via the Milestone mapping. Billable time entries are flagged for potential invoice generation post-migration.

Teamleader Tasks map to Odoo project.task records. Task title, description, due date, and status map to name, description, date_deadline, and stage_id. Assigned user maps to user_id via the User mapping. Linked Contact or Deal resolves via the respective mappings. Teamleader Tasks that are not linked to a Project map to a generic project.task with project_id set to a placeholder project we create during migration.

Teamleader Meetings map to Odoo calendar.event records. Title, start datetime, end datetime, and location map to name, start_datetime, stop_datetime, and location. Attendees resolve via the res.partner mapping for external attendees and res.users mapping for internal attendees. Linked Contact or Deal resolves via the respective mappings.

Teamleader Phone Calls map to Odoo mail.activity records with activity_type_id set to 'Phone Call'. Call duration and disposition map to custom fields on the activity. Linked Contact or Deal resolves via the respective mappings. Odoo 17+ supports phone.code records for call logging; we configure the destination's activity type and document the call log configuration in the migration scope.

Teamleader custom fields scoped under each context (contact, company, deal, project, milestone, product, invoice, subscription, ticket) are enumerated during scoping via the Teamleader customFieldDefinitions.list API. Each field maps to an Odoo custom field on the corresponding model (res.partner, crm.lead, project.project, project.task, product.product, account.move, sale.subscription, helpdesk.ticket). Field type mapping converts Teamleader field types (text, number, date, single-select, multi-select) to Odoo field types (char, float, date, selection, many2many). Fields with the same name appearing in multiple Teamleader contexts are created as separate Odoo fields on each relevant model.