Migrate from Teamwork CRM to HighLevel

Teamwork CRM Contacts map directly to GoHighLevel Contacts. Standard fields (name, email, phone, address) transfer 1:1. We map all Teamwork custom Contact fields to their typed GoHighLevel equivalents (text to text, integer to number, dropdown to dropdown). Note that Teamwork CRM does not support file or email attachments on Contact records, so there is nothing to migrate on that dimension. Contact-to-Company linking uses GoHighLevel's contact-to-company association which we resolve during import.

Teamwork CRM Company records map directly to GoHighLevel Company. Company Name, Domain, Address, Phone, and custom fields migrate 1:1. We sequence Companies first in migration runs to satisfy the parent-lookup relationship before Contacts import. If the customer uses GoHighLevel Locations, Companies attach to the primary Location unless the customer specifies a multi-location assignment strategy during scoping.

Teamwork CRM Leads map to GoHighLevel Leads. Lead status, source, and custom fields transfer. Teamwork CRM allows simultaneous Leads and Opportunities pipelines; we preserve both pipelines and their respective stage assignments in GoHighLevel Opportunities and Pipeline configuration.

Teamwork CRM Opportunities map to GoHighLevel Opportunities with Stage, Pipeline, Value, Probability, Expected Close Date, and custom fields preserved. The pipeline association maps to a GoHighLevel Pipeline that we configure before migration, with stage names and probabilities carried over from the Teamwork CRM pipeline definition.

Each Teamwork CRM pipeline (Leads pipeline and Opportunities pipeline) maps to a GoHighLevel Pipeline. We replicate stage names, stage order, and probability percentages. If the customer runs both Leads and Opportunities pipelines simultaneously in Teamwork CRM, we create corresponding Pipelines in GoHighLevel and document which Opportunities belong to which pipeline during import.

Teamwork CRM Activities (calls, meetings, and tasks) linked to Contacts or Opportunities map to GoHighLevel Activities. We preserve title, description, start date, due date, duration, completion status, and assignee. Assignee resolution uses email-to-Team Member matching. Activity timestamps preserve the original date for timeline ordering.

Teamwork CRM custom fields (short text, integer, dropdown) map to GoHighLevel custom fields of matching type. Text custom fields map to GoHighLevel text fields, integer to number, and dropdown to dropdown. Multi-select, date, and boolean custom fields do not exist in Teamwork CRM natively, so there are no gaps on that side. We pre-create the destination custom field schema before data import.

Teamwork CRM Tags on Contacts and Opportunities transfer to GoHighLevel Tags. Tag names migrate 1:1. If the customer uses a tag taxonomy that GoHighLevel cannot replicate (for example, tag hierarchies), we map to GoHighLevel Tags and document the hierarchy as a separate configuration item for the customer admin.

Teamwork CRM Users (Owners) referenced on Contacts, Companies, Deals, and Activities resolve to GoHighLevel Team Members by email match. Any Teamwork User without a matching GoHighLevel Team Member goes to a reconciliation queue for the customer's admin to provision before record import resumes. This is a prerequisite step because OwnerId references are required on most records.