Migrate from InTouch to HubSpot

InTouch custom fields are matter-template-scoped — mapping requires template inventory first

InTouch defines custom fields per matter template, meaning the same field name may appear across multiple templates with different data types or pick-list values. Before any field maps to a HubSpot property, we inventory every InTouch matter template in use, resolve field-name collisions, and determine whether fields should map to contact, company, or deal properties in HubSpot. A field named 'referrer_source' on a contact template and a deal template becomes two separate HubSpot custom properties unless your team elects to consolidate them. Skipping this inventory step causes type-mismatch errors during HubSpot import and requires a re-migration of affected records.

InTouch deal pipelines require pre-creation in HubSpot before field mapping validates

HubSpot deal stages are scoped to a specific deal pipeline — you cannot import a deal with a stage value unless the pipeline and its stage pick-list already exist in HubSpot. InTouch does not expose pipelines as a first-class API object, so we extract pipeline and stage names from InTouch deal records, group them by unique pipeline, and deliver a pipeline-setup plan for your HubSpot admin to create before the migration import runs. If a new pipeline is created in HubSpot after the migration import has already validated field mappings, the stage pick-list may need re-mapping and the deal records re-imported.

HubSpot's marketing contact billing flag has no InTouch equivalent — intentional decision required

HubSpot bills on marketing contacts when email-sending is active, but InTouch has no concept of a marketing-contact flag. When migrating contacts that have received InTouch-tracked emails or were added through InTouch marketing features, your team must decide whether those contacts should be marked as marketing contacts in HubSpot or remain as CRM-only contacts. This is not an automated mapping — it is a business decision. We surface the count of contacts with marketing engagement history before migration so you can evaluate the billing impact and set the flag intentionally.

InTouch activity history requires multiple API calls per record — large datasets increase migration clock time

InTouch's API exposes engagement records (calls, emails, meetings, notes) as separate sub-objects attached to contacts and deals. There is no bulk-export endpoint for activity history equivalent to a contact export. For datasets with 50,000+ contacts and significant activity volume, fetching activity records individually can push the migration window beyond 48 hours. We throttle API requests to stay within InTouch's rate limits, and we batch activity writes to HubSpot's engagement API. If your InTouch plan has lower API rate limits, we surface that during scoping and adjust the migration timeline accordingly.

InTouch owner-to-user email resolution may leave orphan records if HubSpot user list is incomplete

We resolve InTouch owners by matching the owner email address against HubSpot user email addresses. If an InTouch owner email does not match any existing HubSpot user, that owner is flagged as 'unresolved' before the migration commits. The corresponding records are held and assigned to a designated fallback owner — or your team creates HubSpot user accounts for the unresolved owners before cutover. Orphaned records (records with no resolvable owner) cause reporting gaps in HubSpot's owner-based dashboards. We provide a pre-migration owner audit report so this gap is closed before data lands.