Migrate from X2CRM to HighLevel

X2CRM Contacts map directly to GoHighLevel Contact records. Standard fields (name, email, phone, address) transfer via REST API with application/json payloads. Custom contact fields migrate to GoHighLevel custom fields scoped to the Contact object. Tag associations from X2CRM are preserved as tags on the GoHighLevel Contact using the tag API endpoint. We resolve any duplicate email addresses via upsert rather than insert to avoid orphaned duplicates.

X2CRM Accounts (companies and organizations) map to GoHighLevel Company records. Associated contacts link via GoHighLevel's contact-company association API after both records exist. Account lifetime value, industry, and website fields transfer to GoHighLevel Company properties. If X2CRM Accounts reference custom fields, those fields are pre-created in GoHighLevel as Company-scoped custom fields before migration.

X2CRM Deals map to GoHighLevel Opportunities with stage, value, probability, and expected close date preserved. The X2CRM pipeline assignment maps to a GoHighLevel pipeline that we configure before migration. Deal owners resolve by email match against GoHighLevel users. Activity history attached to the Deal (calls, emails, meetings) migrates separately via the Activity mapping and links back to the Opportunity via WhatId on the GoHighLevel activity record.

X2CRM Products (catalog items with pricing, SKU, and description) map to GoHighLevel Products. Product pricing and SKU transfer to GoHighLevel product fields. If X2CRM Products are linked to Deals via line items, we create the Opportunity Product association during the Opportunity import phase.

X2CRM Services track recurring service contracts or subscriptions linked to Accounts. GoHighLevel does not have a native Services object, so we create a Custom Object named 'Service' in GoHighLevel with fields for status, renewal date, and linked Company. The 10 Custom Object limit per sub-account applies; we confirm the customer's object count during scoping and flag if additional objects from X2CRM custom modules push against the cap.

X2CRM Campaign records (campaign name, type, status, and associated mailing lists) map to GoHighLevel Campaign records. Campaign history and linked contacts transfer as Campaign membership records in GoHighLevel. Email campaign templates from X2CRM migrate as static HTML that we deliver as a reconstruction reference for the customer to rebuild in GoHighLevel's email builder.

X2CRM Activities (calls, meetings, and tasks with timestamps, owners, and related Contacts or Deals) map to GoHighLevel Activities. We sequence Activities in chronological order and map related record IDs to their new GoHighLevel Contact or Opportunity references. Task status, priority, and due date transfer directly. Call duration and disposition from X2CRM map to GoHighLevel custom activity fields if configured.

X2Flow stores automation logic as trigger-action pairs with UI configuration that is not accessible via the X2CRM REST API in a portable format. We do not migrate X2Flow as code. During discovery, we extract every X2Flow rule's trigger type, condition criteria, and action sequence and produce a Workflow Reconstruction Document that maps each X2Flow rule to equivalent GoHighLevel Workflow logic. The customer's admin rebuilds the workflows in GoHighLevel's workflow builder post-migration using this document as a guide.

X2CRM Tags are standalone label records that can be applied to multiple object types. We migrate all Tags and reapply them to their target GoHighLevel records post-import, maintaining the many-to-many associations. GoHighLevel's tag model supports tagging Contacts, Companies, and Opportunities; we map X2CRM tag assignments to the equivalent GoHighLevel tag on the corresponding object.