Migrate from Smarketing Cloud to Odoo CRM

Smarketing Cloud Contact records map to Odoo res.partner in address type (is_company=False). Standard fields (name, email, phone, website) map directly. Custom Contact properties migrate as custom partner fields created via Odoo's Settings > Technical > Custom Fields interface. The res.partner model in Odoo conflates individuals and organizations under one table with an is_company flag; we set is_company=False for all Contact records. Lifecycle stage from Smarketing Cloud maps to a custom stage field partner_stage__c and is preserved for reporting continuity.

Smarketing Cloud Company records map to Odoo res.partner with is_company=True. The Company-Contact linkage is preserved via the child_ids relationship on the parent res.partner record. We export Companies first, then Contacts, so the parent Company record exists before we create child Contact records with parent_id resolved.

Smarketing Cloud Deals map to Odoo crm.lead in Opportunity mode (type='opportunity'). The deal amount, currency, and close date map to Odoo's expected_revenue, currency_id, and date_closed. Deal stage maps to Odoo stage_id by matching stage names; we configure the destination stage sequence before migration so the name-to-ID lookup resolves at import time. Pipeline assignment from Smarketing Cloud maps to crm.team_id in Odoo.

Each Smarketing Cloud Deal pipeline becomes an Odoo crm.team (sales team) with its own stage sequence. We extract the full stage order and probability weights from Smarketing Cloud and configure matching stage records in Odoo via the crm.stage model before Deal migration. Stage names that differ from Odoo defaults are created as new stage records scoped to the relevant team.

Smarketing Cloud Campaign membership (which Contact was enrolled in which Campaign and when) migrates to Odoo as crm.tag records on the Contact partner record, with a custom Campaign enrollment date field campaign_enrolled_date__c. Active Campaign send history is documented as a mail.mailing configuration reference for the customer's admin to rebuild in Odoo's Email Marketing app if the customer licenses it.

Smarketing Cloud activity logs (calls, emails, notes, tasks) linked to Contacts and Companies map to Odoo mail.activity records. Activity type from Smarketing Cloud maps to activity_type_id in Odoo (call, email, meeting, todo). The res.partner record is the activity's res_id target. Owner assignment maps by resolving Smarketing Cloud owner email to the corresponding Odoo res.users record via email match.

File attachments linked to Contacts, Companies, or Activities are exported from Smarketing Cloud with their file URL and metadata. We download files to a staging bucket and re-upload to Odoo as ir.attachment records linked to the corresponding res.partner or crm.lead via res_model and res_id. The original filename and mimetype are preserved.

Smarketing Cloud User records (name, email, role, team assignment) map to Odoo res.users. We map Smarketing Cloud roles to Odoo access rights groups (Employee, Sales Manager, Administrator). Inactive users can be exported but the migration scope excludes user provisioning; the customer's Odoo admin provisions active users before production migration.

Tags applied to Contacts and Companies in Smarketing Cloud migrate to Odoo crm.tag records and are re-applied via the tag_ids many2many relationship on res.partner. Tag names are preserved as-is; Odoo creates tag records on import if they do not already exist. Bulk tag application uses Odoo's write operation on the partner record set.

Static Lists from Smarketing Cloud are exported as record sets and become Odoo crm.team membership records (team member assignments) plus a custom team_static_list__c field referencing the list name. Dynamic Segments are documented as domain filter criteria for the customer to recreate as Odoo saved filter views or team assignment rules.

Smarketing Cloud Email Templates with HTML content and variable placeholders export cleanly, but Odoo uses a different template variable syntax ({{field}} vs Odoo's {{object.field}} or {{ctx.get('field')}}). We extract the HTML body and variable names and deliver a template mapping document specifying the Odoo template reconstruction for each source template. The customer's admin rebuilds templates in Odoo Mail Composer using the mapping document as a guide.

Smarketing Cloud custom objects and their schemas (field definitions, record data) migrate to Odoo custom models created via ir.model and ir.model.fields before data import. The custom model API name is matched to the Smarketing Cloud custom object name. Custom object relationships (lookups to Contacts or Companies) are preserved as Odoo many2one fields pointing to res.partner or crm.lead. All custom field types are mapped to the closest Odoo field type (char, text, float, integer, date, many2one, selection) during schema design.