Migrate from Xtremepush to Freshsales

Xtremepush user profiles are the primary migration unit and map directly to Freshsales Contact records. The Xtremepush user identifier becomes an external ID field (xtremepush_id__c) on Contact for deduplication. Profile attributes (custom key-value pairs) migrate as Freshsales custom fields created during schema design. Tags migrate as a Freshsales multi-select picklist or as Contact tags if the account is on Freshsales Suite. The email address, phone number, and name fields map to their Freshsales equivalents.

All Xtremepush attributes and tag keys are inventoried during discovery and mapped to Freshsales custom fields of the appropriate type (text, number, date, picklist). Tag values with fewer than 200 distinct values map to picklist fields; high-cardinality attributes map to text. We create the fields in Freshsales during schema design before any data loads. Attribute values that reference other Xtremepush records (e.g., a linked location object) are resolved to human-readable strings or IDs at migration time.

Xtremepush user lifecycle stage (subscriber, lead, engaged, loyal, churned) maps to Freshsales Contact Lifecycle Status using a value mapping defined during scoping. We preserve the original Xtremepush lifecycle value in a custom field xtremepush_lifecycle__c on Contact so the customer's admin can reference the source data post-migration.

Xtremepush audience segments are defined by attribute and event rules. Since Freshsales does not have a native segment object, we export segment membership (the list of user IDs in each segment at migration time) and map those contacts to Freshsales Tags using the segment name. The rule-building logic is documented for the customer admin to recreate as Freshsales Contact Filters post-migration if dynamic segment membership is required.

Points balances, tier assignments, and gamification achievements are stored as attributes on Xtremepush user profiles. We export them as custom number and picklist fields on the Freshsales Contact: points_balance__c, loyalty_tier__c, and achievement_count__c. The gamification rule engine (thresholds, triggers, reward logic) is not exposed via export and does not migrate; we deliver a structured inventory of all gamification mechanics observed during discovery for the customer admin to rebuild in Freshsales Workflows if needed.

Xtremepush consent records carry the preference type (Marketing, Legitimate Interest), status (subscribed/unsubscribed), and last-updated timestamp. We map the email opt-out status to Freshsales Contact HasOptedOutOfEmail and SMS opt-out to HasOptedOutOfSMS. The consent type and source (manual, SDK, import) are preserved in custom fields consent_type__c and consent_source__c for compliance audit purposes. The Xtremepush export does not include the full consent change history, which we flag as a limitation for high-compliance industries.

Xtremepush campaign metadata (name, channel, schedule, trigger conditions) does not have a direct Freshsales equivalent because Freshsales is not a campaign execution platform. We export campaign names and assign each campaign an internal ID. For each contact, we create a Freshsales Task with a custom field campaign_name__c and the interaction timestamp (delivered, opened, clicked) recorded as task properties. This preserves a campaign attribution record in Freshsales without requiring the customer to run campaigns from Freshsales. The campaign builder and scheduling logic is documented separately for rebuild in Freshsales Suite or a dedicated marketing platform.

Xtremepush event records (event type, timestamp, associated user and device) map to Freshsales Task records with a custom event_type__c field and the original timestamp preserved as ActivityDate. High-volume event exports (thousands per user) are chunked by user and loaded in batches to stay within Freshsales API rate limits per plan tier. We map the device identifier to a custom field device_id__c on the Task for reference.

Xtremepush has no native deal object, but engagement metrics can be used to construct Freshsales Deals during migration. We identify contacts with high engagement scores (session frequency, campaign open rate, loyalty tier) and create Freshsales Deals for accounts where commercial intent can be inferred. Deal value is derived from a proxy metric (loyalty tier mapped to deal size bracket) agreed upon during scoping. Stage is set to a default value (e.g., 'New') for migration, with the customer's sales admin assigning the correct stage post-import. This step is optional and requires explicit scope inclusion during discovery.