Migrate from Marketing Creatio to HighLevel

Marketing Creatio Contacts migrate directly to GoHighLevel Contacts. Standard fields (Name, Email, Phone, Job Title, Address) map 1:1. The Creatio CanExportGrid permission governs export access; we confirm export permissions during discovery. We preserve the Contact's owner User reference via email-match lookup to GoHighLevel user records, flagging any Creatio owner without a matching GoHighLevel user for admin provisioning before the Contact import phase.

Creatio Accounts map to GoHighLevel Companies. The account-contact linkage is preserved by importing Companies first, establishing the GoHighLevel Location or Company ID as the dedupe key for Contact import. Any Creatio Account without a Company ID (custom or legacy records) receives a generated identifier during staging. Address, industry, and website fields map directly.

Creatio Opportunities map to GoHighLevel Opportunities. The Opportunity-Account Lookup resolves to the GoHighLevel Company ID during staging. Deal amount, stage, close date, and owner migrate 1:1. Creatio stage names are mapped to GoHighLevel Pipeline stage values during configuration; we confirm the stage matrix with the customer before import begins.

Creatio Leads map to GoHighLevel Leads. Status, conversion date, and source information transfer directly. If the customer has configured Creatio Leads to auto-convert to Contacts, we flag any unconverted Leads requiring post-migration follow-up. Lead owner maps via email-match to GoHighLevel user.

Creatio Cases map to GoHighLevel Tickets. Case status, priority, and resolution fields migrate to Ticket status and priority fields. The ticket-contact and ticket-company relationships resolve through the Contact and Company import phases completed earlier. Case owner maps via email-match to GoHighLevel user.

Creatio Orders migrate to GoHighLevel Orders with Account and Contact lookups resolved from the earlier Company and Contact import phases. Product line items require the Products import to be complete first because referential integrity is enforced. Any Order referencing a Product not included in migration scope is flagged for customer review.

Creatio Products map to GoHighLevel Products. Product catalog including SKU, pricing, and bundle structure migrates as reference data before Order import begins. Pricing rules and tiered pricing configurations are documented as a custom text field for admin reconstruction in GoHighLevel pricing rules.

Creatio Activities (Tasks, Events, Calls) migrate to GoHighLevel Task, Calendar Event, and Call records respectively. Due dates, statuses, and assigned owners transfer with original timestamps preserved. Activity templates and reminder configurations do not migrate and are documented as a rebuild reference list. The parent Contact or Company reference resolves via email-match or record ID lookup in the staging layer.

Creatio custom objects built in the Object type schema migrate to GoHighLevel Custom Objects. Schema discovery requires the customer to export custom object definitions from Creatio's Configuration section before migration begins. We pre-create the GoHighLevel Custom Object schema (fields, field types, and lookup relationships) in a pre-migration setup phase. Any Lookup columns referencing unmigrated parent records are flagged during staging to prevent constraint violations at import time.

Creatio tags stored as comma-separated values or via the Tag object migrate to GoHighLevel Tags. Tags are extracted as a custom text property on the target object during staging and loaded as GoHighLevel Tag assignments post-import. Tag strategy (per-contact tags vs. list-based tags) is confirmed with the customer during scoping.

File attachments on Contacts, Accounts, Cases, and other records are exported from Creatio to a file store with their record reference metadata. We re-link them in GoHighLevel using the record's GoHighLevel ID assigned during import. Attachments without a resolvable parent record are held in a reconciliation queue.