Migrate your Marketing Creatio data

Contacts is the primary person record in Creatio. Standard fields include Name, Email, Phone, Job Title, and Address. The CanExportGrid permission governs export access. We migrate Contacts 1:1 and preserve relationships to Account via the AccountId Lookup column.

Accounts are the company/organization records linked to Contacts and Opportunities via Lookup columns. We maintain the account-contact linkage explicitly during migration to prevent orphaned contact records in Creatio.

Creatio's Lead object captures unqualified prospects before conversion to Contacts. Leads carry a Status field and ConversionDate. We map the lead status values to match the destination environment's picklist so scoring and routing data survives transfer.

Opportunities in Creatio represent sales deals with fields for Amount, Stage, Close Date, and Owner. They are linked to Accounts via Lookup. We preserve the opportunity-account linkage and stage values, mapping custom stage names where the destination uses different terminology.

Cases represent customer service or support records. Creatio stores Cases with Status, Priority, and Resolution fields. We map the case status workflow to match the destination's case lifecycle, as stage names vary between implementations.

Orders are transactional records linked to Accounts, Contacts, and Products. Creatio enforces referential integrity on these Lookups. We flag Orders that reference Products not included in the migration scope, as unlinked Order records will cause constraint errors.

Products define the items sold and are used in Orders, Order Line Items, and Opportunities. We map the product catalog and identify any product bundles or pricing rules that require manual reconfiguration in the destination.

Marketing Creatio Campaigns are automation workflows tied to specific audiences over defined periods. Campaign configuration, audience segments, and email templates migrate but marketing automation triggers and third-party tracking pixels do not transfer and must be rebuilt.

Audience Segments in Marketing Creatio define groups of Contacts based on filters and behavioral data. Segment definitions require review post-migration as filter logic may reference field names or picklist values that differ in the destination CRM.

Creatio's Object type schema allows unlimited custom objects built in the Creatio IDE. Custom objects often carry Lookup relationships to standard objects. We discover the full schema via Creatio's metadata and map each custom object's fields individually, flagging any Lookup columns that point to unmigrated parent records.

Creatio supports tag-based classification across objects. Tags are stored as comma-separated values or via a dedicated Tag object depending on configuration. We extract tags as a custom text property to ensure compatibility with the destination system.

File attachments on Contacts, Accounts, Cases, and other records must be exported separately from the record data. We export attachments to a file store and re-link them post-import using Creatio's document management references.

Creatio assigns Owner (User) records to Opportunities, Cases, and other objects via a UserId Lookup. We map the owner user list and flag any owner assignments where the user does not exist in the destination environment, defaulting to an admin placeholder.

Activities include Tasks, Events, and Calls logged against Contacts, Accounts, and Cases. We map activity records with their due dates, statuses, and assigned owners, noting that activity templates and recurring activity rules require manual reconfiguration.