Migrate from Customer.io to HighLevel

Customer.io People records map to GoHighLevel Contacts. The userId becomes the Contact email or a matched external ID. AnonymousId is preserved in a custom field if the GoHighLevel account has custom field capacity. Traits (key-value pairs) migrate to GoHighLevel custom contact fields, with JSON array and nested object traits flattened to comma-separated strings or stored in a custom field with JSON encoding. Active versus inactive status from Customer.io becomes a Contact tag (active_profile / inactive_profile). Profile creation timestamps migrate to a custom field for historical record.

Customer.io Custom Objects with object_type_id representing Companies or Accounts map to GoHighLevel Accounts. We resolve the relationship between a Customer.io Person and their associated Company via the relationships API and map it to the GoHighLevel Account-Contact lookup. Company attributes become Account custom fields. If Customer.io Companies are linked to multiple People, the Account record is created first and Contact linking happens after Account insert to satisfy the lookup dependency.

Customer.io custom events (track() calls with name and properties) do not have a native GoHighLevel equivalent because GoHighLevel activity logs are task-based rather than event-based. We assess each event name: high-signal behavioral events (purchase, upgrade, subscription_renewed) migrate to GoHighLevel custom object records with timestamp and properties. Lower-frequency or informational events migrate as custom fields on the Contact record with the last-occurrence value and timestamp. The customer chooses the strategy during scoping based on how they intend to use behavioral data in GoHighLevel workflows.

Customer.io Segments are dynamic audience definitions based on trait values and event conditions. We export segment criteria as a structured rule set and map them to GoHighLevel tags (for simple audience flags) and GoHighLevel Contact Filters (for multi-condition dynamic audiences). Each Contact receives the corresponding tags from their source segment membership at the time of migration. GoHighLevel Contact Filters rebuild the dynamic aspect of the segment post-migration using the same conditions the customer defines.

Customer.io Campaigns and Journeys with active membership at migration time are exported as tag records on each Contact (e.g., campaign_name_enrolled, campaign_name_active). The tag format preserves campaign name and enrollment date. GoHighLevel does not replicate Campaign automation logic from Customer.io; this is documented in the inventory handoff for the admin to rebuild as GoHighLevel Workflows. Campaign status (active, completed, cancelled) maps to a secondary tag for audit purposes.

Customer.io Broadcast records (one-time sends with target segment, content, and send timestamp) migrate as GoHighLevel Workflow records with a manual or scheduled trigger and a tag-based audience condition. The broadcast content is not stored in GoHighLevel in the same broadcast log format; we preserve the send timestamp, segment name, and recipient count as a migration audit record. GoHighLevel's one-time send equivalent is a Workflow with a bulk tag-action that the admin finalizes with the migrated content.

Customer.io Custom Objects beyond Companies (object_type_id namespaces with their own object_id per record) map to GoHighLevel Custom Objects. We pre-create the GoHighLevel custom object schema during scoping, including all custom fields, field types, and lookup relationships to Contact or Account. Relationships between Customer.io People and their custom object records are resolved via the relationship export and mapped to GoHighLevel custom object lookup fields. Custom object record import follows the Contact and Account import to satisfy any lookups.

Customer.io transactional messages (receipts, password resets, order confirmations) store content that may be redacted if message retention is disabled on the source account. We export what is available (recipient, timestamp, message type, delivery status) and flag any redacted payloads. Transactional message content migrates to a GoHighLevel custom object with a compliance flag field. GoHighLevel does not have a native transactional message log equivalent, so the migration record serves as the audit trail for compliance purposes.