Migrate from TeamWave to HighLevel

TeamWave Contact records (name, email, phone, address, lifecycle stage, custom fields) map to GoHighLevel Contact records via the Contacts API endpoint. The TeamWave lifecycle stage property maps to a GoHighLevel Custom Field (lifecycle_stage__c) since GoHighLevel's native Contact object uses Tags and Custom Fields for lead status rather than a built-in lifecycle stage property. We extract the email as the dedupe key and map phone, address, and custom field values to their GoHighLevel equivalents. TeamWave Company associations (company_id foreign key) are resolved after Company import so that the LocationId and CompanyId references are satisfied on Contact insert.

TeamWave Company records map to GoHighLevel Company records. The Company name, domain, address, and phone fields map directly. We use the company name as the dedupe key during import. Companies are imported before Contacts so that the Company-Contact lookup relationship is resolved at Contact insert time. Note that GoHighLevel's Company object is scoped to the Location (sub-account), and cross-location Company sharing requires manual assignment post-migration or a custom integration.

TeamWave Deal records map to GoHighLevel Opportunity records. The deal name, value (amount), stage, owner, expected close date, and custom fields transfer directly. TeamWave deal stages map to GoHighLevel pipeline stages, which we configure as part of the GoHighLevel pipeline setup before migration. The deal owner maps to the GoHighLevel User by email resolution. Any deal notes migrate as GoHighLevel Notes attached to the Opportunity.

TeamWave's deal pipeline stages (each pipeline's configured stage names and values) map to GoHighLevel Pipeline stages. We read the stage names from the TeamWave export and create equivalent GoHighLevel pipeline stages via the Pipelines API before importing Opportunity records. Stage ordering and probability percentages are preserved as part of the pipeline configuration.

TeamWave Tasks map to GoHighLevel Tasks. We preserve task title, description, due date, status, priority, and assignee. TeamWave's project_id foreign key (linking Task to Project) cannot be preserved as a native GoHighLevel field since GoHighLevel has no Projects module. We store the original project_id as a custom field project_id__c on the Task record for audit and reference, and the customer's admin rebuilds project grouping using GoHighLevel Custom Objects or Tags as part of the post-migration workflow setup.

TeamWave Project records (name, description, status, client association, start/end dates) require a GoHighLevel Custom Object for direct migration. We create a Project custom object via GoHighLevel's Custom Fields API, define the schema (name, description, status, client, start_date, end_date fields), then import Project records. Because GoHighLevel Custom Objects do not have native Task sub-records, Tasks are imported as separate Task objects with a project_id__c custom field linking them to the parent Project custom object. This is a configuration-heavy migration step that requires GoHighLevel Agency Pro or higher plan access for Custom Object creation.

TeamWave User records (name, email, role, department) map to GoHighLevel Users by email resolution. We extract the full user list from TeamWave's team member export, match by email against GoHighLevel Users, and resolve OwnerId assignments on Deals (Opportunities) and Tasks. Any TeamWave User without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

TeamWave custom fields on Contacts, Deals, Projects, and Tasks require pre-creation in GoHighLevel before data import. We extract the custom field definitions (field name, type, options) from the TeamWave export, map them to equivalent GoHighLevel Custom Field types (text, number, date, dropdown, checkbox), and create them via the Custom Fields API before any data is loaded. Dropdown fields in TeamWave map to Select-type Custom Fields in GoHighLevel. Note that GoHighLevel uses object-scoped custom fields, so each object (Contact, Company, Opportunity) gets its own custom field definition even if the field name is identical.

TeamWave Calendar Events (title, date/time, linked entity, attendees) map to GoHighLevel Calendar Events. We export events with their date/time, title, linked Deal or Contact reference, and attendee list. The linked entity is resolved to the corresponding GoHighLevel Contact or Opportunity ID at migration time using the email/name lookup table built during Contact and Opportunity import.

TeamWave HR/Employee records (name, role, department) are evaluated for migration on a case-by-case basis. If the customer uses GoHighLevel as a CRM only, employee records do not have a native GoHighLevel equivalent and are not migrated. If the customer intends to use GoHighLevel's team management features, employee records can be mapped to GoHighLevel Contacts with a department custom field. We confirm the desired approach during scoping. Standard employee data (salary, PTO, performance metrics) does not migrate as those fields have no GoHighLevel equivalent.