Migrate from Touchdown to Odoo CRM

Touchdown Contact records map to Odoo CRM Lead as the primary record type. Standard contact fields (name, email, phone, company name) map to Odoo's name, email_from, phone, and partner_name fields on crm.lead. We resolve the Touchdown company association from the contact's company_name property and carry it into the Lead's partner_name field for later Account creation. Any lifecycle stage or contact type property in Touchdown migrates as a custom Char or Selection field on the Lead for segmentation continuity.

Touchdown Contacts that represent active customers or qualified buyers map to Odoo Partner records attached to an Odoo Account (res.partner with partner_latitude populated to flag as a company). We apply a customer-type filter during migration: contacts with a campaign conversion event in Touchdown map directly to res.partner in customer mode. The customer's admin runs the Odoo Lead conversion (crm.lead convert_to_partner action) for in-progress Leads after migration, or we perform the conversion during migration if the customer provides a conversion rule during scoping.

Touchdown Company records map to Odoo res.partner records in company mode. The company name becomes the partner's name (displayed as company), and the company domain becomes the website field. Touchdown company custom properties migrate as custom fields on the res.partner record. We use company domain as the dedupe key during import. The Partner must exist before any Contact import that references it as a parent company.

Touchdown Campaign records map to Odoo CRM Campaign (utm.campaign). Campaign name, description, start and end dates, and status transfer directly. Touchdown campaign audience assignments (contacts associated with a campaign) map to Odoo CRM Campaign lines or to a Tag on the migrated Lead records so that campaign attribution is preserved without requiring a separate campaign-member object that Odoo CRM does not natively support in the same way Touchdown does.

Touchdown audience segments do not have a direct Odoo CRM equivalent. We discover each segment's filter criteria via Touchdown's API during schema exploration, then recreate those criteria as saved filter domains in Odoo CRM (ir.filters). The segment name becomes the filter name, and the filter domain is translated from Touchdown's segment logic to Odoo's domain notation (e.g., Touchdown 'country = USA AND lifecycle_stage = MQL' becomes [('country', '=', 'USA'), ('lifecycle_stage', '=', 'mql')]). We document the translation for the customer's admin as a living reference for segment maintenance.

Touchdown email templates with merge fields migrate to Odoo mail.template records. We export template body content (HTML), subject line, and merge field tokens, then map them to Odoo's subject and body_html fields using Odoo's QWeb template syntax where personalization tokens are represented as {{ object.field_name }}. The model's model_id on the mail.template record is set to crm.lead for Lead-facing templates or res.partner for Contact-facing templates.

Touchdown custom contact properties discovered during API exploration map to custom fields on Odoo crm.lead (for Lead-scoped properties) or res.partner (for Contact-scoped properties). We use Odoo Studio to pre-create each custom field before the production migration phase. Field type translation follows: Touchdown text becomes Char, long text becomes Text, number becomes Float or Integer, date becomes Date, and multi-select becomes Char (comma-separated) or a dedicated Selection field if the value set is known and bounded. The custom field must be created and deployed to the production Odoo instance before any records referencing it are imported.

Touchdown custom campaign properties discovered via API exploration map to custom fields on Odoo utm.campaign via Odoo Studio. These fields are created during the schema provisioning phase. The same type-translation rules apply as for Contact custom fields.

Touchdown email engagement history migrates to Odoo mail.message records attached to the relevant Lead or Partner (res.partner) record. The email subject, body (HTML), sender, and recipient addresses transfer directly. Activity timeline ordering is preserved by setting mail.message's date field to the original Touchdown timestamp. We link messages to the crm.lead or res.partner record using the model and res_id fields on mail.message.

Touchdown call engagements map to Odoo CRM Lead's activity log or to a Note (note.note) attached to the Lead or Partner record. Call duration, disposition, and outcome properties from Touchdown migrate as custom fields on the activity or note. The original call timestamp is preserved in the activity or note body for audit continuity.

Touchdown meeting engagements map to Odoo calendar.event records. Start datetime, end datetime, location, and description transfer directly. Attendee information from Touchdown migrates to calendar.attendee records linked to the event, with attendee email matched against migrated res.partner or res.users records by email address.

Touchdown task engagements migrate to Odoo CRM Activity records (mail.activity) linked to the Lead or Partner. Task subject, due date, priority, and status transfer directly. Owner assignment resolves Touchdown owner email to Odoo res.users and sets the activity's user_id accordingly. Tasks without a due date or future date become note-style records attached to the Lead.

Touchdown Owner records map to Odoo res.users. We resolve each Touchdown owner by email match against the destination Odoo res.users table. Any Touchdown owner without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before record import resumes. Odoo does not support inactive users on imported records in the same way Salesforce does, so we require active res.users records for all Touchdown owners referenced in the migration scope.