Migrate from InTouch CRM to HubSpot

Direct map from InTouch Contact to HubSpot Contact. InTouch contact fields (firstname, lastname, email, phone, jobtitle, address, city, state, zip, country) map to HubSpot's default contact properties. Owner resolution uses email matching against HubSpot user email addresses. Any unmapped InTouch fields are flagged for custom property creation before migration.

InTouch contacts without a lifecycle-stage equivalent split to HubSpot Lead by default. If InTouch stores lead-status as a custom field, we route those records to HubSpot Lead and map the custom field value to HubSpot Lead Status. Contact records with confirmed customer status land as HubSpot Contact.

InTouch Company maps to HubSpot Company. HubSpot supports company domain-based duplicate detection on import. Parent-child company hierarchies in InTouch map to HubSpot's parent company field. Multi-company associations per contact collapse to HubSpot's primary-company model, with secondary associations surfaced via HubSpot company associations.

InTouch Deal maps to HubSpot Deal. HubSpot deal fields (dealname, amount, closedate, pipeline) map directly. InTouch deal stage names map to HubSpot deal stage values via a value-mapping table created during discovery. Deal owner resolves by email match to HubSpot user during migration.

InTouch's single pipeline model maps to one HubSpot Deal Pipeline. If InTouch stores pipeline as a custom field (common on lower tiers), we create a HubSpot Deal Pipeline and assign deals by that field value. Multi-pipeline InTouch setups create multiple HubSpot pipelines.

InTouch deal stage values map to HubSpot deal stage values via a per-pipeline value map. Stage order, probability, and forecast category are re-applied based on HubSpot's stage configuration. Stage-entered timestamps preserved as custom datetime properties for reporting continuity.

InTouch does not have a native lifecycle_stage property. If InTouch stores lead lifecycle or customer status as a custom field, we migrate it as a HubSpot custom pick-list property (lifecycle_stage__c) on Contact and set the correct values so HubSpot's lifecycle reporting and marketing automation trigger correctly.

InTouch engagement records map to HubSpot's native activity objects. Calls become HubSpot Calls, emails become Emails, meetings become Meetings, and notes become Notes. Original timestamps, owners, and parent-record links (contact, company, deal) are preserved. Activity associations are re-established during migration.

InTouch custom fields on Professional and Enterprise plans migrate as HubSpot custom properties. Field type is preserved (text, number, date, pick-list, checkbox). Pick-list values map via value-mapping tables. HubSpot property names use the InTouch field label converted to a URL-friendly slug if no native equivalent exists.

InTouch owner IDs resolve to HubSpot users by email address lookup. Unmatched owners are flagged before migration — your team either creates the HubSpot user first or assigns their InTouch records to a fallback HubSpot owner. No record lands without a HubSpot owner assigned.

InTouch file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files, linked to the appropriate HubSpot record. File size limits apply (HubSpot's 25MB per file). Inline images in notes are extracted and rehosted as HubSpot-hosted files.

InTouch workflow rules (follow-up sequences, lead assignment logic, reminder triggers) do not migrate. HubSpot's workflow engine uses a different trigger-and-action model. We export InTouch workflow definitions as a structured reference document for your HubSpot admin to rebuild in HubSpot's workflow builder.