Migrate from Odoo Marketing Automation to Nutshell

Odoo CRM Contacts map directly to Nutshell People. We extract name, email, phone, company (partner_id), tags, and custom fields from the res.partner model. Odoo stores tags in a separate ir.attachment model; we flatten them to a string array and reassign by name on the Nutshell People record. The migration dedupes on email address and preserves the original Odoo contact ID in a custom field for audit.

Odoo CRM Leads map to Nutshell People with the lead flag set. We extract name, email, phone, stage, priority, expected closing date, and source from crm.lead. Odoo unifies Leads and Contacts under the res.partner model, so we treat any record where type is 'lead' as a Nutshell Person in lead status. Stage names migrate as custom fields and are reconciled against the customer's Nutshell pipeline stages during scoping.

Odoo Marketing Automation Campaigns map to Nutshell Task records with a campaign reference tag. We extract campaign name, target model (Contact, Lead, Sales Order), audience domain filter, and campaign state. The audience domain filter does not replay on Nutshell; we document the original filter logic as a written item for the customer to manually configure Nutshell's People segmentation or sequence enrollment rules. Campaign traces and activity logs are migrated as Task records attached to the relevant People.

Odoo Automation Rules map to Nutshell Sequences or are documented as manual-rebuild items depending on their complexity. We extract rule name, trigger type (time-based, email event, server action), filter domain, and action chain. Rules containing Python Code activities are flagged as manual-rebuild items because those server-action blocks reference Odoo models with no Nutshell equivalent. Simple time-triggered and email-event-triggered rules with Send Email or Update Record actions are documented with their trigger logic and recommended Nutshell Sequence equivalent.

Odoo Mass Mailings from the Email Marketing app migrate as Nutshell Email Template records. We extract subject, body HTML, scheduled date, and recipient count. Recipient lists are resolved via Contact or Lead domain queries at migration time; we do not preserve the live mailing list as a dynamic segment because Nutshell's template model is static. HTML body and inline images are preserved as template content for the customer to use in future Nutshell sequences.

Odoo Email Templates used by both Email Marketing and Marketing Automation migrate to Nutshell Email Templates. We extract template name, subject, body HTML, and attachment references. Inline images and variable placeholders are preserved. The customer manually maps Odoo's {{object.field}} variable syntax to Nutshell's merge field syntax during the template review step.

Odoo Opportunities (crm.lead with type 'opportunity') map to Nutshell Accounts and pipeline entries. We extract opportunity name, stage, expected revenue, partner, and lost reason. Stage names vary by Odoo database and require a mapping table during scoping. Nutshell's pipeline stages are customer-configured, so we create the mapping before migration and validate that all source stage values have a destination equivalent.

Odoo custom fields added via Odoo Studio or ir.model.fields migrate as custom fields on the relevant Nutshell Person or Account record. Field type (char, integer, many2one, etc.) is preserved from the ir.model.fields metadata. Many2one fields referencing other Odoo models (e.g., a custom field pointing to a product) are migrated as string values with a note that the relationship does not replay on Nutshell.

Odoo user accounts referenced as create_uid, write_uid, and assignees on CRM records and automation rules map to Nutshell Users. We resolve by email match. Any Odoo User without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import resumes.