Migrate from HighLevel to Twenty CRM

HighLevel Contacts map directly to Twenty CRM People. Standard fields (firstName, lastName, email, phone, address, lifecycle stage) migrate to their Twenty equivalents. The HighLevel contact ID is preserved in a custom field for cross-reference. We resolve the Company lookup by matching the Contact's linked Company name against previously migrated Twenty Companies before the Contact insert phase.

HighLevel Companies map 1:1 to Twenty CRM Companies. Fields including domain, industry, size, and address migrate directly. The Company record is imported before Contacts so that the Contact-to-Company lookup relationship is satisfied at insert time. We use domain as the dedupe key during import.

HighLevel Opportunities map to Twenty CRM Opportunities. Each Opportunity's linked Pipeline and Stage name are resolved to Twenty's Stage field, with stage order preserved. Amount, Close Date, and probability migrate directly. The Opportunity's linked Contact (or Company) is resolved through the People or Company lookups already established in earlier phases.

HighLevel Pipelines map to Twenty's Opportunity Stages. If the HighLevel account uses multiple Pipelines, we map each Pipeline name to a distinct Stage name within Twenty's single Opportunities object and note the structure in the handoff document. Stage order and probability percentages migrate as configuration.

HighLevel Tags applied to Contacts migrate to a Twenty custom field defined as a multi-select picklist. We export the full tag vocabulary per contact, then create the corresponding picklist values in Twenty's data model before import. The customer chooses whether Tags become a flat multi-select field or are split into topic-based fields during scoping.

HighLevel Custom Objects migrate to Twenty CRM Custom Objects. We introspect the HighLevel Custom Object schema via the API, identify all field types and lookup relationships, then recreate the equivalent Custom Object in Twenty using Settings → Data Model before any data moves. Relationships to standard objects (Contact, Company, Opportunity) are resolved through lookup fields at migration time.

HighLevel Tasks linked to Contacts migrate to Twenty Tasks. Assignment, due date, status, and body text transfer directly. Tasks are imported after the People records they reference are already present in Twenty to satisfy the relationship dependency.

HighLevel Users are mapped to Twenty Workspace Members by email. The customer's Twenty admin provisions Members in Settings → Members before migration begins so that Owner/Assignee fields can reference valid User records. Any HighLevel User without a matching Twenty Member goes to a manual provisioning queue.

HighLevel Appointments (date, time, contact, status, location) migrate to Twenty Tasks with a calendar-specific field configuration. Calendar booking links and recurring appointment settings do not migrate as Twenty's scheduling module works differently; we document the appointment configuration in the handoff checklist.

HighLevel file attachments linked to Contacts or Opportunities migrate as file references. If the attachment URL is publicly accessible, we store it in a custom URL field on the Twenty record. Files exceeding 25MB are flagged for manual re-upload to avoid migration timeout. We do not migrate the white-label branding assets as these are not accessible via HighLevel's API.