Migrate from Touchpoint MX to Odoo CRM

Touchpoint MX Contacts map directly to Odoo CRM Contacts. Standard fields (name, email, phone) map to Odoo's name, email, and phone fields. Custom field values on the Contact record map to Odoo custom fields created in Settings > Technical > User-defined Fields before migration. Owner assignments in Touchpoint MX map to Odoo User records by email match; any unmatched Owner goes to a reconciliation queue for the customer's admin to provision.

Touchpoint MX stores Companies as organizational records. These map to Odoo CRM Companies (the same Contact type with is_company=True). Company name maps to Odoo's name field; any domain or address data maps to street, city, state, country fields. If Touchpoint MX does not have a Companies object and all records are personal Contacts, we create a pseudo-Company for each Contact to satisfy Odoo's Contact-Company hierarchy.

Touchpoint MX Journey Maps define custom stage labels (e.g., Awareness, Consideration, Decision) that vary by organization. We detect the complete Journey Map stage taxonomy during scoping, create a custom Contact field journey_stage__c in Odoo to store the original stage label, and map each stage to an Odoo pipeline stage (or a Contact custom field) depending on the customer's Odoo configuration. The full stage transition history flattens into a text or notes field if Touchpoint MX stores stage change timestamps.

Touchpoint MX records active channels (Email, SMS, Voice) per Contact. Odoo CRM has no native channel preference field. We create a custom multi-select field contact_channels__c in Odoo and map each active channel to one selection. If the customer uses Odoo integration with a third-party telephony or SMS provider (Nauta, Twilio), we document the channel field as the opt-in source for the integration configuration.

Touchpoint MX Satisfaction Scores (numerical ratings) map to a custom float or integer field on Odoo Contact, named satisfaction_score__c. We preserve the score value, scale (0-10 or 1-5), and the timestamp when the score was recorded. If Touchpoint MX stores multiple satisfaction records over time, we migrate the most recent score and log historical scores as Notes with a score tag for longitudinal reporting.

Touchpoint MX Feedback Records are structured entries with text, date collected, and related Contact. We map Feedback text to Odoo Note.body (as HTML), set Note.create_date to the original Feedback timestamp, and link the Note to the Contact via res_id and res_model=res.partner. This preserves the full feedback history in the Contact's chatter and allows Odoo users to read feedback in context.

Touchpoint MX Message Templates (reusable outbound content) do not have a direct Odoo CRM equivalent. We export Template content, subject lines, and personalization tokens as a structured Note on the relevant Contact or as a standalone Note tagged with template_type=message_template. The customer's admin uses this as a reference to rebuild templates in Odoo email templates or a custom module.

Touchpoint MX Users map to Odoo Users by email match. We extract every distinct user referenced as an Owner on Contact, Journey Map, and Feedback records. Odoo User records must be provisioned manually by the customer's Odoo admin before Contact migration because OwnerId (create_uid) is a required field for activity logging and record assignment in Odoo CRM.

Attachments associated with Contacts or Feedback records in Touchpoint MX are exported as files and stored in Odoo's ir_attachment table with res_model=res.partner and the corresponding Contact ID as res_id. Large attachment volumes (over 1,000 files or files exceeding 25 MB) are chunked to avoid timeout; we flag oversized files during scoping and recommend compressing or archiving before migration.

Touchpoint MX custom fields on Contacts are exported with their values per record. We create matching custom fields in Odoo (Settings > Technical > User-defined Fields) before migration, using Odoo's field types (char, integer, float, selection, boolean, text) to match the source data type. Touchpoint MX visibility settings (Manager-only, Attendee-only, Everyone) do not transfer; we apply the most permissive Odoo access group that includes all roles to avoid data suppression.

Touchpoint MX integrations (connected apps, OAuth tokens, webhook endpoints) are bound to the source account and cannot be exported or transferred. We export a written inventory of every active integration with its configuration parameters, endpoint URLs, and authentication method. The customer's admin uses this inventory to re-establish integrations in Odoo (via Odoo Apps, REST API, or webhook automation) after migration.

If Touchpoint MX stores deal-like records or if the customer has been using Touchpoint MX for sales-stage tracking alongside journey mapping, these map to Odoo CRM Opportunity. We create Odoo pipeline stages to match the source stage labels, map record-level data to name, partner_id, stage_id, expected_revenue, and probability fields, and link each Opportunity to the migrated Contact (partner_id) and Company (parent_id).