Migrate from Creatio to Microsoft Dynamics 365 Sales

Creatio Account records map directly to Dynamics 365 Account. We preserve the full set of address fields, industry classification, annual revenue, number of employees, and any custom fields as typed columns in Dynamics. The Account is created first so that AccountId is available as a foreign key when Contact and Opportunity imports run. If Creatio stores multiple contact persons per Account as separate AccountContactRelation records, we flatten these into the primary Contact lookup on Account and create additional Contact records with the AccountId set.

Creatio Contact records map to Dynamics 365 Contact. We map firstname, lastname, email address, phone, mobile phone, job title, and address fields directly. Creatio's lifecycle stage and owner assignment migrate as custom fields on Contact because Microsoft Dynamics 365 Sales does not have a native lifecycle stage concept. Owner resolution runs by email match against the Dynamics User table, with unresolved owners held in a reconciliation queue.

Creatio Opportunity (Deal) records map to Dynamics 365 Opportunity. The dealstage maps to a Dynamics Sales Process stage value that we configure during schema design. The active Creatio pipeline definition, including stage names and probabilities, becomes a Dynamics Record Type and Sales Process pair. Close date, estimated revenue, and probability percentage migrate directly. If Creatio stores close reason or lost reason as custom fields, these map to Dynamics custom fields on Opportunity.

Creatio Cases map to Dynamics 365 Case. Case status values (New, Open, Pending, Resolved, Closed) map explicitly to Dynamics Case Status option set values rather than relying on integer position. Priority, origin (Email, Phone, Web), and SLA fields migrate as typed fields. The lookup from Case to originating Contact and Account is resolved at migration time using the Account and Contact record IDs established in the first two phases.

Creatio Activity records with type Call map to Dynamics 365 Task with TaskSubtype set to Call. Call disposition, duration in seconds, and any recording URL stored as custom fields migrate to equivalent custom fields on Task. ActivityDate preserves the original Creatio timestamp to maintain timeline ordering. The WhoId (Contact or Lead lookup) and WhatId (Account or Opportunity lookup) are resolved from the ID maps built during earlier phases.

Creatio Activity records with type Email map to Dynamics 365 EmailMessage records for the email content plus a Task record for the activity timeline entry. Email body, subject, from address, and to address migrate to EmailMessage. The Task record provides the visible entry in the activity timeline with ActivityDate set to the original Creatio timestamp. EmailMessage is linked to the Contact or Lead via the EmailMessage.partyid_parentcolumnid relationship.

Creatio Activity records with type Task map to Dynamics 365 Task with the relevant TaskSubtype (General). Subject, description, due date, status, and priority migrate directly. OwnerId is resolved by email lookup against the Dynamics User table. The WhatId links to the related Account or Opportunity where applicable.

Creatio Lead records map to Dynamics 365 Lead. Lead status, source, rating, and estimated revenue fields migrate directly. Any lead scoring value stored in a custom field carries over to a custom field on the Dynamics Lead. The Lead is not automatically converted during migration; conversion is a post-migration step that the customer's admin executes after validating the mapped data in production.

Creatio Products map to Dynamics 365 Product2. Product name, SKU, product description, and unit of measure migrate. If Creatio stores product pricing with multicurrency values, we resolve the TransactionCurrencyId to the Dynamics currency record matching the Creatio currency lookup before writing. Standard Price Book entries are created during the Products phase so that PricebookEntry records are available when Opportunity Line Items are written.

Creatio custom objects built in the Object designer are reverse-engineered from the exported package schema. We extract each custom object's column definitions, field types, and lookup relationships, then pre-create the corresponding custom entity in the Dynamics solution before any data import begins. Custom field types (simple, image, calculated, multicurrency) are mapped to their closest Dynamics equivalents. Calculated fields are flagged and skipped as static data writeback because Dynamics 365 calculates them at display time, not as stored values.