Migrate from Marketing Creatio to Twenty CRM

Creatio Contacts migrate to Twenty CRM People. We map Name, Email, Phone, Job Title, and Address fields to their Twenty equivalents. The Creatio Contact-Account Lookup relationship (linking each Contact to a parent Account) migrates as a relation field on the Twenty Person record pointing to the migrated Company. Owner assignments from Creatio's UserId Lookup require the recipient User to exist in Twenty before import; we flag any Contact with an unmapped Owner for admin provisioning.

Creatio Accounts map to Twenty CRM Companies. The Account-Contact chain is preserved: we import Companies first, then resolve the Account ID on each Contact during the Person import phase. Account type, industry, annual revenue, and address fields map to their Twenty Company equivalents. Companies must load before any Contact import because the Person-Company relationship is required at insert time.

Creatio Leads represent pre-conversion prospects and carry Status and ConversionDate fields. We map Leads to Twenty People records with a note flagging their pre-conversion status. The original Lead status value is preserved in a custom field on the Person for segmentation. If the customer requires a separate Lead concept in Twenty, we configure a Custom Object with status workflow during schema setup.

Creatio Opportunities map directly to Twenty Opportunities. Amount, Stage, Close Date, and Owner migrate as standard fields. The Opportunity-Account Lookup resolves to the migrated Company during staging. Stage values are configured as picklist options in Twenty before import. If Creatio Opportunity records reference a Product, we flag those for Custom Object or Product mapping scope.

Creatio Cases are standard objects with Status, Priority, and Resolution fields linked to Contacts and Accounts. Twenty CRM does not ship a native Case object. We create a Custom Object named Case in Twenty via the /metadata API, define Status and Priority picklist fields, and import Case records with their Contact and Account lookups resolved to migrated Person and Company records.

Creatio Orders are transactional records linked to Accounts, Contacts, and Products via Lookups. Twenty has no native Order object. We create a Custom Object named Order with Order Date, Total Amount, and Status fields via the /metadata API. Product references that lack a migrated Product counterpart are flagged as broken Lookups for admin review before Order import begins.

Creatio Products define items sold and appear in Orders and Opportunities. We create a Product Custom Object in Twenty with Name, SKU, Unit Price, and Description fields. Product bundles are flagged for manual reconstruction in Twenty because bundle pricing logic does not transfer. If the customer does not use product-based selling, Products are archived rather than migrated.

Creatio custom objects are discovered via schema export or Creatio's Configuration section since there is no self-service discovery API. Each custom object schema is translated to Twenty's /metadata API call: we create the Object, then its Fields with type information (text, number, date, select, relation). Lookup columns from Creatio custom objects that reference standard objects are resolved to migrated record IDs in the staging layer before loading.

Creatio Activities including Tasks, Events, and Calls link to Contacts, Accounts, and Cases via Lookup. Twenty CRM represents all activity types as Task records. We map Creatio Tasks to Twenty Tasks with Subject, Due Date, Status, and Body fields. Creatio Events map as Tasks with a date range field. Creatio Call disposition and duration become custom Task fields. Each activity's parent record (Contact or Account) resolves to the migrated Person or Company during staging.

Creatio tags are stored as comma-separated values or a dedicated Tag object depending on configuration. We extract tags as a custom text array field on each object. In Twenty, we create a multi-value text field on the relevant object via /metadata and import tag values as an array. The customer chooses at scoping whether tags apply to Person, Company, Opportunity, or all three.

File attachments on Creatio Contacts, Accounts, Cases, and other records must be exported separately from the record data. We export attachments to a structured file store with a manifest linking each file to its parent record by ID. Post-import in Twenty, we re-link attachments by re-uploading via Twenty's attachment mechanism or documenting the file store location on each record's description field for manual re-attach if Twenty's attachment API does not support bulk re-link.

Creatio assigns Owner (User) records to Opportunities, Cases, and other objects via UserId Lookup. We extract every distinct Owner referenced on migrating records and match by email against the Twenty workspace Members list. Members must be invited and active in Twenty before any Owner references can be mapped. Any Owner without a matching Twenty Member is placed in a reconciliation queue for the customer's admin to provision before that object's import phase begins.