Migrate from Xtremepush to Microsoft Dynamics 365 Sales

Xtremepush user profiles map to Microsoft Dynamics 365 Sales Contact for profiles with a known company affiliation or to Lead for anonymous or prospect-level profiles. We use the profile's xtremepush_user_id as a custom field (xp_original_user_id__c) for traceability. If the profile has an email address associated, it maps to Contact's Email field; if the email domain matches a configured Account domain, it links to the corresponding Account. Profile-level attributes and tags migrate to custom fields on Contact or to a dedicated Tags multi-select picklist field.

Push tokens cannot function across providers; APNS and Firebase tokens registered to Xtremepush are invalidated when the SDK is replaced. We export all device token records (token string, platform type, device model, registration timestamp) as a Note on the Contact record with a note titled 'Xtremepush Push Token Record' for the customer's mobile team to re-register against the new push provider post-migration. Token metadata does not activate in Microsoft Dynamics 365 Sales natively.

Xtremepush attributes (key-value pairs stored against user profiles) map to custom fields on the Dynamics Contact or Account object. We determine field type at migration scoping: numeric attributes become Decimal or Integer fields, date attributes become Date fields, boolean flags become Checkbox fields, and text attributes with a small cardinality become Picklist or Multi-Select Picklist. Tags with large cardinality are stored as a comma-delimited Text field or as a related Custom Object (Xtremepush Tags) with a lookup to Contact.

Xtremepush consent records specify preference type (Marketing, Legitimate Interest), subscription status, last-updated timestamp, and source. We map Marketing opt-in status to Dynamics HasOptedOutOfEmail. A custom field xp_consent_source__c (Picklist: manual, SDK, import) and xp_consent_type__c (Picklist: Marketing, Legitimate Interest) carry the full consent metadata. We flag records with only an import-source for compliance review before cutover, as Xtremepush consent exports do not include historical consent change audit trails.

Xtremepush segments are defined by attribute, event, and tag rules in Xtremepush-specific syntax. We export segment membership rules and the count of profiles in each segment at migration time. The rules cannot be imported into Microsoft Dynamics 365 Sales as a reusable segment definition. We document each segment as a written rule specification with equivalent Dynamics filter criteria so the customer's admin can recreate segments as Saved Views on Contact, Dynamic Microsoft 365 Groups, or Power Automate-triggered audience lists.

Xtremepush campaign metadata (name, schedule, trigger conditions, channel, content template reference) migrates to Dynamics 365 Campaign. Campaign type maps from the Xtremepush channel (push, SMS, email) to Dynamics Campaign Type. We do not migrate campaign content or creative assets; these are exported as a file package for the customer's design team to re-author in Dynamics-compatible templates. Automated journey triggers are not migrated as live workflows.

Xtremepush behavioral events (event type, timestamp, associated user/device) migrate to a custom Activity Log object in Microsoft Dynamics 365 Sales (or to Task records for lower-volume migrations) with fields for event_type__c, event_timestamp__c, and xp_user_id__c linking to the Contact. High-volume event exports (over 100,000 records) require Bulk API chunking with exponential backoff. Event cardinality can be high; we recommend the customer decide whether all historical events migrate or a recent-window snapshot (last 12 months) to control import scope.

Points balance, tier assignment, earned badges, and gamification achievements are stored as attributes on Xtremepush user profiles. We export these as custom fields on the Dynamics Contact record: xp_loyalty_points__c (Integer), xp_loyalty_tier__c (Picklist), xp_badges__c (Multi-Select Picklist), and xp_gamification_state__c (Long Text Area for JSON snapshot). The gamification rule engine (triggers, reward thresholds, achievement conditions) is not exposed via export and is documented as a written inventory for the customer to rebuild in Microsoft Dynamics 365 Sales or a loyalty ISV app.

Xtremepush geofence and iBeacon location metadata (coordinates, radius, venue UUID, beacon identifiers) migrates to a custom Location object in Microsoft Dynamics 365 Sales with a lookup to the Account representing the physical venue. Location permission state (user opt-in to location tracking) is a device-level flag that cannot be transferred and must be re-collected post-migration. We export all location configuration metadata for the customer's dev team to reconfigure in their new location services provider.

Xtremepush SFTP automated exports run on configurable schedules and produce CSV files of profile data, event data, or segment membership. We document each active export schedule, credential path, file schema, and delivery frequency. The Microsoft Dynamics 365 Sales equivalent is a Power Automate flow that queries the migrated data via the Dataverse API on the same schedule. We provide the documented export specification as a handoff to the customer's integration team.