Migrate from Creatio to Salesforce Sales Cloud

Creatio Accounts map directly to Salesforce Account. The Account Name, Industry, Type, Website, Phone, and Address fields migrate 1:1. Account is created first in migration sequence so that Contact and Case imports can resolve the AccountId lookup on insert. Any custom fields on the Creatio Account schema are pre-provisioned in Salesforce as custom fields before migration, with field types matched (text, number, date, picklist) to avoid Salesforce validation rejections.

Creatio Contacts map to Salesforce Contact. Creatio's lifecycle stage and owner assignment fields migrate to custom Contact fields if the destination does not use Salesforce's native Lead model. The primary Account lookup resolves at migration time using the AccountId previously inserted from the Creatio Account. Any multicurrency contact fields are flagged and mapped to CurrencyIsoCode with conversion applied via Salesforce's DatedExchangeRate table.

Creatio Cases map to Salesforce Case when the destination org includes Service Cloud or a Case record type. Creatio Case Status values map explicitly to Salesforce Case Status picklist values, and priority fields map directly. Origin, Reason, and SLA fields migrate to corresponding Salesforce Case fields. The Case lookup chain to Contact and Account is resolved via the AccountId and ContactId references inserted in the preceding phases.

Creatio Activities use a unified Activity schema with Call, Email, and Task subtypes. We separate these by type at writeback: Email activities become Salesforce EmailMessage records linked to a Task; Call activities become Task with TaskSubtype=Call and CallDurationInSeconds in a custom field; Task activities become Salesforce Task directly. ActivityDateTime preserves the original timestamp so the timeline order is maintained. WhoId points to the migrated Contact or Lead; WhatId points to the related Account or Case.

Creatio meeting activities map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendees link via EventRelation records pointing at the migrated Contact, Lead, and User records. Subject and Description fields transfer directly, and any custom meeting fields on the Creatio Activity schema migrate to Salesforce Event custom fields provisioned before writeback.

Creatio notes stored as Activity NOTE subtype migrate to Salesforce Note records. Notes are linked via ContentDocumentLink to the parent record (Contact, Account, Case, or Opportunity). Rich text formatting in the Creatio note body transfers as-is; any embedded image attachments become separate ContentDocument records with a reference in the note body.

Creatio Deals map to Salesforce Opportunity. StageName maps from the Creatio pipeline stage value, and the active Creatio pipeline becomes a Salesforce Sales Process or Record Type configured before migration. Amount, CloseDate, Probability, and Description migrate directly. OwnerId resolves via the User mapping constructed in the owner reconciliation step. Any custom Deal fields on the Creatio schema pre-provisioned as Opportunity custom fields receive the corresponding values during writeback.

Creatio Pipelines are configurable per product line with named stages. We extract the full pipeline definition including stage names, stage order, and probabilities before migration. Each pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the migrated stage values. Stage probability percentages transfer to Salesforce StageProbability, rounded to the nearest integer allowed by the platform.

Creatio Leads map to Salesforce Lead if the destination uses the Lead model for pre-conversion prospects. Status fields, source fields, and lead score values migrate to corresponding Salesforce Lead fields. Any Creatio-specific lead properties that have no Salesforce native equivalent become custom Lead fields (with __c suffix) provisioned during schema design. Lead conversion (to Contact and Account) is a post-migration admin action, not performed during data migration.

Creatio Products map to Salesforce Product2 with Standard Price Book entries created during migration. ProductCode transfers from Creatio's product code field, and the currency code on each product price migrates with the multicurrency flag set on the destination org. Bundle and unit-of-measure structures from Creatio translate to Salesforce Products with bundle pricing maintained via OpportunityLineItem relationships.

Creatio Users assigned as record owners are mapped to Salesforce User records by email match. The migration builds a user lookup table during discovery, and any Creatio User without a matching Salesforce User email is placed in a reconciliation queue. The customer's Salesforce admin provisions missing Users before production migration resumes because OwnerId references are required on most standard object inserts.

Creatio entity schemas in user packages translate to Salesforce custom objects with __c API names matched to the Creatio schema name. We reverse-engineer each custom object's column definitions from the exported package schema, generate the corresponding Salesforce custom object with all custom fields (matching types: Text, Number, Date, DateTime, Picklist, Lookup), lookup relationships to standard objects, and any validation rules. Custom objects are created in the Salesforce destination org before any standard object migration begins because dependent records may hold lookup references.

Creatio distinguishes simple, image, calculated, and multicurrency field types. Simple and image fields map directly to Salesforce equivalents. Calculated fields are flagged and skipped from static value writeback because they compute at display time and should be recreated as Salesforce formula fields. Multicurrency fields require multi-currency enablement in Salesforce and an explicit CurrencyIsoCode mapping using the DatedExchangeRate table. The field type audit happens before schema creation so no mis-typed fields land in the destination.

Creatio v8.3.2+ file attachments are extracted via the File API with routing determined by the UseEntityFileApi flag. Database-mode files download through the File API directly; S3 or Azure Blob storage files require bucket access credentials configured during discovery. Files land as Salesforce ContentVersion records linked to the parent record via ContentDocumentLink. We preserve the original file name, content type, and byte size during writeback so that Lightning Experience file previews work without re-upload.