Migrate your Sales Creatio data

Accounts (companies) in Creatio have a stable schema with standard address, industry, type, and ownership fields. We map them 1:1 to Accounts or Companies in the destination CRM, preserving the primary contact lookup and any custom columns.

Contacts carry name, email, phone, communication preferences, and a link to their parent Account. Lifecycle stage and owner assignment are standard fields we carry forward as-is.

Leads in Creatio are distinct from Opportunities until converted. We preserve the Lead source, status, rating, and conversion date fields and map them to Leads or Contacts in the destination based on the target object's lifecycle.

Opportunities have a pipeline stage, amount, probability, and close date, but stage names are fully customizable per organization. We extract the active pipeline configuration and map stage names explicitly rather than by position.

Cases (service tickets) have a status, priority, owner, and linked Account/Contact. Resolution notes and SLA timers are standard fields we migrate directly; custom case types require field-level mapping.

Activities cover tasks, calls, emails, and meetings linked to any parent object. The activity type enumeration varies between editions; we normalize types and preserve the Regarding (lookup) relationship to the parent record.

Orders link to an Account and contain line items referencing Products. We migrate order headers and line items separately, maintaining the order-to-product lookup relationship.

Products carry pricing, unit type, and tax categories. We migrate the product catalog as a standalone object; bundle and pricing rule support depends on the destination's data model.

Custom objects created in Studio have user-defined schemas that vary per instance. We perform a schema discovery pass, extract the field list, and map each field type to its nearest equivalent in the target CRM.

Both standard objects and custom objects can have user-added fields with custom data types (dropdowns, lookups, checkboxes). We map each field type explicitly; lookup fields require a separate target-side lookup table to exist or be created.

Creatio's BPM (business process management) workflows encode logic in Creatio's internal process engine format. This format is not portable to other CRMs and must be manually rebuilt in the destination. We export workflow configurations as documentation to guide the rebuild.

Files can be stored in the Creatio database or in external storage (AWS S3, Azure Blob). On-site instances can migrate files via the FileMigrator utility; cloud instances require Creatio support to initiate the file export. We coordinate this as a separate phase.

Dashboards built in Classic UI require the separate Dashboards Migrator app (Marketplace) to transition to Freedom UI. Standard section dashboards and custom ones can be migrated selectively. We extract dashboard definitions and re-implement them in the target BI layer.

Creatio user records include email, role, and organizational unit. Owner assignment on records links to these users. We map users to their counterparts in the destination by email and flag any orphaned assignments for resolution.