Migrate from Xtremepush to HighLevel

Xtremepush user profiles map to GoHighLevel Contacts. The profile identifier (email, phone, or anonymous ID) becomes the Contact lookup key. We use GoHighLevel's Contact import endpoint with the profile's primary identifier as the dedupe match field. Custom attributes from Xtremepush (preference types, engagement scores, loyalty standing) map to GoHighLevel Contact Custom Fields, created with matching field types before import. The Xtremepush profile UUID is preserved in a reference field on the GoHighLevel Contact for audit traceability.

Xtremepush attributes (key-value pairs with typed values: string, number, date, boolean) map to GoHighLevel Contact Custom Fields with equivalent input types. Multi-value tags map to GoHighLevel Tags (applied at the contact level) or to a multi-select picklist Custom Field depending on the customer's GoHighLevel setup preference selected during scoping. We export the full attribute schema during discovery and match each key to an existing or newly created Custom Field before the Contact import begins.

Xtremepush consent records with type (Marketing, Legitimate Interest), status (subscribed/unsubscribed), and last-updated timestamp map to GoHighLevel Contact Custom Fields using Boolean flags (e.g., sms_consent__c, email_marketing_consent__c) and a date field for consent_last_updated. We carry the consent source (manual, SDK, import) in a text field for compliance audit. The Xtremepush consent export does not include historical change audit trails; we flag records with only an import-source and recommend the customer review high-compliance contact segments before cutover.

Xtremepush audience segments are defined by attribute, event, and tag rule combinations. We export the segment membership rules (rule logic, operator, value) and the contact count at migration time. GoHighLevel does not have an equivalent automated segment object; segments map to GoHighLevel Smart Lists (Contact filter views) or to pipeline stage and tag-based filters that the customer's admin rebuilds. We deliver a segment inventory document listing every Xtremepush segment with its rule structure and equivalent GoHighLevel Smart List filter configuration.

Xtremepush campaign metadata (name, trigger conditions, channel, schedule) exports as a campaign inventory. GoHighLevel's Workflow builder executes automations with trigger, condition, and action steps; the campaign concept does not have a direct equivalent migration target. We deliver a written campaign inventory with each Xtremepush campaign's trigger, conditions, channel, and recommended GoHighLevel Workflow steps so the customer's admin can rebuild. No campaign logic migrates as executable code.

Push device tokens (APNS for iOS, Firebase Cloud Messaging for Android) are provider-specific and tied to Xtremepush's SDK installation. They cannot be imported into GoHighLevel because GoHighLevel does not have a native push notification delivery engine. We export the token list as a CSV for the customer's development team to use if they integrate a push provider (OneSignal, Airship, Firebase Cloud Messaging) into the GoHighLevel ecosystem or rebuild push delivery through a third-party app. Post-migration, users must re-opt into push notifications through the updated app build.

Xtremepush in-app and cross-channel behavioral events (event type, timestamp, associated user identifier) export as a behavioral event log. GoHighLevel does not have an equivalent event stream object. We map event history as Notes on the Contact record (one Note per event category or a consolidated behavioral summary note) for historical reference. Event volume exceeding 50,000 records per contact is chunked and summarized rather than individually listed. Event-based trigger logic in campaigns does not migrate and is documented in the campaign inventory for rebuild as GoHighLevel Workflow triggers.

Xtremepush loyalty mechanics (points balance, current tier, earned badges) are stored as attributes on user profiles. We export these as snapshot values and map them to GoHighLevel Contact Custom Fields: loyalty_points_balance__c (number), loyalty_tier__c (text), and loyalty_badges__c (multi-select picklist). The gamification rule engine (point-earning triggers, reward thresholds, achievement definitions) is not exposed via export and must be rebuilt manually in GoHighLevel using Workflows or a loyalty app from the GoHighLevel Marketplace. We provide a structured inventory of all gamification mechanics observed during discovery.

Xtremepush geofence and iBeacon location data (coordinates, radius, beacon UUIDs) exports as location metadata records. GoHighLevel does not have a native geofencing or beacon object. Location metadata is documented in the migration handoff as coordinate and zone records that the customer's development team can use if they integrate location features through a third-party app or custom development. The live location permission state (opted-in vs opted-out) is not preserved and requires users to re-opt through the app post-migration.