Migrate from Twenty CRM to HighLevel

Twenty People records map directly to GoHighLevel Contacts. Email is the primary dedupe key during import. We map name fields (firstName, lastName, displayName) to GoHighLevel's contactName structure. Phone, jobTitle, and any custom fields on People migrate as GoHighLevel custom fields. The companyId reference on People resolves to a previously imported GoHighLevel Company record before Contact insert to satisfy GoHighLevel's company-contact relationship.

Twenty Company records map to GoHighLevel Companies. Domain, industry, size, and location fields translate to GoHighLevel Company fields directly. GoHighLevel Companies must import before People because Contacts reference the parent Company. We use domain as the dedupe key. If a Contact's companyId references a Company not yet imported, we hold the Contact in a resolution queue.

Twenty Opportunities map to GoHighLevel Deals inside a configured Pipeline. The Twenty opportunity stage maps to a GoHighLevel Pipeline stage value. We pre-create the GoHighLevel Pipeline with stage names matching the Twenty stage labels before migration begins. Amount and close date migrate directly. The opportunity's linked CompanyId and PersonId (primary contact) resolve to the imported GoHighLevel Company and Contact respectively at migration time.

Twenty Tasks migrate to GoHighLevel Tasks with title, due date, assignee, and completion status preserved. Task assignment resolves via owner email matching to GoHighLevel User records. The task's relational target (linked to People, Companies, or Opportunities) migrates as a GoHighLevel tag or custom field indicating the related record type, since GoHighLevel Tasks do not expose the same polymorphic WhatId model as Salesforce.

Twenty Notes migrate as GoHighLevel Notes attached to the related Contact or Company. Note body content transfers as plain text. If the Note references a People or Company record, we link it to the corresponding imported GoHighLevel Contact or Company. Notes on Opportunities attach to the primary linked Contact as a fallback since GoHighLevel Deals do not have a native notes attachment object.

Twenty Custom Objects (unlimited on Organization tier, capped at 10 on Pro) migrate to GoHighLevel custom objects configured in the destination workspace before data import. We create the GoHighLevel custom object schema with fields mapped by type — text fields, number fields, date fields, and picklist fields. Custom object records import last, after all standard object imports, to resolve any cross-object lookup references. If GoHighLevel is on Starter tier ($97/mo), custom objects may be limited; we confirm tier during discovery.

Twenty Owner records (the user who owns a record) map to GoHighLevel User accounts. We resolve owners by email match. Any Twenty Owner without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before record import resumes, since OwnerId references are required on standard object inserts.

Twenty does not have native first-class engagement objects for calls, emails, and meetings — it lacks the activity timeline depth of platforms like HubSpot. Any engagement metadata stored in custom fields or linked notes migrates as GoHighLevel custom fields on the Contact or as Notes. We flag this limitation during discovery so the customer understands that the activity timeline inside GoHighLevel will be populated by GoHighLevel-native tracking (calls, emails, SMS logged via the platform) going forward, not from historical Twenty data.