Migrate from Sales Creatio to Twenty CRM

Creatio Accounts (companies) map directly to Twenty Companies. Standard address, industry, type, and ownership fields map to their Twenty equivalents. The company name becomes the primary dedupe key during import. Twenty's Company object supports custom fields added via Settings → Data Model before import. Account owner assignment maps to Twenty workspace Members resolved by email match.

Creatio Contacts map to Twenty People. Name, email, phone, and communication preferences migrate directly. The link to the parent Account becomes the link to the Twenty Company. We resolve the Company reference before Contact insert so that the relationship is satisfied at migration time. Any lifecycle-stage or ownership field maps to a custom field on People if the customer has configured one in their Creatio instance.

Creatio Leads are distinct from Opportunities until conversion. We migrate Lead records as Twenty People, preserving Lead source, status, rating, and conversion date. If the customer requires a distinct pre-conversion object in Twenty, we map Leads to a custom People status field rather than creating a separate Lead object since Twenty does not have a native Lead object equivalent to Salesforce or Creatio.

Creatio Opportunities map to Twenty Opportunities. Pipeline stage names, amount, probability, and close date migrate. Stage names are fully customizable per Creatio organization, so we extract the active pipeline configuration during discovery and map stage names to Twenty Opportunity stage values. Close date and amount migrate as-is; probability migrates to a custom field if Twenty's standard stage probabilities do not match the source.

Creatio Activities (calls, emails, meetings, tasks) require disaggregation in Twenty because Twenty uses separate Task and Note objects rather than a unified Activity composite. Call dispositions and durations map to Task records with a call subtype custom field. Meeting details (location, attendees, time) map to Event records or to Notes with an activity flag. Emails migrate as Note records linked to the parent Company or People record. The original Creatio Regarding lookup links to the parent Company or People in Twenty.

Creatio Cases (service tickets) have no direct equivalent in Twenty CRM's standard object set. We create a custom object named Case in Twenty's Data Model with fields for status, priority, owner, linked Company, and resolution notes. SLA timer fields require manual reconfiguration in Twenty since Twenty does not have native SLA enforcement. Case types that were custom dropdowns in Creatio map to select options in the Twenty custom object.

Creatio Orders link to an Account and contain line items referencing Products. Twenty has no native Order object, so we create a custom Order object with fields for order date, status, total amount, and linked Company. Order line items require a separate custom LineItem object with a lookup to the Order parent and a Product reference if the customer maintains a product catalog.

Creatio Products carry pricing, unit type, and tax categories. We create a custom Product object in Twenty with fields for name, SKU, price, unit type, and tax category. Bundle and pricing rule support depends on the customer's use of Creatio's advanced pricing engine; these require manual rebuild in Twenty since no pricing rule automation migrates as code.

Creatio custom objects created in Studio have user-defined schemas that vary per instance. We perform a schema discovery pass during scoping, extract the complete field list with data types, and create matching custom objects in Twenty's Data Model before any data import. Lookup fields within and across custom objects require pre-creation of the target object and field so that the lookup reference resolves during insert. This phase typically extends the timeline by one to two weeks for instances with more than five custom objects.

Both standard and custom objects in Creatio can have user-added fields with custom data types (dropdowns, lookups, checkboxes, text, number). We map each field type to its nearest Twenty equivalent. Lookup fields require a separate target-record resolution step since Twenty resolves lookups by record ID rather than by string reference. Select and multi-select fields in Creatio map to Twenty select options configured in Settings → Data Model before import.

Creatio BPM workflows encode logic in a proprietary internal process engine format with no export path to any other CRM. We export every active BPM workflow as a reference document containing screenshots, step sequences, condition logic, and action descriptions. The customer uses this document to rebuild workflows in Twenty's workflow builder or through a developer extension. This scope item must be agreed before migration begins because the document production adds time and must be reviewed by the customer's process owners.

Files in Creatio can be stored in the database or in external storage (AWS S3, Azure Blob). On-site Creatio instances use the FileMigrator utility to extract files to S3 and re-link them. Cloud Creatio instances require opening a support ticket with Creatio to initiate file extraction. We factor the file extraction path into the migration timeline and identify file-heavy objects during the data audit phase. Once extracted, files are re-linked to their parent records in Twenty on the customer's self-hosted infrastructure.