Migrate from Agillic to HubSpot

Agillic recipient profiles migrate to HubSpot contacts. HubSpot requires a valid email address to create a contact — recipients without email addresses are flagged and exported to a separate exception report for manual review. All standard recipient fields (email, first name, last name, phone, address components) map to their HubSpot contact equivalents.

Agillic's self-defined recipient properties map to HubSpot contact properties. We match property names to existing HubSpot properties by label and API name, or create new HubSpot properties preserving the original data type. Pick-list properties require value-by-value mapping; multi-select properties are stored as comma-separated strings or as HubSpot multi-checkbox properties depending on HubSpot tier availability.

Companies linked to recipients in Agillic migrate to HubSpot companies. Where Agillic recipients reference a company by name without a separate company record, we create a HubSpot company from the name and link it to the contact. Parent-child company hierarchies in Agillic map to HubSpot's parent company field — circular references are flagged before migration.

Agillic global data tables map 1:1 to HubSpot custom objects. Each row in a global data table becomes a custom object record in HubSpot. Field types are preserved: text fields become text properties, date fields become date properties, and pick-list fields map to HubSpot pick-list properties. We validate that the table schema fits within HubSpot's custom object limits per tier.

Agillic global data tables used to represent many-to-many relationships between entities translate to HubSpot junction objects. The junction object holds foreign keys to both related custom object records. We create the junction object schema in HubSpot, map each relationship row, and configure the association labels before the migration runs.

Email open events from Agillic activity exports become HubSpot email engagement logs attached to the contact record. The original timestamp of the open, the subject line, and the email campaign name are preserved as properties on the engagement log. Multiple opens of the same email are preserved as separate engagement events.

Email click events from Agillic activity exports map to HubSpot email engagement logs on the contact record, with the clicked URL and timestamp preserved. The link URL is stored in a custom property on the engagement log for reporting on digital engagement intensity.

Unsubscribe events from Agillic activity exports update the HubSpot contact's email unsubscribe property and are also logged as an engagement event for auditability. The original unsubscribe timestamp is preserved. We validate that the contact exists in HubSpot before writing the unsubscribe property — orphan events are logged separately.

Agillic SMS sends and push notifications map to HubSpot call engagement logs on the contact record, since HubSpot does not have a native SMS engagement type. The original send timestamp, message content, and SMS campaign name are preserved as properties on the engagement log.

Agillic flow execution IDs linked to recipients are stored as a custom property on the HubSpot contact — a number or text property depending on the ID format. This preserves the audit trail of which campaigns reached each contact. Flow execution metadata (execution timestamp, flow name) is stored in a secondary custom property for reference.