Migrate from Insider to HubSpot

Insider user profiles map 1:1 to HubSpot Contacts. Primary identity resolved by email — if an Insider profile lacks email, we flag it for manual review. The Insider uuid is stored in a custom Source_ID__c field for traceability and delta-run de-duplication.

Insider company records map to HubSpot Accounts. Company-to-contact associations in Insider translate to the Account lookup on HubSpot Contacts. Multi-contact accounts are preserved — each contact links to one primary Account. The mapping preserves the parent-child relationships between companies, ensuring organizational hierarchies transfer correctly.

Insider transaction records map to HubSpot Deals. Deal properties (amount, stage, close date) translate to HubSpot Deal fields. Pipeline association in Insider maps to HubSpot's Deal Pipeline field. The mapping also preserves deal currency, owner assignments, and any custom deal-level attributes that exist in the source system.

Insider event data (page_view, purchase, custom events) has no native HubSpot equivalent. We transform high-value events into HubSpot engagement notes or custom activity properties on the Contact. Original event timestamp and event type are preserved. Low-value event types may be summarized or excluded based on migration scope.

Insider segments with static membership map to HubSpot static lists. Dynamic segments with rule-based membership map to HubSpot Smart Lists — however, Insider segment rules need manual translation to HubSpot filter logic. We deliver a segment mapping document listing each Insider segment and its recommended HubSpot equivalent.

Insider profile attributes that map to HubSpot native properties (email, phone, firstname) use direct mapping. Attributes with no HubSpot equivalent (loyalty_tier, credit_score, custom behavioral scores) become HubSpot custom contact properties. Custom properties use the __c suffix in HubSpot's data model.

Insider user tags do not map to a native HubSpot construct. We migrate tags as a custom multi-select property (Tags__c) on the Contact. Tag values are preserved verbatim — HubSpot's multi-select field type handles the list of values. Multi-select fields display tags as a comma-separated list on the contact record.

Insider's internal uuid has no HubSpot equivalent. We store it as a custom text field (Source_ID__c) on the Contact for reconciliation, deduplication across delta runs, and traceability if future data corrections are needed. The Source_ID__c field is indexed for fast lookups during reconciliation.

Insider lifecycle or status properties map to HubSpot's built-in lifecycle_stage property when present. If Insider uses a custom status field (e.g., customer_type, account_status), we map it to a HubSpot custom property. HubSpot's lifecycle_stage accepts values like subscriber, lead, MQL, SQL, opportunity, customer, evangelist.

Insider journey definitions and automation logic are proprietary constructs that do not export via API in a form that maps to HubSpot workflows. We document each active journey's trigger, steps, and conditions as a rebuild reference for your HubSpot admin. The migration data carries forward; the automation logic must be recreated in HubSpot.

Insider company hierarchies map to HubSpot Account ParentId. The parent company must be migrated first; we sequence the load to resolve parent references before child accounts land. Circular references are flagged before the migration runs. Account hierarchies preserve organizational structure for enterprise accounts with subsidiary relationships.

Insider engagement records (email opens, push notifications, in-app messages) translate to HubSpot engagement types. Email engagement maps to HubSpot email activities. Push and in-app records are surfaced as custom note activities or custom contact properties based on relevance — the original engagement timestamp and channel are preserved.