Migrate from Sales Creatio to Salesforce Sales Cloud

Creatio Accounts map directly to Salesforce Account. Standard address fields, industry, type, annual revenue, and ownership assignment migrate 1:1. Creatio's Primary Contact lookup resolves to a Salesforce Contact record that we link via AccountId. If Creatio Accounts hold individual persons (Creatio supports this in some configurations), we flag them for Contact splitting during scoping.

Creatio Contacts map to Salesforce Contact with the parent Account resolved via the Contact's Account lookup. Communication preferences, lifecycle stage fields, and custom contact properties migrate to custom fields on Contact. OwnerId resolves via email match to the Salesforce User table.

Creatio 8.0 introduced a dedicated Lead object distinct from Contacts. Leads in Creatio map to Salesforce Lead with Lead Status mapping to Salesforce's default Status picklist. Source, rating, and any lead scoring fields migrate to custom fields. If the customer uses Creatio's legacy Account-as-person model, those records map to Contact instead of Lead.

Creatio Opportunities map to Salesforce Opportunity. The pipeline stage configuration from Creatio maps to Salesforce StageName and a corresponding Sales Process that we pre-configure. Stage probability percentages migrate from Creatio to Salesforce StageProbability. Custom Opportunity fields migrate to custom Opportunity fields. Close date and amount migrate directly.

Each Creatio pipeline becomes a Salesforce Record Type on Opportunity with its own Sales Process. Stage values from Creatio map to StageName entries in the Sales Process, with probability and ForecastCategory configured per stage. This prevents stage picklist bleed between business units.

Creatio Cases migrate to Salesforce Case if the destination org includes Service Cloud or has Cases enabled. Case Status maps to Salesforce Case Status, priority maps to Priority, and the linked Account/Contact resolves via Salesforce AccountId and ContactId lookup. Resolution notes and SLA timer fields migrate as custom Case fields.

Creatio Activities cover tasks, calls, emails, and meetings linked to any parent object. We normalize activity types and migrate tasks to Salesforce Task, calls to Task with TaskSubtype=Call, emails to Salesforce EmailMessage linked to a Task, and meetings to Salesforce Event. The Regarding lookup (WhatId, WhoId) resolves to the migrated parent record's Salesforce ID at migration time. Activity timestamps preserve the original Creatio created date.

Creatio Orders map to Salesforce Order if the destination org has Orders enabled in Setup. Order headers link to Account, and the status, effective date, and total amount migrate directly. Order line items migrate separately as OrderProducts. If Salesforce Order Management is not enabled in the destination org, we flag this during scoping so the customer's admin can activate it before migration.

Creatio Products map to Salesforce Product2 with Standard Price Book entries created during import. ProductCode from Creatio becomes ProductCode on Product2. Bundle and pricing rule support depends on the destination's data model; if the customer uses complex pricing, we flag it as a manual configuration step.

Creatio custom objects created in Studio have user-defined schemas that vary per instance. We perform a schema discovery pass during scoping, extract the full field list and field types, and map each to an equivalent Salesforce custom object with __c API naming. Lookup relationships to standard objects resolve at migration time once the parent standard record IDs are established. This must be scoped explicitly before migration begins.

Both standard and custom objects in Creatio can carry user-added fields with custom data types including dropdowns, lookups, checkboxes, and integers. We map each field type explicitly: dropdowns to picklists, checkboxes to booleans, lookups to Salesforce lookup or external ID fields. Lookup fields require a separate target-record resolution step that we execute in dependency order after parent records are migrated.

Creatio stores files in its database or external S3/Azure Blob storage. On-site instances use Creatio's FileMigrator utility to extract files to S3 and re-link them. Cloud instances require opening a support ticket with Creatio to initiate file extraction. We factor the extraction timeline into the migration plan, extract files during the audit phase, upload them to Salesforce Files, and link them via ContentDocumentLink to the parent Account, Contact, Opportunity, or Case record.

Creatio's BPM workflows encode logic in a proprietary format tied to the internal process engine. There is no export path that preserves workflow logic for use in Salesforce Flow. We export a written reference inventory of every active BPM workflow including screenshots, step sequence, conditions, timers, and notification actions. The customer's admin rebuilds each workflow in Salesforce Flow post-migration. This must be scoped explicitly before migration begins and is excluded from the data migration scope.

Creatio's Classic UI dashboards require the separate Dashboards Migrator app from the Creatio Marketplace to transition to Freedom UI, and Freedom UI widgets do not map directly to Salesforce dashboard components. We include the Dashboards Migrator step in the migration plan, install it in the target environment, run selective migration, and test dashboard fidelity against the source. Final dashboard rebuilding in Salesforce's Lightning dashboard builder is a manual admin step post-migration.

Creatio User records include email, role, and organizational unit. Owner assignment on records links to these users. We map users by email match to their Salesforce User counterparts. Any Creatio user without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive status resolves at migration time.