Migrate your Creatio data

Standard Contacts object with a full set of address, industry, and lookup fields. We map it 1:1 to the destination Account/Company object and preserve all lookup relationships to Contacts and Cases.

Primary customer record. Creatio stores it as a base entity schema with support for simple fields, calculated fields, and multicurrency fields. We preserve lifecycle stage and owner assignment during migration.

Service Cases are tracked as distinct records with status, priority, resolution SLA fields, and a lookup to the originating Contact and Account. We map Case status values explicitly to avoid silent status drift at the destination.

Creatio supports Call, Email, and Task activity types stored under a unified Activity schema. We separate these by type at writeback so the destination receives correctly typed activity records rather than a generic activity object.

Deals/opportunities carry stage, amount, probability, and close date. Creatio's pipeline is configurable per product line, so we capture the active pipeline schema and map stage names explicitly rather than relying on ordinal position.

Lead object feeds the marketing funnel before conversion into a Contact and/or Opportunity. We preserve Lead status and source fields as custom Contact properties when the destination CRM lacks a native Lead object.

Products carry price lists, bundle structures, and unit-of-measure fields. Creatio supports multi-currency product pricing, which requires explicit currency mapping during writeback to avoid rounding errors.

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 destination table or object before migration.

Custom fields extend base schemas across Accounts, Contacts, Cases, and Opportunities. Field type mapping is critical: Creatio distinguishes simple, image, calculated, and multicurrency field types, each requiring a different writeback strategy.

Creatio v8.3.2+ uses a File API that stores files either in the database or externally (S3/Azure Blob). We detect the storage mode during discovery and redirect file writes to match the destination's attachment handling approach.

Creatio Pipelines are configurable per product line with named stages. We extract the full pipeline definition including stage order, stage names, and any automation triggers before writing Opportunities to the destination pipeline.

Creatio Users are assigned as record owners. We build a user lookup map at migration start so owner IDs are translated to the destination system's corresponding user records rather than orphaned.