Migrate from Teamwork CRM to HubSpot

Teamwork Contact maps directly to HubSpot Contact. HubSpot uses a flat properties bag; Teamwork properties become HubSpot properties on the contact record. The Teamwork contact's primary company link becomes HubSpot's primary company association. All standard fields such as name, email, phone, and address are transferred as-is, while any custom fields are created as HubSpot properties before import.

Teamwork's separate Leads pipeline has no HubSpot equivalent — HubSpot has one Contact object. Teamwork lead records route to HubSpot Contacts with lifecycle_stage set to the stage that corresponds to the lead's pipeline position. The original pipeline-stage value is preserved in a custom property for reporting continuity.

Teamwork Company maps 1:1 to HubSpot Company. Company name, domain, industry, employee count, and annual revenue map directly to HubSpot company properties. HubSpot supports parent-company hierarchies via the parent_company_id property. Additional address fields such as city, state, and country are also mapped to HubSpot's corresponding company properties, preserving location context.

Teamwork Deal maps to HubSpot Deal. Each Teamwork deal pipeline becomes a HubSpot deal pipeline. Deal name, amount, close date, owner, and stage map directly. Stage values map value-by-value per pipeline to maintain deal probability semantics. Any custom deal fields are transferred as HubSpot custom properties, and deal-associated activities are linked via the engagement API.

Teamwork pipeline stage names map to HubSpot dealstage values value-by-value within each pipeline. Stage order and probability weights are reapplied from Teamwork's stage configuration. Original stage-entered timestamps are preserved in a custom datetime property. If a stage is inactive in Teamwork, it is still migrated but marked inactive in HubSpot until you activate it.

Teamwork activities map to HubSpot engagements: calls become HubSpot call engagements, emails become email engagements, meetings become meeting engagements, and notes become HubSpot notes. Original timestamps, owners, and linked contact/company/deal associations are preserved. Activity bodies are stored as engagement body text, and attachments are imported via HubSpot's file management API.

Teamwork contact custom fields map to HubSpot contact custom properties. HubSpot property names use snake_case internally. Text, number, and dropdown field types map directly; multi-select dropdowns require HubSpot property type configuration. We create any missing HubSpot properties before import. If a Teamwork field uses a picklist, the possible values are preloaded into HubSpot as option labels for the select property.

Teamwork deal custom fields map to HubSpot deal custom properties. Type-aware mapping applies: Teamwork number fields become HubSpot number properties, pick-list fields become HubSpot select/multi-select properties. We flag any HubSpot property type that requires admin-side configuration before import. For date fields, we map them to HubSpot datetime properties and preserve the original UTC timestamps to ensure reporting continuity.

Teamwork user IDs resolve to HubSpot owners by email address match. We pull the Teamwork user list, match by email against HubSpot users, and flag any Teamwork owner with no HubSpot match before migration so your team can invite them or assign records to a fallback owner.

Teamwork file attachments on contacts, companies, and deals download from Teamwork and re-upload to HubSpot Files. Files are linked to the corresponding HubSpot record. File size limits apply per HubSpot's file hosting constraints. If a file exceeds HubSpot's size limit, we store the file URL in a custom property and link to the external source instead.

Teamwork tags on contacts and deals map to HubSpot custom properties of type 'string' or 'enumeration' depending on whether the tag set is open or closed. We create the property in HubSpot and populate it during import. If tags contain hierarchical values, we flatten them into a delimited string property to preserve hierarchy in a simple format.

Teamwork allows a contact to be associated with multiple companies (N:1 from contact perspective). HubSpot contacts have one primary company. We migrate the most-recently-modified or first-listed company as primary and surface additional companies in a custom multi-select property or association field for reference.