Migrate from Iterable to Odoo CRM

Iterable User Profiles map to Odoo CRM Lead for unqualified prospects and Contact for qualified buyers. We apply a lifecycle-based split during scoping: Iterable users with subscription or marketing-only signals map to Lead; users with a purchase event or assigned sales owner map to Contact. The original Iterable userId and email preserve as fields on the Odoo record for audit and deduplication.

Iterable profile-level custom fields map directly to custom fields on Odoo crm.lead or res.partner. We audit the full custom field schema during scoping, flag deprecated fields (which Iterabl cannot delete), and collapse redundant or unused fields to keep the Odoo schema clean. Field type mapping converts Iterables picklist, boolean, date, and number types to their Odoo equivalents.

Iterable Lists are audience segments used for campaign targeting. We map each List to an Odoo Tag attached to the corresponding Lead or Contact. List membership is preserved as a Tag value so segmentation logic is recoverable in Odoo. Note that Tags in Odoo are a flat key-value structure and do not support the nested or dynamic audience logic that Iterable Lists offer; we document the original List definition for the admin to rebuild in Odoo.

Iterable Custom Events capture behavioral data beyond profile updates (page views, feature usage, cart actions). We map these to Odoo Activity records logged against the corresponding Lead or Contact. Event metadata (event name, timestamp, payload) stores in the Activity note body. This preserves the behavioral signal for historical analysis but does not trigger Odoo automations natively. If behavioral triggers are required, we recommend a separate event-tracking integration post-migration.

Iterable Purchase events record transaction data (orderId, total, items, userId). We map these to Odoo Sale Order lines attached to the customer Contact if Odoo Sales app is active, or to Activity log entries if only the CRM module is in scope. Total revenue and item count preserve as Activity note content. Note that Iterables revenue attribution does not map to Odoo Opportunity without additional configuration.

Iterable tracks channel-level opt-in and opt-out state per user (email, SMS, push). We map these to Odoo Contact fields: email opt-out to user_ids.opt_out, SMS opt-out to a custom field sms_opt_out__c. Suppression event history preserves as Activity log entries so the team can audit opt-out timestamps post-migration. Note that Odoo CRM does not have a native SMS opt-out field and requires a custom field or partner app for SMS compliance tracking.

Iterable Campaign records contain metadata (name, channel, status, schedule). Campaign metadata migrates as Odoo Opportunity records with the campaign name as Opportunity name, or as Activity log entries if no Opportunity association is appropriate. Campaign metrics (sends, opens, clicks) do not have a native Odoo equivalent and are documented in a separate campaign audit spreadsheet for the admin.

Iterable Templates define email, SMS, and push message content with Handlebars personalization syntax. Odoo CRM does not have a message content template system; email templates are scoped to CRM mail templates and do not support the multi-channel dynamic content that Iterables templates provide. We export template metadata and content to a structured document during migration. The customer rebuilds templates in their chosen marketing execution tool (Odoo Email Marketing, a separate ESP, or the tool they adopt post-Iterable).

Iterable Journeys define multi-step, multi-channel automation paths with branching logic, delays, and action triggers. Odoo CRM has Automated Tasks and Server Actions that cover basic trigger-response workflows but do not replicate Iterables Journey logic. We deliver a written Journey inventory during migration: each Journey documented with its trigger conditions, step sequence, channel actions, and recommended Odoo Automated Task equivalent. The admin rebuilds Journeys post-migration in Odoo or in a dedicated marketing automation tool.

Iterable Catalog stores product data used for dynamic content insertion in messages. If the Odoo Sales app is active, we import Catalog schemas and items as Odoo Product records with relevant fields (name, SKU, price, description). If only Odoo CRM is in scope, Catalog items migrate as custom fields or a dedicated custom module. Note that Catalog-to-Journey associations do not migrate; these relationships are documented for the admin to reconfigure in Odoo.

Iterable email engagement records (sends, opens, clicks, unsubscribes) migrate as Odoo Activity log entries attached to the corresponding Lead or Contact. Email content summary preserves in the Activity note body. Odoo CRM does not have a native engagement tracking layer; the activity log provides a historical record but does not update a live engagement dashboard. If ongoing email engagement tracking is required, a separate marketing integration is needed.

Iterable call engagement records (call made, answered, duration, recording) migrate as Odoo Activity log entries. Duration and disposition data preserve in the Activity note. Call recordings do not migrate to Odoo natively; we document the original recording URL if the customer has an external storage policy.

Iterable meeting engagements (name, date, attendee list) migrate as Odoo Activity log entries. Attendee associations map to additional Activity log entries or are documented in the Activity note body. Odoo CRM does not have a native meeting calendar sync without Odoo Calendar app; we flag this dependency during scoping.

Iterable Owners map to Odoo Users. We resolve owners by email match against the destination Odoo User list. Any Iterabl Owner without a matching Odoo User goes to a reconciliation queue for the customer admin to provision before record import resumes.

Iterable Data Sync exports data to a warehouse and requires Customer Success coordination and IP allowlisting. If the customer uses Data Sync as a primary data source, we export the historical records to CSV or JSON and deliver them alongside the CRM migration. The customer is responsible for loading warehouse exports into their chosen analytics environment post-migration.