Migrate from Teamgate to HighLevel

Teamgate People map 1:1 to GoHighLevel Contacts. Standard fields (first_name, last_name, email, phone, address) map directly. Custom fields on People migrate to GoHighLevel custom contact fields. We extract tags as GoHighLevel tags and apply them during import. Owner assignment maps via email match to GoHighLevel User records; unresolved owners go to a reconciliation queue.

Teamgate Company records map 1:1 to GoHighLevel Companies. The Company domain name becomes the Website field. Companies import before Contacts so that the Company-Contact link is satisfied at insert time. Custom fields on Company migrate to GoHighLevel custom company fields.

Teamgate Deals map 1:1 to GoHighLevel Opportunities. Deal value migrates to Opportunity Amount. Pipeline stage assignment maps to GoHighLevel pipeline stage via a stage-mapping table created during scoping. Owner assignment resolves via email match to GoHighLevel User. Loss reasons map to GoHighLevel custom opportunity loss reason fields.

Teamgate pipeline definitions (names, stage counts, stage ordering) are exported and recreated as GoHighLevel Pipelines. Each Teamgate pipeline becomes a separate GoHighLevel Pipeline. Stage-specific probability weights are preserved if they exist in Teamgate and are set on the corresponding GoHighLevel stages.

Teamgate Pipeline Stages map to GoHighLevel Pipeline Stages within their parent Pipeline. Stage names and sequence order transfer directly. We create the stage-mapping table during scoping and apply it during Deal-to-Opportunity import. Custom probability weights per stage migrate if configured in Teamgate.

Teamgate custom fields on People, Companies, and Deals are exported with their field types (text, number, date, dropdown, checkbox). We recreate equivalent custom fields in GoHighLevel under Settings > Custom Fields before importing any data. Dropdown options are preserved; checkbox fields become GoHighLevel checkbox fields. We map field values during import rather than relying on post-migration manual entry.

Teamgate flat-label tags applied to People, Companies, and Deals export as normalized string arrays per record. We apply these as GoHighLevel Contact Tags during import. GoHighLevel tags are not multi-select picklist fields; they are a separate tag entity. We preserve tag names exactly so that reporting by tag is uninterrupted after migration.

Teamgate Activity records (calls, emails, meetings, tasks) attach to People or Deals and export with timestamps, notes, and type indicators. We import them as GoHighLevel Activities linked to the migrated Contact or Opportunity. Original timestamps are preserved as the Activity date. Call duration and disposition from Teamgate map to GoHighLevel activity notes or custom fields.

Teamgate file attachments store names and URLs. Binary files must be downloaded from Teamgate and re-uploaded to GoHighLevel. We flag the total file volume during scoping and advise whether the customer handles re-upload or engages a file migration add-on. Storage tier limits (5GB/user Starter, 10GB/user Professional) are calculated during scoping to determine whether Teamgate storage can accommodate the full export.

Teamgate Users export with name, email, role, and active status. We map by email match to GoHighLevel Users. Inactive Teamgate users are held out of the migration unless the customer explicitly requests them. Unresolved users (no matching GoHighLevel User) go to a reconciliation queue for the customer's admin to provision before record import resumes.

Teamgate Loss Reasons are a configurable dropdown tied to Deals. We export all active loss reason values and create a corresponding custom field on GoHighLevel Opportunity to store them. Values are created in GoHighLevel before Deal import begins, and Deal records reference the correct loss reason value at insert time.

Teamgate integration configurations (OAuth tokens for Gmail, Twilio credentials, Zapier webhooks, QuickBooks connections) are not exportable via API and cannot be migrated. We export integration names and settings as a documented list for the customer's admin to reconfigure manually in GoHighLevel. GoHighLevel's native integrations (Google Calendar, Zapier, QuickBooks) require fresh OAuth setup in the destination environment.