Migrate from Simplero to Twenty CRM

Simplero Contact maps to Twenty CRM Contact as the primary record. However, Simplero has no Company or Account object, so contacts representing organizations must be synthesized into Twenty Company records during migration. We use the contact's domain field, a manual company_name field, or a customer-supplied mapping table to create Company records before Contact import. The twenty_company_id lookup on Contact is resolved at migration time. Any contact without a resolvable company affiliation becomes a standalone Contact without a Company link.

Simplero tags are flat key-value labels applied to contacts. We migrate them as a multi-select text custom field on the Twenty Contact object, with each distinct tag value mapped to a comma-separated entry. During scoping, the customer chooses whether tags are preserved as a single custom field or distributed across multiple boolean fields for segmentation. Segment membership (dynamic filter groups) migrates by exporting the full contact-to-segment membership table and reconstructing it as a Twenty View filter.

Simplero Segments are dynamic filter groups based on contact properties and tag combinations. We export the segment definition (filter conditions and operators) and recreate it as a Twenty CRM View with equivalent filter criteria. Segments with complex branching or date-based conditions may require simplification in Twenty's filter builder, which we document during scoping.

Simplero Deals (available on Skyrocket tier at $299/mo) map to Twenty CRM Opportunity. The Simplero deal stage maps to the Twenty opportunity stage, and the pipeline maps to the Twenty pipeline. We apply value mapping during scoping so that Simplero stage names (which vary by customer) match the Twenty stage values configured in the destination. Deal value, close date, owner, and notes migrate directly.

Simplero Products (courses, memberships, digital downloads, coaching programs, 1:1 sessions) encompass a broader product concept than Twenty CRM's default schema. We assess whether the customer uses Simplero Products primarily as enrollment access (in which case we document them as a custom object or custom field on Contact) or as sellable items with pricing (in which case we map to a Product-like custom object in Twenty). Product-type classification (course vs. membership vs. download) migrates as a category custom field.

Simplero Members are contacts with active access to a Product. Enrollment records track which member has access to which product and when. We migrate enrollments as a custom object in Twenty CRM with lookup relationships to Contact and to the Product custom object (or Contact if Products are stored as fields). Access start date, access end date, and enrollment status migrate as custom fields on the Enrollment custom object.

Simplero Order records include product, price, date, payment gateway, and refund status. We map these to a custom Order object in Twenty CRM with fields for order_id, product_reference, amount, currency, payment_gateway, refund_status, and order_date. Refund flags and partial payments require value mapping since Simplero uses specific statuses. If the customer uses Simplero primarily for membership billing rather than transactional orders, we assess whether Order records are needed or whether enrollment status is sufficient.

Simplero email broadcast content (individual emails sent to segments) does not have a structural equivalent in Twenty CRM, which is a CRM and not an email marketing platform. We export the email subject and body as a written record in the migration handoff document so that the customer can recreate key broadcast templates in their chosen email platform (Mailchimp, ConvertKit, or similar). This is not a data migration; it is a content inventory.

Simplero Flows (triggers, delays, branching conditions, and action chains) cannot be exported or accessed via API. We document the Flow structure during discovery by walking through each Flow in Simplero's UI: trigger event, step sequence, conditions, and actions. This document is delivered to the customer as a written handoff so their admin can rebuild each Flow in Twenty's visual workflow builder. Complex multi-step sequences require significant manual rebuild effort; we estimate rebuild hours during scoping so the customer can plan accordingly.

Simplero Help Desk tickets (subject, status, assignee, conversation thread) migrate to Twenty CRM Case. Ticket status maps to Case Status, assignee resolves to the matching Twenty User by email, and conversation threads migrate as Case Comments. Simplero's help desk is only available on Scale and Skyrocket tiers, so this object only exists for customers on those plans.

Simplero Owners map to Twenty CRM Users. We resolve owners by email match. Any Simplero Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Child accounts (Simplero Skyrocket feature) map to additional User records with appropriate workspace permissions set in Twenty.