Migrate from Actito to HubSpot

Actito profiles map 1:1 to HubSpot contacts. Every Actito profile attribute becomes a HubSpot contact property. Where Actito stores a profile with no email, we flag it for review before migration to avoid landing uncontactable records in HubSpot for quality assurance.

Actito custom table columns attached to a profile migrate as HubSpot custom contact properties. We create each property in HubSpot matching Actito's field type (text, number, date, picklist, boolean) before the bulk import runs. We also verify field length constraints and required status before import runs.

Actito custom tables not linked directly to profiles require a destination model decision: if the table represents a Company-scoped object, we migrate it as Company custom properties; if it is an independent entity, we create a HubSpot custom object and establish the relationship via a lookup field.

Actito email campaign sends become HubSpot logged emails on the contact timeline with original send timestamp, campaign name, and subject line preserved. The HubSpot engagement type is 'EMAIL' and the activity date matches Actito's event timestamp, and additional metadata fields.

Actito email open events map to HubSpot email_open engagements on the contact record. Each open event preserves the original Actito event timestamp and campaign identifier so attribution reporting reflects the source campaign and provides clear visibility into recipient interaction patterns.

Actito click events migrate as HubSpot email_click engagements including the URL clicked and the referring campaign. HubSpot's engagement model records the clicked URL as a property on the engagement record. These URL details enable detailed click‑through analysis and help identify high‑value content paths for future campaigns.

Hard bounces and unsubscribe events from Actito set corresponding HubSpot contact properties: email_bounce = true and hs_email_unsubscribe = true. Soft bounces are preserved as a note or custom property for admin review rather than a hard flag for accurate list hygiene.

Actito entities partition data per brand or division. In HubSpot, we map entities to Teams (if on a single portal) or recommend separate HubSpot sub-portals for strict data isolation. The migration plan flags entity-to-team mappings for your admin to configure before data lands.

Actito opt-in and preference flags migrate to HubSpot's standard subscription properties. We preserve the original subscription source and timestamp as custom properties since HubSpot tracks opt-out at the list level rather than per-campaign to ensure compliance and maintain historical communication preferences across campaigns.

Actito scenario-based workflows scoped to entities have no direct equivalent in HubSpot's workflow engine. We export the Actito scenario definitions as JSON including trigger conditions, audience filters, and action sequences for your HubSpot admin to rebuild using HubSpot Workflows post-migration.

Actito target lists and segments migrate as HubSpot static lists by default. If the Actito segment uses dynamic inclusion rules, we document the criteria so your team can recreate it as a HubSpot active list with the equivalent property filters.

Actito A/B test results (variants, open rates, click rates) are preserved as a custom object in HubSpot linked to the campaign. HubSpot's built-in reporting does not replicate Actito's A/B test comparison view, so we surface the historical data as a reference report rather than a live dashboard element.