Migrate from Creatio to Freshsales

Creatio Accounts map directly to Freshsales Accounts. Address fields, industry classification, and ownership assignments transfer directly. We resolve the OwnerId by matching Creatio's Owner email against Freshsales User email. Account is the parent of Contact, so it migrates before any Contact records to satisfy Freshsales's foreign-key expectations.

Creatio Contacts map to Freshsales Contacts with first name, last name, email, phone, address, lifecycle stage, and owner assignment preserved. Creatio lifecycle stage values transfer to Freshsales's contact stage or a custom multi-select field if the customer's stage matrix exceeds Freshsales's default picklist. Owner resolution runs by email match against Freshsales Users.

Creatio Opportunities map to Freshsales Deals. Stage, amount, probability, and close date transfer directly. Creatio's configurable pipeline per product line maps to Freshsales Deal Stages, and we configure Freshsales pipeline stages to match the Creatio pipeline definition before import. Probability percentages round to Freshsales's allowed range.

Creatio Leads map to Freshsales Leads with status, source, and score preserved. If the customer uses Creatio's lead scoring model, we carry the score into a Freshsales custom numeric field. Freshsales supports lead conversion mapping from Lead to Contact and Account at migration time, and we document the conversion field mapping from Creatio's lead fields to Freshsales's target fields.

Creatio Cases map to Freshsales Cases with status, priority, resolution SLA, and lookups to Contact and Account. Case status values from Creatio map explicitly to Freshsales Case Status picklist values rather than relying on index-order matching, which is a common source of silent status errors. Freshsales's Cases require Service Cloud or an active case management configuration on the target plan.

Creatio stores Call, Email, and Task activity types under a unified Activity schema. We separate by type at writeback: calls land as Freshsales Tasks with TaskSubtype=Call, emails land as Tasks or Notes depending on content type, and meetings land as Appointments. The activity timestamp preserves timeline ordering in Freshsales. Creatio's activity body and disposition fields map to custom task fields.

Creatio Products with price lists and bundle structures map to Freshsales Products. Multi-currency pricing in Creatio requires explicit currency mapping during writeback to avoid rounding errors; we resolve currency by matching the Creatio currency record name to Freshsales's currency configuration. Unit of measure and bundle parent-child relationships map to Freshsales product hierarchy.

Creatio entity schemas built in the Object designer reverse-engineer into Freshsales custom objects. We extract the complete column map from the exported Creatio schema package, pre-create the corresponding Freshsales custom object with all fields and data types, then import data via Freshsales REST API. Lookup relationships between custom objects and standard objects (Account, Contact, Deal) resolve at migration time using the mapped foreign keys.

Creatio custom fields extending Accounts, Contacts, Cases, and Opportunities require type-aware mapping before writeback. Calculated fields are skipped as static writeback targets (they compute at display time and have no persistent value). Multicurrency fields transfer the base currency numeric value and trigger an explicit currency record mapping in Freshsales rather than writing a raw numeric that lacks currency context.

Creatio v8.3.2+ File API stores attachments either in-database or externally on S3/Azure Blob, controlled by the UseEntityFileApi flag. We detect the storage mode during discovery, extract files from the appropriate source, and redirect writes to Freshsales's native file attachment model. If Creatio uses external storage and the UseEntityFileApi flag is enabled, the file URL redirect chain must be rewritten to point to Freshsales's storage location.