Migrate from Teamgate to HubSpot

Teamgate People map directly to HubSpot Contacts. All standard properties (name, email, phone, job title, address) migrate as HubSpot native fields. Custom properties on the Person object become HubSpot custom properties on the Contact object and are created before the import runs so the field mapping references them correctly. Engagement history (calls, emails, meetings logged against the person) migrates as HubSpot Engagements.

Teamgate Organizations map to HubSpot Companies. Company name, domain, industry, employee count, and annual revenue migrate as native HubSpot Company properties. If the Teamgate organization has a parent-child hierarchy, the parent link migrates as HubSpot's parent_company_id on the Company record. Multi-contact organizations: all contacts are associated to the same Company record in HubSpot via the primary company link.

Teamgate Deals map to HubSpot Deals with the full set of standard properties: deal name, amount, close date, owner, and stage. The migration creates a HubSpot pipeline for each Teamgate pipeline before Deals land so the deal records reference a valid pipeline ID. Stage names and probability percentages are mapped value-by-value per pipeline during import. Original Teamgate create and update timestamps are preserved as custom datetime fields in HubSpot.

Each Teamgate pipeline becomes a separate HubSpot pipeline object. HubSpot requires pipelines to exist before deals reference them, so FlitStack creates all pipelines during the pre-migration schema setup phase. Stage names are mapped by your specification; probability percentages are applied per stage during deal import. Active and archived Teamgate pipelines are treated separately — archived pipelines are migrated as inactive HubSpot pipelines to preserve historical stage data.

Teamgate activities (calls, emails, meetings, tasks) migrate as HubSpot Engagements. Each engagement records the original timestamp, owner, and associated contact/company/deal ID from Teamgate. HubSpot engagement IDs are assigned at import time; the association back to the contact or deal uses the migrated record IDs so the timeline view in HubSpot reflects the full activity history with original owners preserved.

Teamgate custom fields on People, Organizations, and Deals become HubSpot custom properties. Field type is preserved — text fields stay text, pick-list fields become pick-list properties with the same option values. All custom properties are created in HubSpot before the migration run so the import mapping references them correctly. HubSpot's property name convention uses snake_case for the internal name and a human-readable label for display.

Teamgate workflow automations do not migrate automatically. HubSpot's workflow engine uses trigger-action logic with different event models than Teamgate's automation builder. FlitStack exports the full list of active and archived workflow definitions (trigger types, conditions, and actions) as a structured reference document your HubSpot admin uses to rebuild them in HubSpot Flows. The rebuild is a manual step; we do not offer automated translation of automation logic between platforms.

Teamgate tags on People and Organizations migrate as HubSpot tags on the corresponding Contact and Company records. Tags preserve the original label text. HubSpot tags are flat (no hierarchy), which matches Teamgate's tag model. If a contact in Teamgate has multiple tags, all of them are applied to the HubSpot Contact record. Tag usage statistics are preserved as reference counts in the migration audit log.

Teamgate loss reason values on closed-lost deals migrate as a custom pick-list property in HubSpot named deal_loss_reason__c. The closed-lost reason options must be pre-created in HubSpot before the migration so the value mapping applies correctly. Historical deals that closed lost in Teamgate retain their reason value in HubSpot, preserving loss pattern reporting by reason category. If Teamgate used open-text loss reasons, they are mapped to a text field and flagged for manual review post-migration.

Teamgate owner assignments are resolved by email match against HubSpot Users. Unmatched owners are flagged in the pre-migration audit; you either invite them to HubSpot first or assign their records to a fallback owner before the migration runs. Owner names and email addresses are preserved on the migrated records. If a Teamgate owner has no email (a system owner), their records are assigned to the HubSpot admin owner by default.

Teamgate files attached to People, Organizations, or Deals are downloaded from the source storage location and re-uploaded to HubSpot Files. Each file is associated back to the migrated contact, company, or deal record using HubSpot's file association API. File size limits for HubSpot imports apply; files over 25MB are flagged and handled per your instruction. Inline images embedded in Teamgate notes are extracted and re-hosted as HubSpot file attachments.