Migrate your Teamgate data

People are the primary contact records in Teamgate with standard fields (name, email, phone, address) plus custom fields. We export all fields via the API, mapping to destination Contact or Lead objects. Tags on people records are preserved as a comma-separated custom field during migration.

Company records are distinct from People in Teamgate and support custom fields, industry classification, and address data. We map Companies 1:1 to the destination CRM's Account/Company object, preserving any linked People associations through a foreign key mapping table.

Deals are Teamgate's primary revenue-tracking object tied to Pipeline Stages. We preserve deal value, stage assignment, expected close date, loss reasons, and owner. Activity history attached to deals is extracted as a secondary export and relinked by deal ID at the destination.

Teamgate allows multiple named Pipelines. We export pipeline definitions including stage names, stage order, and stage-specific win/loss probability values. These are recreated at the destination using the same stage configuration during migration.

Each Pipeline contains ordered Stages with optional probability weights. We preserve stage names, sequence order, and probability mappings. If the destination CRM uses a different stage model, we map to the closest equivalent and flag any probability gaps.

Teamgate supports custom fields on People, Companies, and Deals. Custom field types include text, number, date, dropdown, and checkbox. We export the full custom field schema alongside data, mapping by field name to destination custom fields that may require manual creation if the destination has different field type constraints.

Tags in Teamgate are flat label strings applied to People, Companies, and Deals. We export tags as a normalized list per record. Some destination CRMs store tags as a multi-select field while others use a separate Tags object, requiring a mapping decision during scoping.

Teamgate logs tasks, calls, emails, and meetings as Activities tied to People or Deals. Activity types, timestamps, and notes are exportable. The destination CRM may have a different activity model (Engagements, Timeline Events), so we map activity records to the closest equivalent object.

Teamgate stores files up to the tier storage limit (5–200GB/user). File names, links, and storage locations export via API, but the actual binary files must be downloaded and re-uploaded at the destination. Google Drive attachments export as shareable links rather than file copies.

User records include name, email, role, and active status. Owner assignment on Deals and Companies is preserved as a user ID cross-reference. We export the full user list and map owner IDs to destination user records, flagging any inactive users that need to be reactivated.

Loss reasons are a configurable dropdown in Teamgate tied to Deals. We export all active loss reason values and map them to the destination CRM's opportunity loss reason field, creating new values where the destination has a closed vocabulary.

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 reference document so the customer can manually reconfigure integrations at the destination.