Migrate from Sales Creatio to Microsoft Dynamics 365 Sales

Creatio Accounts map directly to Microsoft Microsoft Dynamics 365 Sales Account records. The Account Name, Website, Industry, Address fields, and Account Type (Customer, Prospect, Vendor) migrate as text and picklist fields. We use Account Name as the dedupe key during import. Owner assignment migrates by resolving the Creatio owner email to a Dynamics 365 User by email match.

Creatio Contacts map to Dynamics 365 Contact records linked to their parent Account via the ParentAccountID lookup. Name, Email, Phone, Job Title, and Communication Preferences migrate as standard Contact fields. Lifecycle stage (lead, marketing qualified, sales qualified, customer) from Creatio is preserved in a custom field creatio_lifecycle_stage__c for audit and segmentation continuity.

Creatio Leads that have not been converted map to Dynamics 365 Lead records. Lead source, status, rating, and conversion date migrate as standard and custom fields. Any Lead that was partially converted in Creatio (has a conversion timestamp but no resulting Contact) is flagged in a reconciliation report for the customer admin to manually resolve in Dynamics 365 before final validation.

Creatio Opportunities map to Dynamics 365 Opportunity records. Pipeline stage names from Creatio's customizable stage matrix map to a pre-configured Microsoft Dynamics 365 Sales Process with matching stage values and probability percentages. Close Date, Amount, Probability, and Description migrate directly. The parent AccountId and OwnerId are resolved via lookup before Opportunity insert.

Creatio Cases (service tickets) map to Dynamics 365 Case records. Case status, priority, owner, and linked Account/Contact are migrated with the Regarding field resolved to the target Contact and Account records. Resolution notes and SLA timer values migrate to custom fields on Case if the destination org uses Service Cloud features.

Creatio Activity records of type Task map to Dynamics 365 Task records. Subject, Status, Priority, ActivityDate, and Description migrate as standard fields. The Regarding (lookup) relationship resolves to the target Contact, Account, or Opportunity record ID after parent lookup is complete.

Creatio Call activity records map to Dynamics 365 Task with TaskSubtype set to Call. Call disposition, duration in seconds, and any notes migrate to custom Task fields. Activity timestamp is preserved in the ActivityDate field to maintain timeline ordering.

Creatio Email activities map to Dynamics 365 EmailMessage records linked to a Task entry in the Activity timeline. The EmailMessage stores subject, body, from, and to addresses. The Task provides the WhoId (Contact or Lead) and WhatId (Account or Opportunity) for timeline display. Email direction (inbound/outbound) is preserved in a custom field.

Creatio Meeting activities map to Dynamics 365 Event records with StartDateTime, EndDateTime, Location, and Subject preserved. Attendees resolve to EventRelation records linked to the corresponding Contacts, Leads, and Users in the destination.

Creatio Orders map to Microsoft Dynamics 365 Sales Order records. Order headers carry Account, date, and status; order line items map to SalesOrderDetail records referencing Products. We resolve the Pricebook2 reference and Product2 IDs during migration. If the destination uses Project Service Automation or Field Service add-ons, order-to-project linking is preserved in custom fields.

Creatio Products migrate to Dynamics 365 Product2 records with Name, Product Number (from SKU), Unit, Price, and Description. Standard Price Book entries are created during import. Bundle and pricing rule support depends on whether the destination org has CPQ configured; we document any unsupported pricing rules in the migration report for admin review.

Creatio custom objects created in Studio have user-defined schemas that vary per instance. We perform a schema discovery pass that extracts every custom object's field list, field type, and lookup relationship, then maps each to an equivalent Dataverse custom table and column. All custom entity names are normalized to meet Dataverse naming conventions (alphanumeric, no spaces). Lookup fields to standard entities (Account, Contact, Opportunity) are resolved during the parent-record phase after the standard entity import completes.