Migrate from Xtremepush to Salesforce Sales Cloud

Xtremepush user profiles with an email address and a sales-qualified interaction history (campaign response, deal-linked engagement) map to Salesforce Contact attached to an Account. Profiles without a qualifying interaction history but with a captured email (newsletter subscriber, campaign impression recipient) map to Salesforce Lead. We evaluate the Xtremepush profile's last_campaign_action timestamp, any associated deal linkage, and the consent type to determine the split. The original Xtremepush profile identifier is preserved in a custom field xp_profile_id__c on both Lead and Contact for audit.

Xtremepush profiles that are email-captured but have no Salesforce-worthy sales relationship (pure marketing subscribers) map to Salesforce Lead with a custom field xp_profile_id__c and a lead source set to Xtremepush for campaign attribution. These Leads can be converted to Contacts when a sales rep qualifies them.

Xtremepush attributes (key-value pairs stored on a profile) map to Salesforce custom fields on Contact or Lead depending on the profile split. Standard attributes like email, phone, first_name, and last_name map to standard Salesforce fields. Custom attributes map to custom fields with the API name derived from the Xtremepush attribute key (xp_attribute_[key]__c). Multi-value attributes map to multi-select picklists.

Xtremepush tags stored as multi-value profile attributes migrate to Salesforce multi-select picklist fields on Contact or Lead. Tags used for audience classification migrate to Salesforce Topics with TopicAssignment records linked to the Contact or Lead. The customer chooses the tagging strategy during scoping.

Xtremepush consent records carry preference type (Marketing, Legitimate Interest), status (subscribed/unsubscribed), last-updated timestamp, and source. We map Marketing consent status to Salesforce HasOptedOutOfEmail and create a custom field xp_consent_type__c with the preference type value. The consent source (manual, SDK, import) is stored in xp_consent_source__c for audit. Full consent audit trail (historical changes) is not available from Xtremepush export and is flagged as a compliance gap for regulated industries.

Xtremepush campaigns (push, SMS, email execution units) map to Salesforce Campaign records. Campaign name, type, channel, and scheduled time migrate. Campaign status maps to Salesforce Campaign Status (Planned, In Progress, Completed, Aborted). The Xtremepush campaign identifier is preserved in xp_campaign_id__c on the Salesforce Campaign for audit.

Xtremepush campaign event history (impressions, clicks, conversions, unsubscribes) migrates as CampaignMember records linked to the corresponding Salesforce Campaign and the target Contact or Lead. Event type, timestamp, and campaign response status map to CampaignMember Status (Sent, Delivered, Opened, Clicked, Unsubscribed, Converted). Large event histories require Bulk API chunking to avoid Salesforce governor limits.

Xtremepush audience segments (defined by attribute, event, and tag rules) migrate as static Salesforce Campaign membership lists. We export the segment membership at migration time as a list of profile identifiers, then add those profiles to the corresponding Salesforce Campaign as CampaignMember records. The segment rule logic (Xtremepush-specific query syntax) is documented in the migration inventory for the customer to rebuild using Salesforce Reports and Filters or a segmentation tool. Dynamic segment rebuild is out of migration scope.

Xtremepush device tokens are tied to the Xtremepush SDK install state and cannot be directly migrated as active push delivery records to Salesforce. We export all device token records as a CSV (token, device OS, user profile ID, last_active timestamp) and document the token re-registration workflow for the customer's mobile dev team to implement against Salesforce MobilePush or their chosen push provider in the new app build. The CSV is a handoff document, not a live record migration.

Xtremepush loyalty points balances are stored as numeric attributes on user profiles. We migrate the current points balance as a custom field xp_loyalty_points__c on the Salesforce Contact record. Tier assignments migrate to xp_loyalty_tier__c. These are point-in-time state snapshots, not a loyalty ledger; the gamification rule engine (points-earning triggers, reward thresholds, badge award rules) is not exposed via export and is documented in the migration inventory for the admin to configure in Salesforce or a loyalty management app.

Xtremepush gamification achievements (badges, milestones, challenges) are stored as attributes or tags on user profiles. We migrate earned achievements as custom fields (xp_badge_[name]__c for named badges) or as entries in a custom object (Achievement__c with Name, Type, EarnedDate, and Contact__c lookup) depending on the achievement volume. Achievement rule logic is not migratable and is documented for rebuild.

Xtremepush geofence and iBeacon location metadata (coordinates, radius, UUID, beacon major/minor values, venue name) is exported as location records associated with user profiles. We migrate the location metadata as custom fields on the Contact record or as a custom Location__c object with geolocation fields and a lookup to Contact. Live location permission state (has the user opted in on the current device) cannot be migrated; it is reset when the app is reinstalled and must be re-collected per platform policy. This is documented as a post-migration step.

Xtremepush in-app and cross-channel behavioral events (event type, timestamp, associated profile) migrate as Salesforce CampaignMember activity records or as entries in a custom Experience__c or Event__c object depending on the volume and the customer's reporting needs. High-volume event exports (over 500,000 records) require Bulk API chunking. Event attribution to campaigns migrates to CampaignMember with the event type mapped to a CampaignMember Status value.

Xtremepush custom objects (Growth and Enterprise tiers) migrate to Salesforce custom objects with equivalent API names. We pre-create the destination schema in Salesforce including all custom fields, lookup relationships to Contact or Account, and validation rules before importing data. Custom object migration runs last in the dependency order because destination custom objects often have lookups that must resolve to already-migrated Contact or Account records.

Xtremepush user accounts (campaign managers, team admins) are mapped to Salesforce User records by email address. Any Xtremepush owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated Campaigns and Contacts is resolved at migration time using the email match.