Migrate from Contlo to HubSpot

Direct map. Contlo contact records land as HubSpot contacts with original email, phone, name, and address fields preserved. Owner resolution happens by email match against HubSpot users — unmatched owners flagged before migration commits. The mapping preserves the original create date as a custom field since HubSpot sets its own creation timestamp at import time. All standard contact properties transfer directly without transformation.

Contlo tracks AI agent interactions as custom contact attributes. We migrate these as HubSpot custom properties using the contlo_ prefix to preserve traceability. HubSpot has no native AI agent interaction field — manual analysis determines which metrics to surface in HubSpot workflows.

Direct map. Contlo company records map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue fields migrate as HubSpot standard properties. Multi-contact companies resolve to one HubSpot company record with associated contacts. The original Contlo company creation timestamp is preserved as a custom datetime property since HubSpot sets its own create date at import time.

Contlo campaign records migrate as HubSpot campaigns with membership preserved. Engagement metrics (open rate, click rate, send volume) migrate as HubSpot custom numeric properties because HubSpot tracks engagement differently. Original send timestamps are preserved as campaign custom datetime fields. Campaign status and type map directly to HubSpot campaign fields. Each contact's campaign membership history is preserved in HubSpot's campaign member object.

Contlo segment definitions do not migrate as HubSpot lists or smart lists because the underlying filter logic differs between platforms. FlitStack exports segment logic as a rebuild reference document with filter criteria mapped to HubSpot's list builder syntax. Teams recreate segments in HubSpot using static lists or smart lists, or through HubSpot's Contacts filter, guided by the exported segment criteria document delivered in the migration package.

Contlo automations — multi-step flows with conditional branches, delay nodes, and AI agent calls — cannot migrate to HubSpot workflows due to architectural differences. FlitStack exports automation definitions as a structured JSON file plus human-readable documentation for manual rebuild in HubSpot's workflow builder. The export includes trigger conditions, each automation step, branch logic, and AI agent configuration details so teams can recreate equivalent workflows in HubSpot.

Contlo AI agents (voice agents, outbound agents) have no HubSpot equivalent. Agent configuration, prompt templates, and conversation logic are exported as a rebuild reference. Teams implement equivalent functionality in HubSpot using Workflows, Sequences, and calling logic via HubSpot's API or partner tools.

Contlo engagement events (opens, clicks, unsubscribes) populate HubSpot contact timelines as engagement notes. HubSpot does not store granular per-email engagement as separate records — instead, we attach a consolidated engagement summary to the contact and preserve raw data in a custom long-text field.

Any Contlo custom contact attributes migrate as HubSpot custom properties with the contlo_ prefix. Property type (text, number, date, dropdown) is inferred from the source data. Picklist values are mapped value-by-value where HubSpot dropdown options exist or created as new options.

Contlo users and owners resolve to HubSpot users by email address match. Unmatched owners are flagged before migration — teams either create HubSpot user accounts first or assign records to a fallback owner. Owner history is preserved as a custom field on each record.