Migrate from Xtremepush to HubSpot

Xtremepush user profiles map directly to HubSpot contacts. The user's email, phone, and name fields translate to HubSpot's standard contact properties. Unique Xtremepush user ID preserved as Source_System_ID__c for delta-run de-duplication. This mapping ensures each contact can be traced back to its original Xtremepush record for future sync.

Users with no sales engagement history in Xtremepush route to HubSpot Leads. Users with open deals, campaign responses, or lifecycle activity route to HubSpot Contacts based on engagement scoring rules defined during discovery. Lead routing helps maintain data hygiene and aligns with HubSpot's lifecycle stage definitions.

Xtremepush organization records linked to user profiles map to HubSpot companies. Company name, domain, and industry fields translate directly. Parent-child hierarchies in Xtremepush preserve as HubSpot company associations. This ensures corporate structures and subsidiary relationships are maintained for accurate reporting and segmentation.

Xtremepush tags and behavioral attributes that have no HubSpot standard equivalent become custom contact properties. Property type inferred from Xtremepush data type (string, number, boolean, date). Tag values with multiple options map to HubSpot picklist properties. All custom properties are labeled with source tags for auditability.

Xtremepush stores APNS and Firebase Cloud Messaging tokens per device per user. These have no native HubSpot equivalent. We create a custom text property (e.g., Push_Token__c) per channel and populate it for re-engagement campaigns post-migration, though the tokens may expire and require fresh SDK enrollment.

Xtremepush tracks channel-specific consent (push, SMS, email, web) with status (subscribed, unsubscribed), source, and timestamp. HubSpot's subscription type model covers email and SMS; push consent migrates as a custom boolean property. The original consent timestamps preserved as custom datetime fields for audit compliance.

Xtremepush campaign definitions (name, channel, schedule) map to HubSpot Campaigns. Campaign engagement history (sends, opens, clicks, deliveries) translates to HubSpot engagement records linked to contacts — though HubSpot analytics dashboards must be rebuilt to match Xtremepush reporting depth. Post-migration reporting should be validated against historical data.

Xtremepush engagement events per user become HubSpot engagement records. Opens and clicks attach as notes or emails to the contact record. Conversion events attach as custom activity notes with campaign attribution preserved. These records maintain the timeline of user interactions for future analysis and reporting.

Xtremepush geofence and iBeacon trigger data attached to user profiles migrates as custom contact properties (last_known_location, geofence_triggers) and notes describing the location context. Location data is point-in-time and does not become a live map feature in HubSpot. Use these fields for segmentation based on past location activity.

If Xtremepush gamification features (points, levels, badges) are in use, these migrate as custom numeric and picklist properties on the contact. HubSpot has no native loyalty object — the gamification logic and reward rules must be rebuilt using HubSpot workflows or a dedicated loyalty app.

Xtremepush audience segments with static membership migrate to HubSpot static lists. Dynamic segments with behavioral rules do not transfer — HubSpot requires equivalent list-building logic using its own filters and workflows post-migration. Static list migration preserves existing group definitions for immediate marketing campaigns.

Xtremepush session and behavioral event data (page views, in-app actions, feature usage) has no direct HubSpot equivalent at the contact level without a separate event-tracking tool. We preserve raw event payloads as a custom long-text property for reference but recommend HubSpot's built-in event tracking or a CDP integration for future behavioral analysis.