Migrate from Systeme IO to Twenty CRM

Systeme.io contacts migrate to Twenty People records. Standard fields (first name, last name, email, phone, job title) map directly. The company link in Systeme.io becomes a companyId lookup in Twenty — the Company record must exist first, so we migrate companies before contacts.

Systeme.io lifecycle stages such as subscriber, lead, and customer have no native equivalent field in Twenty CRM's data model. We resolve this by creating a custom select field named Lifecycle_Stage__c in Twenty's Settings → Data Model prior to the import. Every stage value present in Systeme.io is preserved exactly as stored, ensuring that any segmentation logic your team relies on remains intact after the migration. The custom field accepts the same enumerated values from the source system.

Systeme.io tags are comma-separated strings on the contact record with no native equivalent in Twenty. We create a Tags__c text field to hold the full tag list per contact. Teams that rely on tag-based segmentation will need to redesign their tagging logic in Twenty's custom-field model.

Systeme.io companies map directly to Twenty Companies. Domain maps to the website field, industry to the industry pick-list (value-by-value), and employee count to the numberOfEmployees field. Social handle URLs that do not map to named website fields are preserved in a custom text field.

Each Systeme.io pipeline's stage labels map to Twenty Opportunity Stage values. We create a custom Stage__c select field on the Opportunity object with options matching Systeme.io's stage names exactly. Probability percentages associated with each stage are stored as a companion custom field for reporting continuity.

Systeme.io deal amount (stored as a numeric value) maps directly to the Opportunity amount field in Twenty. The deal close date transfers to the closeDate date field, preserving the original temporal data. Currency denomination from Systeme.io carries over unchanged, maintaining financial accuracy. For organizations operating across multiple currencies, the Twenty administrator must configure currency settings in the workspace before the import process begins to ensure proper display and reporting.

Systeme.io engagement records (calls, emails, meetings) migrate as Twenty Tasks with Type set to Call, Email, or Meeting respectively. Original timestamps and the engagement title become the Task subject. Note that Systeme.io stores some activity data in proprietary formats that may require pre-export formatting before the CSV import can accept them.

Systeme.io notes migrate as Twenty Notes. Body text is preserved as-is. Inline images embedded in Systeme.io notes are downloaded and re-hosted as Twenty file attachments. Rich-text formatting that cannot be rendered in Twenty's plain-text note body is flagged in the pre-migration diff.

Any Systeme.io custom objects map 1:1 to Twenty custom objects. N:N relationships between custom objects in Systeme.io require junction objects in Twenty. We surface these relationships in the migration plan so your Twenty admin can pre-create the junction schema before the import run.

Systeme.io automation rules, funnel-based sequences, and tag-triggered workflows do not have a functional equivalent in Twenty CRM. The migration carries a machine-readable export of every automation definition so your Twenty admin can use it as a rebuild reference when configuring Twenty Workflows.