Migrate from Systeme IO to Odoo CRM

Systeme.io contacts map directly to Odoo res.partner (type=contact). The email, phone, name, and address fields map to Odoo's standard contact fields. Systeme.io contacts linked to a company set the res.partner's parent_id to the mapped company record. Unlinked contacts land as standalone partner records.

Systeme.io companies map to res.partner with type=company. The company name maps to the partner's name field. Website, industry, and employee count map to website, industry, and employee_qty on the company partner record. Parent-child hierarchy in Systeme.io maps to parent_id on res.partner.

Systeme.io deals map to Odoo crm.lead records. The deal name becomes the lead's name field. Deal amount maps to Odoo crm.lead's expected_revenue or planned_revenue (depending on stage). Deal stage maps to crm.lead stage_id, which points to a crm.stage record scoped to the target sales team.

Each named Systeme.io pipeline becomes a dedicated Odoo crm.team (sales team) with its own set of crm.stage records. Systeme.io stage names map to stage_id values under that team. If Systeme.io has one pipeline, Odoo uses the default Sales Team and its stages. Multiple pipelines require pre-creation of additional crm.team records.

Systeme.io contact tags map to res.partner.category_id (a many2many to res.partner.category). Each unique Systeme.io tag becomes a res.partner.category record. If a contact has multiple tags, all are applied as many2many category links on the res.partner record. Tags without an Odoo equivalent are preserved as a custom Char field for manual review.

Systeme.io deal tags map directly to Odoo's crm.lead.tag model, which is a dedicated tag classification system for CRM leads. Each unique Systeme.io deal tag is created as a crm.lead.tag record, and the corresponding lead's tag_ids field (many2many) links the crm.lead to all its applicable tags for filtering and segmentation in Odoo's pipeline view.

Systeme.io products map to Odoo product.template records (name, list_price, default_code). Historical transaction line items that reference specific products need sale.order records in Odoo, linked to the customer partner. Odoo Community requires the Sale app to be installed for order records. Products must exist before sale.order.line records can reference them.

Systeme.io transactions (payment status, amount, date) map to Odoo account.move records as customer invoices or bills depending on direction. The res.partner (customer) is linked via partner_id. Odoo requires the Accounting app to be installed for invoice records. Payment status maps to move_state and payment_state fields. We store Systeme.io's transaction ID in a custom reference field on the account.move.

Systeme.io automation rules and email sequences do not have structural equivalents in Odoo CRM. The logic (triggers, conditions, actions, delays) is exported as a JSON specification from Systeme.io and provided as a rebuild reference. FlitStack documents the trigger conditions, tag-based audience filters, and action sequences so your Odoo admin can rebuild them using Odoo's Studio automation builder or base.automation module.

Systeme.io custom contact fields (created via the property builder) migrate as Odoo custom fields on res.partner. Field type is inferred from the source data — text fields map to char, numeric fields to float or integer, date fields to date, and pick-list fields to selection or many2one depending on Odoo version. All custom fields must be pre-created in Odoo before migration runs. We provide a field creation checklist as part of the migration plan.

Systeme.io sales funnels, landing pages, and blog posts have no direct Odoo CRM equivalent. Pages can be migrated to Odoo Website (if installed) as website.page records, but funnel logic (upsells, order bumps, gated content) must be rebuilt in Odoo's eCommerce or product configurator modules. We export the page structure as a reference document for your Odoo implementation team.

Systeme.io team members (owners assigned to contacts and deals) are resolved by email match against Odoo res.users records. If a Systeme.io owner email matches an existing Odoo user, that user's id populates the crm.lead's user_id and the res.partner's user_id. Unmatched owners are flagged before migration; you either invite them to Odoo first or assign their records to a fallback user.