Migrate from InTouch CRM to Odoo CRM

InTouch Contacts cover both unqualified prospects and qualified buyers. We split during migration: Contacts with InTouch lifecycle stage of New, Attempting to Contact, or Idle map to Odoo Lead. Contacts with stage of In Progress, Under Offer, or Closed Won map to Odoo Contact attached to a Company. We preserve the original InTouch lifecycle stage as a custom field itcrm_lifecycle_stage__c on both the Lead and Contact for audit and reporting after migration.

InTouch Company records map directly to Odoo CRM Company. The company name, domain, industry, annual revenue, phone, and address fields transfer one-to-one. Odoo requires Company to be created before any linked Contact import so that the contact_company_id lookup relationship is satisfied at Contact insert time. We sequence the import accordingly.

InTouch Deal records map to Odoo CRM Opportunity. The deal name, value, expected close date, and probability transfer. The InTouch pipeline stage maps to an Odoo Stage configured per sales team. Closed Won and Closed Lost reasons from InTouch become custom fields on the Odoo Opportunity. Deals without a linked Company create a placeholder Company in Odoo before the Opportunity is imported.

Each InTouch pipeline becomes an Odoo Sales Team with its own stage configuration. We map InTouch stage names to Odoo stage labels and probabilities, and configure the Odoo sales team to use the corresponding stage set. Stage order is preserved by setting the sequence integer on each Odoo stage.

InTouch Activity records (call, email, meeting, task) map to Odoo CRM Activities linked to the parent Contact, Lead, or Opportunity. We resolve the parent record by matching the InTouch record's contact_id or deal_id to the newly inserted Odoo record's external ID, which we store during the Contact and Opportunity import phase. Activity timestamps and descriptions transfer directly.

InTouch custom fields on Contact, Company, and Deal map to Odoo custom fields created via Odoo Studio before migration begins. Field type translation is required: InTouch text fields map to Odoo char or text fields; InTouch number fields map to Odoo float or integer; InTouch date fields map to Odoo date; InTouch dropdown fields map to Odoo selection fields with equivalent option lists. The customer selects which custom fields are critical to preserve during scoping.

InTouch Owner records map to Odoo Users by email match. We extract every distinct owner referenced on Contact, Company, Deal, and Activity and match against the destination Odoo instance's User list. Owners without a matching User go to a reconciliation queue for the customer's Odoo admin to provision before record import resumes.

InTouch tags on Contact, Company, and Deal transfer to Odoo Tags. Tag names and colors preserve where the source supports color metadata. Tags migrate as a separate entity after the primary record import so that they can be applied to existing Odoo record IDs.

InTouch Notes attached to Contacts, Companies, or Deals transfer to Odoo Notes linked via the mail.message model to the parent record. Rich text content converts to Odoo's HTML note format with attachment links preserved as Odoo attachments.

If InTouch CRM holds product records used in Deals, these map to Odoo Product records. The product name, SKU, unit price, and cost transfer. Products must be created before any Deal-to-Opportunity migration that includes product line items.

InTouch form submissions that created Contact records in InTouch map to Odoo Lead records. We preserve the submission source, landing page URL, and UTM parameters as custom fields on the Odoo Lead for attribution and reporting.

InTouch workflow automations (triggers, conditions, and actions defined in the automation builder) do not migrate as code. We audit every active automation, document its trigger object, conditions, and action sequence, and deliver a written inventory recommending equivalent Odoo Automated Actions or server actions for the customer's admin to rebuild in Odoo Studio or Python.