Migrate from Touchdown to HubSpot

Touchdown contacts migrate as HubSpot contacts with all standard properties (name, email, phone, job title) preserved. Owner assignment resolves by email match against HubSpot users. Unmatched owners are flagged before migration commits so your team can invite them or assign a fallback owner.

If Touchdown uses a lifecycle-stage concept, values map value-by-value to HubSpot's fixed lifecycle_stage pick-list (subscriber, lead, MQL, SQL, opportunity, customer, evangelist). Any Touchdown values that don't match HubSpot's list are preserved as a custom text property and reviewed with your team before import.

Touchdown company records map directly to HubSpot company records. Company name, domain, industry, phone, and address fields map field-by-field. HubSpot's domain-based company creation can auto-merge companies for contacts sharing the same domain post-migration. If multiple Touchdown companies share the same domain, the auto-merge may create a single HubSpot company, consolidating contact associations. You can review the merged result in the pre-migration validation report and choose to disable auto-merge if a separate representation is required.

Touchdown deals map to HubSpot deals with deal name, amount, close date, owner, and stage preserved. HubSpot deal stages must be pre-created in your portal before the migration runs — we deliver a stage-mapping plan as part of the migration specification so your team creates the right stages in the right order.

Touchdown pipeline stages map to HubSpot deal pipeline stages. If Touchdown uses multiple pipelines, each becomes a separate HubSpot deal pipeline. Stage probability values are optional in HubSpot but we recommend setting them for accurate forecasting — we apply your specified probability values per stage during import.

Touchdown campaign enrollment (which contacts were enrolled in which campaigns) migrates as HubSpot static lists. Each Touchdown campaign becomes one HubSpot list with the enrolled contacts. Active list enrollment criteria cannot transfer — those sequences must be rebuilt in HubSpot workflows using the exported campaign definitions as a reference.

Touchdown email activities (sent, opened, clicked) migrate as engagement records linked to the contact in HubSpot. Original timestamps and email subject lines are preserved. Full email body content migrates as a note attached to the contact record when available via API.

Touchdown calls, meetings, and notes migrate as HubSpot engagements with original timestamps, owners, and subject lines preserved. Call duration and meeting end times are mapped to HubSpot's engagement metadata fields where the platform exposes them. If a call or meeting includes attendees not already in HubSpot, they are added as contacts and linked to the engagement record, ensuring complete activity context.

Touchdown file attachments associated with contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Files are re-attached to the corresponding records. HubSpot's file storage limits apply — we surface any files exceeding the size threshold before the migration run.

Any custom properties defined on Touchdown contacts, companies, or deals are created as HubSpot custom properties (or custom objects if they represent a separate entity type). We infer the HubSpot field type (text, number, date, picklist) from the source data type and validate the mapping in the sample migration before the full run.

Touchdown owner IDs are resolved by email address against HubSpot user accounts. Contacts and deals without a matched HubSpot user are flagged in the pre-migration report — your team either creates the HubSpot user account or designates a fallback owner before the migration commits.

The original Touchdown record ID is stored as a custom property on each HubSpot record for traceability, delta-run deduplication, and audit purposes. This allows subsequent delta migrations to identify records that were created or updated in Touchdown after the initial migration run.