Migrate from Simplero to Odoo CRM

Simplero Contacts migrate to Odoo res.partner records. We preserve name, email, phone, address fields, subscription date, and custom contact field values. The dedupe key is email. If a Simplero Contact has an associated Company name, we create a separate res.partner Account record and link the Contact as a child partner via type=contact. Custom Contact Fields must be pre-created in Odoo Studio before migration; we document the required field name, type, and sample values from Simplero during scoping.

Simplero Contacts with no associated product enrollment and no order history are treated as unqualified prospects and migrate to Odoo crm.lead records. We compute this split by checking enrollment and order association during the transform phase. Leads carry the original contact email and name; any Simplero tags migrate as crm.lead.tag records linked via crm.tag.rel.

Simplero flat tags migrate to Odoo res.partner.category records applied to res.partner. Dynamic Segments (filter-based groups) migrate as Odoo CRM Tags with a note that the dynamic behavior must be recreated using Odoo Studio domain filters on the CRM Lead or Opportunity search view. Segments with complex multi-condition logic are documented but cannot be migrated as live automation.

Simplero Deals migrate to Odoo crm.lead records with type=opportunity. Deal stage maps to Odoo Stage (stage_id) with the probability percentage preserved from Simplero. The deal value (amount) maps to Odoo's expected_revenue and planned_revenue fields. If Simplero Deal is linked to a Contact, we resolve the Contact's Odoo res.partner ID as the partner_id on the Opportunity. Note that Odoo Deals are only available when the CRM app is activated; we confirm CRM app is installed before migration begins.

Simplero pipeline stages (e.g., Qualified Lead, Demo Scheduled, Proposal Sent, Won, Lost) map to Odoo crm.stage records created under the active CRM sales team. Stage probability percentages migrate as is, rounded to the nearest integer Odoo allows. If Simplero uses multiple pipelines, we create multiple CRM sales teams in Odoo and map pipeline-to-team during scoping.

Simplero Products (courses, memberships, digital downloads, coaching programs) map to Odoo product.template records with type=service. Pricing, product-type classification, and access rules migrate as product.list_price and product.categ_id. If a Simplero product is a bundle or includes multiple access tiers, we create separate product.template variants in Odoo to represent each tier.

Simplero order records migrate to Odoo sale.order as confirmed sales orders. The order product lines map to sale.order.line with Odoo product.product references resolved by SKU match. Payment gateway, order date, and refund status are stored in custom fields on sale.order since Odoo out-of-the-box payment tracking is tied to the account.move (invoice) model. Refund flags become a sale.order.custom_status field set to Refunded or Partially Refunded.

Simplero Members (contacts with active product access) map to sale.order records for one-time purchases or to Odoo Subscription (sale_subscription app) records for recurring access. If the Simplero subscription uses tiered pricing, we create multiple product variants in Odoo and link the enrollment to the correct variant. The enrollment date and expiration date migrate as custom fields on the subscription or sale order.

Simplero help desk tickets migrate to Odoo helpdesk.ticket records. Ticket subject, status, assignee, and conversation thread migrate as ticket description and chitchat.message records linked to the ticket. Ticket priority maps to Odoo priority. Note that Simplero help desk is only available on Scale and above, so tickets from Starter-plan accounts are not present. Odoo helpdesk requires the helpdesk app to be installed and activated.

Simplero email broadcast content (subject, body, from name) migrates as Odoo mass.mailing records. The Odoo email marketing module must be installed. Individual contact suppression lists and per-send analytics (open rate, click rate) do not transfer because Odoo tracks these at the send level, not the broadcast level. Email send history is preserved as a record in the migration log for reconciliation but does not populate the Odoo mailing stats.

Simplero Owners map to Odoo res.users records by email match. We extract every distinct owner referenced on Contact, Deal, and Ticket records and reconcile against the destination Odoo instance. Any Simplero Owner without a matching Odoo User is held in a reconciliation queue; the customer's Odoo admin provisions the missing User before record import resumes. Inactive Simplero owners map to Odoo users with active=False.

Simplero site pages migrate as Odoo website.page records. We preserve slug paths to support URL redirects. Media assets and theme settings require separate export and re-import; Simplero's no-code builder content maps to HTML content on Odoo website pages but visual layout (columns, spacing, block types) does not transfer and requires rebuilding in Odoo's website builder.

Simplero Custom Contact Fields must be pre-created in Odoo Studio before migration. We document the field name in Simplero, its data type (text, number, date, checkbox, dropdown), and sample values during scoping. The customer or an Odoo admin creates the corresponding field in Odoo Studio, and we map the field values during the contact import phase. Fields with invalid Odoo field names (spaces, special characters) are renamed per Odoo's field naming convention during transform.