Migrate from Inflection.io to HubSpot

Inflection.io persons map directly to HubSpot contacts. The email address is the primary key for de-duplication. First name, last name, phone, job title, and address fields map to HubSpot's standard contact properties. Behavioral scores and journey enrollment status migrate as custom contact properties.

Inflection.io companies map to HubSpot companies with domain-based matching to link contacts. Industry, employee count, revenue, and address fields map to HubSpot's standard company properties. Parent-company hierarchies in Inflection map to HubSpot's parent company association. For companies without a clear domain match, we use fuzzy name matching and manual review to ensure correct linking before finalizing the company merge.

Journey enrollment status and last-enrolled date cannot map to a native HubSpot object. We create custom contact properties (e.g., Journey_Name_Enrolled__c, Journey_Status__c) and enroll contacts in corresponding HubSpot lists to replicate segment visibility for marketing ops teams. The custom properties store the journey name and enrollment timestamp, while list membership provides a way to segment contacts based on their Inflection journey enrollment without requiring immediate workflow recreation.

Inflection.io product events (feature used, plan upgraded, key action completed) have no native equivalent in HubSpot CRM. For Enterprise tiers, we create a Product_Event custom object with fields for event type, timestamp, product ID, and associated contact. For lower tiers, events flatten into contact properties or association notes.

Inflection.io calculates behavioral scores based on product activity, email engagement, and journey progression. We migrate the current score value as a numeric custom property (e.g., Behavioral_Score__c) on HubSpot contacts. Historical score changes are not available via API and cannot be migrated.

Inflection.io dynamic segments (built from product events, CRM data, and warehouse joins) cannot replicate as HubSpot lists because HubSpot's list filtering cannot span product events or data warehouse fields. We migrate segment membership as a static list snapshot at migration time; dynamic behavior requires manual segment recreation in HubSpot.

Inflection.io campaigns and batch sends map to HubSpot marketing emails and campaigns. Email content, subject lines, and send history migrate as HubSpot campaign records. Template metadata migrates as HubSpot email templates. AI-generated email variants are not supported for migration — content must be reviewed and recreated.

Inflection.io's account model links persons and companies. We split this into HubSpot contacts linked to HubSpot companies via the primary company association. Additional company relationships from Inflection account records migrate as secondary company associations or custom association records. This approach preserves the account hierarchy while ensuring each person record maintains accurate company linkage in HubSpot's CRM without duplicating company records.

Inflection.io form submissions map to HubSpot contacts with submission timestamps and UTM property capture. If HubSpot forms were the destination for Inflection's form API, form IDs map to HubSpot form GUIDs for attribution continuity. This mapping ensures that form submission history is preserved in HubSpot, allowing marketing teams to track which forms contacts submitted and maintain UTM parameter data for campaign attribution analysis.

Inflection.io users match to HubSpot users by email address. We resolve Inflection owner IDs to HubSpot user IDs for contact and deal ownership. Unresolved owners receive a fallback assignment to a migration admin user and are flagged for manual reassignment.

Inflection.io custom person properties (beyond standard fields) map to HubSpot custom contact properties. We create the property in HubSpot with the matching field type (text, number, date, picklist) before importing data. Picklist values require value-by-value mapping if the options differ between platforms.

Inflection.io custom company properties migrate to HubSpot custom company properties using the same type-aware mapping as person properties. Company-level product associations (which Inflection stores on the company) map to a custom company property or custom object depending on data complexity.