Migrate from Creatio to Twenty CRM

Creatio Accounts map directly to Twenty CRM Companies. The Account Name, Industry, Website, Phone, and Address fields map 1:1 to their Twenty Company equivalents. Account Type and Owner fields map to Company.annualRecurringRevenue (if applicable) and Company.createdByWorkspaceMember respectively. We extract the full column map from the Creatio package schema during discovery and create corresponding Twenty Company fields before importing any records. Company creation precedes all Contact imports to satisfy the twenty_crm_company__c lookup on Contact.

Creatio Contacts map directly to Twenty CRM Contacts. Core fields including Name, Email, Phone, JobTitle, and Address map 1:1. Creatio's lifecycle stage property (simple field type) maps to a custom Contact field that we create in Twenty during schema provisioning. Owner assignment maps to Twenty's createdByWorkspaceMember lookup via the User lookup map built at migration start. We flag calculated fields and multicurrency fields during field mapping and skip static value writeback for the former.

Creatio Opportunities map to Twenty CRM Opportunities. Stage, Amount, Probability, and Close Date migrate directly. Creatio's configurable pipeline per product line requires explicit stage name mapping; we extract the active pipeline definition including stage order and stage names during discovery and configure corresponding Twenty Opportunity stages before migration. Close Lost and Close Won dates from Creatio become Opportunity.closeDate and a custom closedAt__c field.

Creatio Cases represent service records with status, priority, and resolution SLA fields. Twenty CRM does not have a native Case object, so Cases require a decision during scoping: map to a custom Opportunity variant with Case-type fields, or map to Twenty's generic Opportunities with a type discriminator field and custom status picklist. We preserve Case status values as custom Opportunity status values, priority as a custom priority field, and the originating Contact and Account lookups as Opportunity contacts and company links. The customer chooses the Case strategy during discovery.

Creatio Activities with type=Call map to Twenty CRM Call records. We separate by type at extraction time using Creatio's Activity.Type field so that calls land as first-class Call records rather than generic tasks. Call duration, disposition, and outcome migrate to custom Call fields. ActivityDate from Creatio sets the Call startTime for timeline ordering. The Call's WhoId maps to the resolved Twenty Contact lookup and WhatId to the related Opportunity or Company.

Creatio Activities with type=Email map to Twenty CRM Email records. Email subject, body, from address, and to address migrate as Email fields. Thread ID and message ID from Creatio migrate to custom Email fields to preserve email threading context. Attachments on emails migrate as Twenty EmailAttachment records linked to the parent Email. We handle the email direction (inbound/outbound) via a custom direction__c field.

Creatio Activities with type=Task map to Twenty CRM Task records. Subject, Status, Priority, ActivityDate, and description migrate directly. Task assignment migrates by resolving Creatio Owner ID to the Twenty workspaceMember lookup built during owner reconciliation. Reminder and recurrence settings are not migrated; these are recreated in Twenty's task model.

Creatio Leads feed the marketing funnel before conversion. If Twenty CRM lacks a native Lead object at the customer's target tier, we map Leads to Twenty Contacts with a custom leadSource__c field and a conversionStatus__c flag that marks the record as pre-conversion. When Twenty's native Lead object is available, we map directly. Lead status and source fields migrate as custom Contact fields. Conversion history is preserved as a note or custom activity record.

Creatio Products carry price lists, bundle structures, and unit-of-measure fields with multi-currency pricing. Twenty CRM does not ship a native Product2-style object in all configurations, so we evaluate during discovery whether Twenty's native Opportunity line items suffice or whether a custom Product object needs provisioning via the Twenty /metadata API. Multi-currency pricing fields from Creatio require explicit currency mapping to avoid rounding errors; we handle currency conversion and store the base currency value and currency lookup separately.

Creatio's entity schema system allows arbitrary custom objects built in the Object designer. We reverse-engineer each custom object's column map from the exported package schema and generate a corresponding Twenty CRM custom object via the /metadata API. All columns, data types, and lookup relationships are translated to Twenty equivalents. Lookup dependencies (custom objects referencing Accounts or Contacts) are resolved in dependency order; parent objects must exist before child object import begins.

Creatio v8.3.2+ uses a File API that stores files either in-database or externally on S3/Azure Blob. We detect the UseEntityFileApi storage mode flag during environment discovery and route extraction accordingly. For in-database storage, we export via Creatio's Excel export and binary file extraction. For external S3/Azure Blob, we download directly from the configured bucket, then write to Twenty's attachment storage. Missing this detection step causes attachments to land as null or broken links in Twenty.

Creatio Pipelines are configurable per product line with named stages. We extract the full pipeline definition including stage order, stage names, probability percentages, and any automation triggers during discovery. Each pipeline maps to a Twenty Opportunity stage configuration. Stage probability percentages round to Twenty's allowed precision. The customer reviews and approves stage mapping before migration of any Opportunity records.