Migrate from Factoreal to Twenty CRM

Factoreal Contact records map to Twenty CRM Person objects. We extract contact profiles from CSV including name, email, phone, and custom fields, then transform them to Twenty's Person GraphQL mutation format. Factoreal's source attribution fields (how the contact entered the system) migrate as text fields on the Person record. Any duplicate detection runs against email as the canonical dedupe key before insert.

Factoreal custom fields on Contact records map to identically named custom fields on Twenty CRM's Person object. We identify all custom field definitions during discovery, export their per-record values from the CSV, and create matching custom fields in Twenty's Settings → Data Model before import. Field type mapping (text to text, number to number, date to date) is validated against the CSV header values to catch formatting mismatches early.

Factoreal Segments are defined by filter rules on contact attributes and behavioral events. We extract segment membership logic as written filter criteria during the discovery phase, then create equivalent saved Views in Twenty CRM. Each View is named to match the original segment and scoped to the Person object with matching filter conditions. Segment membership (which contacts belong to which segment) is preserved by assigning a multi-select picklist or tag-style field to each Person rather than as a native segmented list object.

Factoreal tags on contacts migrate to Twenty CRM tags on the Person record. We export the full tag list per contact from CSV and create matching tags in Twenty, preserving the many-to-many relationship across both systems. Tag names are normalized (lowercase, stripped of special characters) to ensure consistent matching.

Factoreal company data (if stored as a related record rather than fields on Contact) maps to Twenty CRM Company. We extract company name, domain, address, and industry from the CSV export and create Company records before any Person records that reference them, satisfying the lookup dependency at migration time.

Factoreal Campaign records hold subject, content, send history, and engagement metrics. The campaign structure maps partially to Twenty CRM's Opportunity model for pipeline tracking, but Factoreal's campaign engagement data (open rates, click rates, send timestamps) does not have a direct Twenty CRM equivalent. We preserve open and click metrics as custom number fields on the Opportunity record, and campaign send history as Activity notes for attribution purposes.

Individual campaign send events map to Twenty CRM Activity or Task records linked to the relevant Person. We preserve send timestamp, direction (outbound), and content reference. Inbound replies and bounces map to inbound Activity records with a type discriminator field.

Factoreal SMS and WhatsApp message logs export as part of campaign and contact data. We preserve send timestamp, direction, and message content as Activity records in Twenty CRM's timeline, using a type discriminator (SMS or WhatsApp) on the Activity record. The Person lookup ties each message to the correct contact record.

Factoreal automation workflows define trigger conditions and multi-step action sequences across channels. These are not stored in a portable exportable format. We document the full workflow graph — triggers, conditions, delays, and action steps — as a written specification that the customer's admin uses to manually configure equivalent logic in Twenty CRM or an external automation tool. This is scoped as a parallel workstream outside the data migration.

Factoreal email templates include HTML content and dynamic merge field placeholders. We extract template HTML from the CSV or application export, convert merge field syntax to a generic placeholder format, and store the result as a Note attached to a dedicated Template reference record in Twenty CRM. Visual rendering and dynamic personalization logic do not migrate as executable template code.

Factoreal's built-in e-commerce integration captures order and product data. These map to Twenty CRM as custom objects (e.g., Product and Order) that we design and create in the destination schema before migration. Order records reference the Person (customer) and include line item data, transaction amounts, and dates. Product records include SKU and description. This mapping requires custom field schema creation in Twenty's Data Model during the schema design phase.

Factoreal users and owners referenced on contacts, campaigns, and automations map to Twenty CRM WorkspaceMembers. We extract owner email addresses from the CSV and match them against Twenty workspace members. Any owner without a matching workspace member is held in a reconciliation queue for the customer's admin to provision before Person record import resumes.