Migrate from Splio to Odoo CRM

Splio Contacts map to Odoo res.partner records. The primary mapping uses email as the dedupe key. Splio custom fields in the contacts scope declare as Odoo Studio custom fields on res.partner before import. Critical: we audit for orphan contacts (contacts without any list membership) before the Splio export, assign them to a catch-all Odoo partner tag, and verify post-export counts match the full Splio contact total. Odoo has no equivalent to Splio's list-membership gate; all active partners appear in reporting by default.

Splio list memberships map to Odoo res.partner.category (tags). Each Splio list becomes an Odoo partner category, and membership is set during partner import via SQL or partner import tool. These tags are used to rebuild Splio filter-based campaign targets inside Odoo's segment filters and Action Rules post-migration.

Splio Store records map to Odoo res.partner with company_type=company. The store's address, city, country, and location coordinates map to Odoo's street, city, country_id, and partner_latitude/longitude fields. Custom fields in the stores scope declare on res.partner using Odoo Studio before import. Stores with loyalty program assignments link to the relevant Odoo Loyalty program via a Many2one field.

Splio Orders map to Odoo sale.order records. Each Splio order links to a contact (res.partner) and carries order_items referencing products. We resolve the partner_id from the contact migration before inserting sale.order records. Splio's order_id replacement on duplicate imports has no Odoo equivalent; we use the Splio external_id mapped to Odoo's client_order_ref field and rely on the customer's dedupe preference (upsert by client_order_ref or insert-only) during import. Order dates and confirm timestamps migrate as date_order and date_confirm.

Splio order_items map to Odoo sale.order.line records. Each line requires a resolved product_id from the product migration and a resolved order_id from the sale.order parent migration. We validate product existence in Odoo before inserting lines; any order_item referencing a missing product is logged to a quarantine report for the customer's admin to resolve (either create the product or reassign the line). Quantity, unit_price, and discount migrate directly.

Splio Products map to Odoo product.product records. The product name, sku (product_code), and barcode migrate as name, default_code, and barcode respectively. Custom fields in the products scope declare on product.product via Odoo Studio before migration. Products are inserted before order_items so that the product_id lookup is satisfied at the moment of order line import.

Splio Loyalty memberships map to Odoo loyalty.card records within the Loyalty program. Each card carries the card_code (mapped to Odoo's code field), nq_points (non-quantized points, stored in Odoo's points field with decimal precision), q_points (quantized points), and the program tier mapped to Odoo's loyalty program level. The loyalty.card is linked to the migrated res.partner via partner_id. We sequence loyalty migration before campaign target rebuilding because Splio filter-based segments reference loyalty-tier data that must exist in Odoo first.

Splio Rewards (program-level reward definitions) and reward attributions (which contacts received which rewards) map to Odoo loyalty.reward records within the relevant loyalty.program. Each Splio reward maps to a configured Odoo loyalty reward of matching type (discount, free product, free shipping). The attribution history migrates as loyalty.card line records tracking reward redemption. We map reward attributions after loyalty.card is resolved, ensuring the contact relationship is satisfied.

Splio Interactions are custom events sent via API for loyalty point credits and campaign triggers. These map to Odoo mail.message records on the res.partner timeline, tagged with a custom subtype to distinguish them from standard activities. Event type, timestamp, and payload data migrate as custom message fields. Customers planning to use Odoo's CRM tracking instead reclassify these events during scoping.

Splio blocklists migrate as Odoo mail.blacklist entries. Email addresses on the Splio blocklist insert into Odoo's blacklist table with active=True so that mass mailing respects suppression. We verify the blocklist is honored during any post-migration test email send before go-live.

Splio's per-scope custom fields (contacts, stores, products, orders, rewards, loyalty) are declared in Odoo using Odoo Studio or the ir.model.fields API before data migration begins. Each scope's custom fields become custom fields on the relevant Odoo model (res.partner, product.product, sale.order, loyalty.card, loyalty.reward). We do not migrate Splio campaign filter logic as code; the customer uses migrated custom field data within Odoo's Action Rules and Studio filters to rebuild targeting logic.

Splio Owners referenced on Contacts, Orders, and Loyalty memberships map to Odoo res.users by email match. Any Splio Owner without a matching Odoo User is held in a reconciliation queue; the customer's Odoo admin provisions missing users before the production migration begins. Owner resolution is required before sale.order import because Odoo requires an effective user_id on orders.