Migrate from Xtremepush to Pipedrive

Xtremepush user profiles map to Pipedrive Person (for customers, evangelists, and post-sale contacts) or Pipedrive Lead (for subscribers, marketing-qualified leads, and prospects without a sales relationship). We apply a split rule during scoping based on the customer's lifecycle data: profiles with a purchase event or post-sale attribute become People; profiles with only campaign engagement events become Leads. The original Xtremepush profile ID is preserved in a custom field xtremepush_profile_id__c for audit and cross-referencing. All Xtremepush attributes and tags migrate as Pipedrive custom fields on the target record.

Xtremepush key-value attributes and tag sets migrate as Pipedrive custom fields. Text attributes map to Pipedrive text fields; numeric attributes map to number fields; date attributes map to date fields; multi-value tags map to multi-select picklist fields where the picklist values are enumerated from the observed tag vocabulary. We create the custom fields in Pipedrive during the schema phase before record import begins. Any attribute key that conflicts with a reserved Pipedrive field name is prefixed with xp_ (e.g., xp_loyalty_tier__c).

Xtremepush loyalty state (points balance, current tier, lifetime points) is stored as profile attributes and migrates as custom fields on the Pipedrive Person record. The loyalty rule engine (triggers, reward thresholds, badge definitions) is not exposed via Xtremepush export and cannot migrate. We provide a structured inventory of all observed gamification mechanics during discovery, including point-earning rules, tier thresholds, and badge triggers, so the customer can rebuild the program in Pipedrive's workflow engine or a dedicated loyalty tool.

Xtremepush consent records (Marketing, Legitimate Interest, per-channel status, source) migrate as a custom field consent_status__c on Person, storing the aggregated opt-in state, and as an Activity Note recording the last-updated timestamp and source. Xtremepush's consent export does not include full audit trail (historical changes or per-campaign consent events). We flag which records have only an import-source consent record and recommend re-collecting consent for regulated industries (iGaming, financial services, healthcare-adjacent) before finalizing migration. Pipedrive's native HasOptedOutOfEmail flag is set based on the Marketing channel consent status.

Xtremepush campaign executions (push sends, email deliveries, SMS messages, event triggers) migrate as Pipedrive Activity records (calls, emails, meetings, tasks) linked to the Person record. Each Activity captures the campaign name, channel, timestamp, and outcome (delivered, opened, clicked) as custom fields. Campaign trigger conditions and execution metadata are stored as an Activity Note rather than as native automation objects. Campaign state (scheduled, draft, active, paused) cannot migrate because Pipedrive has no campaign execution object.

Xtremepush audience segments are defined by attribute, event, and tag rule sets. We export the segment membership rule syntax and segment sizes at migration time, then document each segment with its name, rule definition, and estimated record count. Pipedrive does not have an audience segmentation engine; segments must be rebuilt manually as saved filters or as Smart Lists if the customer licenses the appropriate Pipedrive plan. We deliver a segment inventory spreadsheet that maps each Xtremepush segment to one or more Pipedrive filter criteria.

Xtremepush in-app and cross-channel behavioral events (page views, purchases, feature interactions) migrate as Pipedrive Activity records with the event type name as the Activity subject and the original timestamp as ActivityDate. High-volume event exports require chunking; we batch by event type and date range to stay within Pipedrive's API write limits per plan tier. The event schema (event type names, property keys) is preserved in an Activity Note on the Person record for reference.

Xtremepush location data (geofence coordinates, radius, beacon UUIDs, venue names) migrates as a structured address in Pipedrive's address fields on the Person or Organization. Location permission state cannot migrate because it is a device-level runtime permission that resets on app reinstall. We document the location schema in the migration handoff so the customer's dev team can re-implement geofencing via Pipedrive's API if needed. Pipedrive does not have native geofence or iBeacon support.

Push tokens are tied to the Xtremepush SDK and have no equivalent in Pipedrive's data model. Pipedrive is a sales CRM without push notification capability, so APNS and Firebase/GCM tokens cannot be imported. We document the token export workflow (CSV from Xtremepush's developer export, handed to the app team) separately. Push re-registration after migration requires an app update with the customer's new push provider SDK and is outside the CRM migration scope.

Xtremepush SFTP and email-based automated exports (hourly, daily, weekly) are documented with their schedule, credential paths, and exported schema. If the customer intends to maintain Xtremepush for push and email delivery alongside Pipedrive as the CRM of record, we document the export schedule so that a data integration (via Zapier, Make, or a custom connector) can be configured to keep Pipedrive synchronized with Xtremepush profile updates post-migration.