Migrate from InTouch to HighLevel

InTouch custom fields span two object types in HighLevel

InTouch collapses contact-level and deal-level custom properties into a single custom field model. HighLevel separates Contact custom fields (personal data) from Opportunity custom fields (deal-specific data), and this type assignment is permanent — once created as one type, it cannot be switched. During migration planning, FlitStack audits every InTouch custom field and classifies each as Contact or Opportunity type in HighLevel before creating the field in your sub-account. Fields mis-assigned to the wrong object type require deletion and re-creation, which breaks any existing data already loaded under that field name.

InTouch's browser-based CSV export has size and encoding limits

InTouch's export process runs in the browser and generates CSV files asynchronously — for large datasets the file creation can queue for up to 1 hour. High-value data (custom field values with special characters, non-ASCII company names, or Unicode in note bodies) can corrupt during the CSV encoding step. FlitStack validates the InTouch export against a schema check before processing: any records with encoding errors are flagged with row numbers and corrected in the source before the migration pipeline runs, preventing silent data loss in HighLevel.

HighLevel's workflow automations have no InTouch equivalent

InTouch sequences and drip campaigns use a simple linear automation model (add contact → send email → wait N days → send next). HighLevel's workflow engine is trigger-based with IF/ELSE branching, wait-for-conditions, and action chaining — architecturally incompatible with a direct import. All InTouch automation logic must be rebuilt in HighLevel's Workflows builder. FlitStack exports your InTouch sequence definitions as a human-readable rebuild reference (stage names, delay lengths, email subject lines, trigger conditions) so your HighLevel admin can reconstruct them as HighLevel workflows.

HighLevel API rate limits require batched migration for large datasets

HighLevel's API allows 200,000 requests per day per sub-account with a 100-request-per-10-second burst limit. InTouch setups exceeding approximately 50,000 contacts, 20,000 companies, and 10,000 deals total will exceed a single-threaded API migration within the daily window. FlitStack uses HighLevel's Bulk CSV import endpoint (asynchronous backend processing) for large-record objects, falling back to paginated API writes for custom fields and activity history. This requires planning the migration run order so custom fields exist in HighLevel before bulk contact loads reference them.

InTouch owner-to-HighLevel-user resolution requires pre-provisioning

InTouch stores deal and contact owners as internal user references keyed by user ID. HighLevel requires all users to be manually provisioned with an email address before data can be assigned to them via the API. If InTouch has owner IDs with no corresponding HighLevel user (departed team members, inactive accounts), their records must either be re-assigned to an active HighLevel user or left unassigned. FlitStack generates a User Resolution Report listing every InTouch owner, their email, and their HighLevel provisioning status before the migration run commits.