Migrate from Sales Creatio to HighLevel

Creatio Accounts (companies) map directly to GoHighLevel Company records. We extract the Account Name, Website, Industry, Address, and Phone fields and map them to the equivalent GoHighLevel Company fields. The Company record must exist before importing Contacts so that the Contact-to-Company association is resolved at insert time. Owner assignment from Creatio maps to GoHighLevel user by email match.

Creatio Contacts map to GoHighLevel Contacts. The contact's name, email, phone, communication preferences, and lifecycle stage migrate as standard fields. Creatio's Contact-to-Account lookup links to the GoHighLevel Contact-Company association. We preserve the Creatio Contact Owner as a custom field original_owner__c for audit, and map to the GoHighLevel assigned user by email.

Creatio Leads (distinct from Opportunities until conversion) merge into GoHighLevel Contacts because GoHighLevel does not have a separate Lead object. We preserve the Creatio Lead source, status, rating, and conversion date as custom fields on the GoHighLevel Contact (lead_source__c, lead_status__c, lead_rating__c, lead_converted_date__c). Customers who need strict Lead/Contact separation in GoHighLevel should note this is not supported natively and would require a custom tagging strategy.

Creatio Opportunities map to GoHighLevel Opportunities. The pipeline stage, amount, probability, and close date transfer. Stage names are fully customizable per Creatio organization; we extract the active pipeline configuration and create GoHighLevel pipeline stages that mirror the source. A critical limitation: GoHighLevel does not allow editing the Opportunity created date after import (documented in GoHighLevel's Canny feedback board, multiple user requests 2022-2025). We flag this during scoping and advise the customer to set correct created dates during import rather than after. Historical close dates do migrate correctly.

Creatio Cases (service tickets) do not have a native GoHighLevel equivalent. Cases with a service-billing context map to GoHighLevel Opportunities with a custom case_type__c field. Cases that represent internal service requests or support tickets map to GoHighLevel Tasks with a custom case identifier. We determine the split strategy during scoping based on how the customer uses Creatio Cases.

Creatio Activities (tasks, calls, emails, meetings) map to GoHighLevel Tasks and Calendar Events. The activity type enumeration varies between Creatio editions; we normalize types and preserve the Regarding (lookup) relationship to the parent Contact or Opportunity. Activity timestamps migrate as the ActivityDate to maintain chronological ordering in the GoHighLevel timeline.

Creatio Orders link to an Account and contain line items referencing Products. We migrate order headers as GoHighLevel Opportunities with a custom order_number__c field and order_status__c. Line items migrate as Opportunity custom fields (product_name__c, quantity__c, unit_price__c) or as a structured custom field if the order has multiple line items requiring granular tracking.

Creatio Products carry pricing, unit type, and tax categories. We migrate the product catalog as a GoHighLevel Opportunity product custom field or as a standalone custom field group depending on whether the customer uses GoHighLevel's product catalog feature. Bundle and pricing rule support depends on the destination configuration and is scoped during discovery.

Creatio custom objects created in Studio have user-defined schemas. GoHighLevel does not have an independent custom object type; instead, custom fields attach to Contact or Opportunity records. We perform a schema discovery pass on Creatio, then pre-create equivalent GoHighLevel custom fields (with Folder organization for Contact vs Opportunity scope) before importing any records. Lookup relationships from Creatio custom objects to standard objects require mapping to GoHighLevel custom fields with reference-style storage.

Creatio BPM workflows encode logic in the internal process engine format and are not exportable or portable to GoHighLevel. We do not migrate them as code. We extract the workflow configuration as a reference document: screenshots of the step sequence, condition branches, action types, and delay configurations. The customer's GoHighLevel admin rebuilds these using GoHighLevel's Workflow builder. This must be scoped explicitly before migration begins because BPM workflows may govern business processes that affect how data should be organized in the destination.

Creatio stores files in the database or external S3/Azure Blob storage. Cloud instances require a support ticket with Creatio to initiate file extraction; on-site instances can use the FileMigrator utility. Files migrate as base64-encoded custom fields or as links to an external storage location that the customer maintains post-migration. We coordinate the extraction step with the customer's Creatio instance type during the data audit phase.