Migrate from Marketing Creatio to Microsoft Dynamics 365 Sales

Creatio Account records map to Microsoft Microsoft Dynamics 365 Sales Account with name, industry, address, phone, and type fields. Accounts are imported first because Contacts, Opportunities, Cases, and Orders all reference the parent Account via a Lookup or Customer ID relationship. Microsoft Dynamics 365 Sales supports hierarchical billing and shipping addresses that require field-level decisions during the staging transform; we flag these for customer review before the Accounts phase begins.

Creatio Contact records migrate directly to Microsoft Dynamics 365 Sales Contact. The primary phone and email fields map to telephone1 and emailaddress1 respectively. We preserve the Account-Contact linkage by resolving AccountId from the Creatio Lookup during staging. Microsoft Dynamics 365 Sales does not use a separate primary-contact flag as Creatio does; we set the primary contact role via the Contact Business Rules or account-level defaults post-migration.

Creatio Lead records migrate as Microsoft Dynamics 365 Sales Lead. The Lead Status field maps from Creatio's status codes, and the CreationDate preserves the original timestamp. Any pre-conversion notes or activities on the Creatio Lead migrate as Tasks attached to the Lead. If a Creatio Lead has already been converted before migration, the resulting Contact and Account are migrated as standard records using the conversion timestamp preserved in the record.

Creatio Opportunity records map to Microsoft Dynamics 365 Sales Opportunity with Amount, Stage, Close Date, and OwnerId. The opportunity-account linkage is preserved via AccountId resolution. Microsoft Dynamics 365 Sales requires a price list (PriceListId) on Opportunities; we configure a default price list during schema setup and flag any opportunities without a matching price list for admin resolution. Closed-Won and Closed-Lost reasons from Creatio custom fields migrate as Opportunity close fields.

Creatio Orders migrate as Microsoft Dynamics 365 Sales Sales Orders linked to Account. Order line items require a separate import pass after the parent Order is created with a resolved price list. Microsoft Dynamics 365 Sales enforces a price list requirement on the order header, so we configure a default price list during schema setup and flag any orders without a matching price list for admin configuration. Referenced Products that do not exist in the destination are held in a reconciliation queue.

Creatio Cases migrate as Microsoft Dynamics 365 Sales Case records with Status, Priority, and Resolution preserved. The case status workflow maps to match the destination case lifecycle states, and any custom priority fields are mapped to the Case Priority picklist. Microsoft Dynamics 365 Sales requires a Case Title; for Creatio Cases that store subject and description separately, we concatenate these fields during the staging transform.

Creatio Products migrate as Microsoft Dynamics 365 Sales Product records with name, product number, default unit, and pricing information. Product bundles and pricing rules in Creatio do not automatically transfer; we document the bundle structure and pricing rule logic for the customer's admin to rebuild in Microsoft Dynamics 365 Sales using the product family and price list model. Standard Price Book entries are created during the import pass.

Creatio Marketing Campaigns migrate as Microsoft Dynamics 365 Sales Campaign records with campaign name, type, status, start and end dates, and target audience preserved. Audience segment definitions transfer as reference data or as static Marketing List membership. Automated triggers, email send schedules, and tracking pixels from Marketing Creatio do not migrate; we export the campaign taxonomy and segment filter logic as a written document for the customer to rebuild in Dynamics 365 Customer Insights Journeys.

Creatio Audience Segments define filter-based groupings of Contacts. Segment definitions migrate as reference data documenting the filter logic and field names used. Microsoft Dynamics 365 Sales does not have a native equivalent for behavioral filter-based segments; we recommend rebuilding segments in Dynamics 365 Customer Insights Journeys or maintaining segment logic as a documented reference for manual list building. The customer chooses the segmentation strategy during scoping.

Creatio custom objects built in the Creatio IDE require schema recreation in Microsoft Dynamics 365 Sales as custom entities. We pre-create the destination schema including all custom fields, data types, and Lookup relationships before any data import. Lookup columns referencing parent records that have not yet been imported are flagged in the staging layer and sequenced last to prevent constraint violations. Microsoft Dynamics 365 Sales does not use an IDE-based schema designer; schema is created via the Power Apps maker portal or the Advanced Find metadata export.

Creatio Activity records (Tasks, Events, and Calls) migrate as Microsoft Dynamics 365 Sales Task and Event records with subject, status, due date, and owner preserved. The activity-account and activity-contact linkages are preserved via WhatId and WhoId resolution. Activity templates and reminder configurations do not transfer; these are rebuilt by the admin post-migration. Activity history ordering is preserved by setting the Activity Date to the original Creatio timestamp.

Creatio Owner records are resolved by email match against the Microsoft Dynamics 365 Sales User table. Any Creatio Owner without a matching User in the destination org is placed in a reconciliation queue; the customer's Dynamics 365 admin provisions the missing User before record import resumes. OwnerId references are required on most standard objects, so this step gates the start of the production migration.

Creatio Tags are stored as comma-separated values or via a dedicated Tag object depending on the configuration. We extract tags as a custom text field and either populate a Microsoft Dynamics 365 Sales Topic entity with TopicAssignment records or store the tags as a multi-select text field on the Contact and Account records. The customer selects the tag strategy during scoping.