Migrate from Marketing Creatio to Freshsales

Marketing Creatio Contact records map directly to Freshsales Contact. Email serves as the primary dedupe key. Standard fields (Name, Email, Phone, Job Title, Address) map to Freshsales equivalent fields. We resolve the Contact-to-Account Lookup by importing Accounts first, then remapping the Creatio Account GUID to the Freshsales-assigned Account ID in the staging layer before Contact insert to prevent orphaned relationships.

Creatio Account records map to Freshsales Account. Account Name becomes the Account Name field; the Creatio Industry field maps to Freshsales Industry; Website maps to Website. Account is imported before Contact to satisfy the foreign key constraint. We extract all Account IDs assigned in Freshsales and build a cross-reference table to update Contact.AccountId during the Contact import phase.

Creatio Lead records map to Freshsales Lead with Status, Lead Score (if present), and Owner preserved. Creatio Lead Status values (New, Open, Qualified, Unqualified) map to Freshsales Lead Status picklist. Any custom lead scoring field from Creatio migrates as a custom field on Freshsales Lead for post-migration Freddy AI recalibration.

Creatio Opportunity maps to Freshsales Deal. Amount, Stage, Close Date, and Owner migrate directly. The Opportunity-Account Lookup resolves through the Account cross-reference table built during the Account import phase. Closed-Won and Closed-Lost reason fields from Creatio custom properties map to Freshsales Deal custom fields.

Each Creatio deal pipeline becomes a Freshsales Pipeline. Pipeline stages from Creatio map to Freshsales stage values within the pipeline. Stage probabilities are translated from Creatio to Freshsales. If multiple pipelines exist in Creatio, we create multiple Pipelines in Freshsales and assign the relevant Deal records during import.

Creatio Case records map to Freshsales Case with Status, Priority, and Resolution fields preserved. Case-Contact and Case-Account Lookups resolve through the contact and account cross-reference tables. Case status workflow values (New, In Progress, Resolved, Closed) map to Freshsales Case Status values. If Creatio uses custom case statuses, we create custom picklist values in Freshsales before migration.

Creatio Owner (User) records referenced on Contacts, Accounts, Opportunities, and Cases map to Freshsales User by email address. We extract every distinct Owner GUID and email from Creatio source records, match against Freshsales User table by email, and hold any unmatched owners in a reconciliation queue for the customer's admin to provision before record import resumes.

Creatio Activity records (Tasks, Events, Calls) migrate to Freshsales Activity records with due dates, statuses, and assigned owners preserved. Each Activity's parent Contact or Account Lookup resolves through the cross-reference table. Activity timestamps are preserved to maintain timeline ordering. We use Freshsales REST API with batch chunking for large activity volumes.

Creatio Product records map to Freshsales Product Catalog entries. Product Name, SKU (from hs_sku), Unit Price, and description migrate. If the customer migrates Product Bundles or pricing rules, we flag these as requiring manual reconfiguration in Freshsales CPQ (add-on at $19/user/month on Growth) because bundling logic does not transfer automatically.

Creatio custom objects (defined via Object type schema) map to Freshsales Custom Modules. Freshsales Custom Modules are available from the Enterprise tier ($59/user/month); if the destination is Pro or Growth, Custom Modules cannot be provisioned within the current subscription. We pre-create the Custom Module schema including all custom fields and Lookup relationships before data import. Lookup columns that reference standard objects resolve through the parent cross-reference tables built during earlier phases.