Migrate from TeamWave to HubSpot

Direct map. TeamWave contacts migrate as HubSpot contacts with all standard properties. The primary company link maps as a HubSpot company association. Multi-company contacts (TeamWave allows linking a contact to multiple organizations) collapse to one primary company in HubSpot.

Direct map. TeamWave companies migrate as HubSpot companies with all standard properties. Company hierarchies (parent-child) preserve using HubSpot's parent company lookup. Multi-branch organizations use the parent company link. All standard company fields such as industry, phone, and address are transferred as-is.

Direct map. TeamWave contacts migrate as HubSpot contacts with all standard properties. The primary company link maps as a HubSpot company association. Multi-company contacts (TeamWave allows linking a contact to multiple organizations) collapse to one primary company in HubSpot. Standard contact fields such as name, email, phone, and job title are transferred directly.

Stage names map value-by-value from TeamWave pipeline stages to HubSpot deal stages. We preserve the stage order and probability percentage from TeamWave and apply them to the corresponding HubSpot stage. Teams can review the value map before migration commits. If stage names differ, we flag them for manual review to avoid data loss.

HubSpot has no native lifecycle stage field. TeamWave lifecycle stage migrates as a custom pick-list property (Lifecycle_Stage__c) on both Contact and Deal. Original stage values are preserved verbatim. Stage-transition timestamps migrate as a secondary custom datetime property if TeamWave tracks them.

TeamWave logged calls map to HubSpot calls, emails to HubSpot emails, meetings to HubSpot meetings, and notes to HubSpot notes. Original timestamps and owner assignments are preserved. Activity text content migrates as-is. Any attachments or call recordings associated with activities are also transferred, subject to HubSpot file size limits.

TeamWave file attachments on records re-upload to HubSpot Files and attach to the corresponding CRM record. Files under HubSpot's size limits (25MB per file) migrate directly. Files exceeding the limit are flagged for manual handling. We also verify file integrity after upload to ensure no corruption during transfer.

TeamWave users resolve to HubSpot users by email match. We check each TeamWave owner email against HubSpot user accounts and flag unmatched owners before migration. Teams either invite the user to HubSpot first or reassign records to a designated fallback owner.

TeamWave project records have no native HubSpot CRM equivalent. Teams choose between three paths: create a HubSpot custom object for projects, add project reference as custom properties on the related deal, or handle project data in a separate project management tool post-migration. We surface the decision before migration runs.

TeamWave tasks and sub-tasks attached to projects require a team decision on handling. Tasks linked to CRM records (contacts, deals) can migrate as HubSpot tasks with the project reference preserved as a custom property. Standalone project tasks may need a custom object or external reference list.

TeamWave HR records have no HubSpot CRM equivalent. Employee data does not migrate to HubSpot CRM — teams handle this in HR tools outside HubSpot or manually recreate employee records if needed. We provide a structured export of HR data for reference.

TeamWave custom contact, company, and deal fields migrate as HubSpot custom properties. Type-aware mapping applies: date fields convert to HubSpot datetime format, number fields preserve as numeric, and pick-list fields require value-by-value mapping against the TeamWave option list. Any missing custom properties are created in HubSpot before the migration run begins.

TeamWave workflows and automations do not migrate. They have to be rebuilt in HubSpot using HubSpot Workflows and Sequences. We export your TeamWave workflow definitions as a structured reference document for your HubSpot admin to use during rebuild. The exported definitions include trigger events, conditions, and action steps for accurate recreation.