Migrate from Marketing Creatio to Salesforce Sales Cloud

Creatio Contact maps directly to Salesforce Contact with standard fields (Name, Email, Phone, JobTitle, MailingAddress) migrated 1:1. The Creatio AccountId Lookup resolves to Salesforce AccountId on Contact. We extract the contact's primary Address record from Creatio and populate Salesforce Contact address fields. Owner resolution uses email matching against the Salesforce User table.

Creatio Account maps to Salesforce Account with Name, Website, Industry, Type, and BillingAddress migrated 1:1. Account is imported before Contact to satisfy the AccountId foreign key. Creatio's primary Contact relationship is preserved via the Contact's AccountId reference after Account insert completes. Address data from Creatio's Account-detail section populates the Account's billing and shipping address fields.

Creatio Lead (pre-conversion prospects) maps to Salesforce Lead. The Creatio Lead Status and ConversionDate fields determine whether a record should migrate as a Lead or a Contact-Account pair; we apply the customer's conversion rules during the transform phase. Any lead scoring value in Creatio custom fields migrates to a custom Salesforce Lead field hs_lead_score__c for audit continuity.

Creatio Opportunity maps to Salesforce Opportunity with Amount, StageName, CloseDate, and Owner preserved. The Creatio AccountId Lookup resolves to the Salesforce AccountId via the Account migration mapping. Stage values are validated against the destination Salesforce Sales Process stage whitelist; non-matching values are remapped to the nearest equivalent or flagged for pre-migration Sales Process configuration.

Creatio Case maps to Salesforce Case if the destination org includes Service Cloud or Sales Cloud. Case Status, Priority, and Resolution migrate directly; Case Origin maps from the Creatio Case channel field. We validate the destination Case Record Type and Status picklist values match the source before migration; if they do not, we document the status mapping matrix for the customer's admin to configure before load.

Creatio Product records map to Salesforce Product2 with Name, ProductCode (from Creatio's SKU field), Description, and Family migrated. Standard Pricebook entries are created during migration so that Products can be attached to Opportunities via OpportunityLineItem without pricebook errors. Custom pricing rules on Products (volume discounts, tiered pricing) are flagged as manual-rebuild items for Salesforce CPQ if required.

Creatio Order records map to Salesforce Order (available on Enterprise and Unlimited or via the Order Management add-on). The AccountId, ContractId, and Products references are resolved via the Account and Product2 mapping. Order Status migrates to Salesforce OrderStatus; effective and completion dates migrate as OrderEffectiveDate and EndDate. We flag any Orders referencing Products not included in the migration scope to prevent constraint violations.

Creatio Activities (Tasks, Events, Calls) map to Salesforce Task and Event objects. Task records carry Status, Priority, ActivityDate, and Subject; Event records carry StartDateTime, EndDateTime, Location, and WhatId. The WhoId on each Activity is resolved to the migrated Lead or Contact Salesforce ID via email matching. Creatio's activity sub-types (phone call, meeting, email) map to Salesforce TaskSubtype and Event Type fields.

Creatio Marketing Campaigns migrate as Salesforce Campaign records with Campaign Name, Type, Status, StartDate, and EndDate preserved. Campaign Member records (Contacts in the Creatio audience) migrate to CampaignMember with Status values mapped to the destination CampaignMemberStatus. Campaign budget data migrates if present. Automation triggers, email send schedules, and Journey Builder-style sequencing do not migrate; we export the full campaign taxonomy and audience segment definitions as a reference document for the customer's admin to rebuild in Salesforce Flow or Marketing Cloud Account Engagement.

Creatio Audience Segments (filter-based contact groups) migrate as Salesforce Campaign records with the segment criteria exported as a reference JSON file. The actual segment members (the filtered Contact records) are already migrated as Salesforce Contacts and appear in the Campaign via CampaignMember. Segment filter logic referencing field names or picklist values unique to Creatio may require adjustment post-migration; we document the full filter tree for the admin's review.

Creatio tags stored as comma-separated values or a dedicated Tag object migrate to Salesforce multi-select picklist fields on the relevant object (Contact, Account, Opportunity). If the customer uses tags for content classification rather than CRM categorization, we map them to Salesforce Topics with TopicAssignment records. The customer selects the tag strategy during scoping before migration begins.

Creatio custom objects built in the Object type schema migrate to Salesforce custom objects with __c API names matched to the Creatio schema name. We pre-create the destination schema in a Salesforce Sandbox first: all custom fields with type-mapped Salesforce field types, lookup relationships to standard objects, and validation rules. Custom object migrations run last because their Lookup columns often reference Account, Contact, or Opportunity records already migrated. Any Lookup columns pointing to records not included in the migration scope are flagged for the customer's admin to resolve.

File attachments on Contacts, Accounts, Cases, and other records export from Creatio to a file store, then re-import into Salesforce as ContentVersion records linked to ContentDocumentLink records pointing at the parent Contact, Account, or Case. The original file name, file type, and created date are preserved. Large attachments (>25 MB) may require chunked upload via the Salesforce Content API; we flag any files exceeding Salesforce's 2 GB ContentVersion size limit.

Creatio Owner (User) records assigned to Opportunities, Cases, and other objects are resolved by email matching against the Salesforce User table. Owners without a matching Salesforce User are held in a reconciliation queue; the customer's Salesforce admin provisions missing Users (active or inactive per the original Creatio user's status) before record import resumes. The Creatio OwnerId on each record remaps to the corresponding Salesforce OwnerId post-User provisioning.