Migrate from Odoo Marketing Automation to Freshsales

Discovery and plan-tier check

We audit the source Odoo database: plan tier (Standard or Custom), active apps (Marketing Automation, Email Marketing, SMS Marketing), record volumes per object (Contacts, Leads, Opportunities, Campaigns, Automation Rules, Email Templates), and custom field definitions via ir.model.fields. We confirm XML-RPC API availability during this call and determine whether extraction uses the API (Custom plan) or CSV export from list views (Standard plan). We also identify which Odoo users correspond to CRM owners and whether the destination Freshsales tenant has the Growth-tier marketing automation license needed to host migrated campaigns.

Automation inventory and Python-flag extraction

We extract all Automation Rules (marketing.activity records) with their trigger_type, filter_domain, and action chain, flagging every rule that contains a Python Code activity. We extract Campaign metadata (name, target model, audience domain, state, participant counts) and Email Template metadata (name, subject, body HTML, model reference). We produce the automation inventory document before any data extraction begins so that the customer understands the rebuild scope and can allocate admin time to the Freshsales workflow builder post-migration. Python-dependent rules are explicitly excluded from migration and marked as manual-rebuild items.

Data extraction and cleansing

For Custom-plan databases, we pull Contacts, Leads, Opportunities, and Email Templates via XML-RPC using Odoo's external API endpoint (/xmlrpc/2/object) with the res.partner, crm.lead, and mail.template models. For Standard-plan databases, we export CSV files from Odoo's list views and normalize the field names. We deduplicate Contacts that share the same email address, flag incomplete records missing required fields (name, email), and validate email format against RFC 5322 before loading into Freshsales. Data cleansing is a separate chargeable phase if record quality issues exceed 15 percent of total volume.

Freshsales schema preparation and owner reconciliation

We create custom fields on Freshsales Contacts, Leads, and Deals to host Odoo-specific data (odoo_partner_id, odoo_stage__c, odoo_lost_reason__c) and to store any Odoo custom field values that have no Freshsales standard equivalent. We extract Odoo user accounts by email and match them against Freshsales Users. Any Odoo user without a matching Freshsales User is placed in a reconciliation queue for the customer's admin to provision before record import proceeds, because OwnerId references are required on Leads, Contacts, and Deals.

Production migration in dependency order

We run production migration in this sequence: Contacts (with tags resolved), Leads (with stage name mapping applied and original stage stored in odoo_stage__c), Deals (with partner_id resolved to Contact or Account, probability migrated, owner resolved), Email Templates (HTML body loaded into Freshsales template storage), and Campaign metadata (as Freshsales Sales Campaign records). Automation Rules are not migrated as code — they are documented in the automation inventory delivered at step 2. Each phase emits a row-count reconciliation report before the next phase begins, and we validate a random sample of 25-50 records against the Odoo source.

Cutover, delta migration, and automation handoff

We freeze writes on the Odoo source during the cutover window, run a final delta migration for any records created or modified since the initial extraction, then set Freshsales as the system of record. We deliver the automation inventory document to the customer's Freshsales admin, which lists every Odoo Campaign and Automation Rule with its trigger, conditions, action chain, and recommended Freshsales Workflow equivalent. We support a three-day hypercare window where we resolve any reconciliation discrepancies raised by the customer's team. We do not rebuild Odoo Automation Rules as Freshsales Workflows as part of the migration scope — that is a separate rebuild engagement or internal admin task.