Migrate from Xtremepush to Twenty CRM

Xtremepush user profiles map directly to Twenty People records. We extract all standard profile fields (name, email, phone, country) and map them to Twenty's name, email, and phone fields. Xtremepush custom attributes and tags migrate as custom fields on the Person object—boolean and single-select attributes become checkbox or select fields; multi-value tags become multi-select picklists or text fields depending on cardinality. The migration user must pre-create all custom fields in Twenty's Settings -> Data Model before import, as Twenty's CSV import creates records only, not fields.

Xtremepush stores company data as profile attributes rather than a distinct object. We extract company name, domain, industry, size, and address from user profile attributes and create Twenty Company records. Each Person record is then linked to its parent Company via Twenty's WorkGroupRelation or a Company link field on Person. We use the company domain as a dedupe key during import.

Xtremepush key-value attributes and tags export as columns in the profile CSV. We map each distinct attribute key to a Twenty Person custom field of the appropriate type (text, number, date, select). Tags with high cardinality become text fields; tags with fewer than 30 distinct values become select fields. We flag any attribute with more than 30 distinct values for manual review during scoping because multi-select picklists in Twenty have practical cardinality limits.

Xtremepush consent records (preference type, Marketing or Legitimate Interest, subscription status, last-updated timestamp, consent source) migrate as custom fields on the Person object: consent_status__c (select: subscribed/unsubscribed), consent_type__c (select: marketing/legitimate_interest), and consent_updated__c (date). We flag that the full consent audit trail (historical changes, campaign context per consent event) is not included in Xtremepush's automated export, and recommend re-collecting consent for high-compliance industries before finalizing the migration.

Xtremepush campaigns have no direct Twenty CRM equivalent because Twenty does not have a native campaign execution object. We create a Campaign__c custom object in Twenty with fields for campaign name, channel (push/SMS/email), status, schedule, and target segment description. We link Person records to campaigns via a CampaignMember__c junction object (Person lookup + Campaign lookup) so that campaign membership is preserved. The campaign rule engine and trigger conditions are documented separately for rebuild in Twenty's workflow builder.

Xtremepush audience segments are defined by attribute, event, and tag rules that produce a membership list at migration time. We create a Segment__c custom object in Twenty and export the segment name, rule description, and membership count. We do not migrate the Xtremepush segment rule syntax (which is Xtremepush-specific) into Twenty; instead we document the segment membership snapshot as Person records tagged with the segment name and deliver a written segment inventory for the customer to rebuild using Twenty's filters and custom field combinations.

Loyalty points balance, tier assignment, and gamification achievements are stored as attributes on Xtremepush user profiles and export as key-value pairs. We map these as custom fields on the Person object: loyalty_points__c (number), loyalty_tier__c (select), and loyalty_achievements__c (text or multi-select). The gamification rule engine (triggers, rewards, thresholds) is not exposed via export and must be rebuilt manually in Twenty's workflow builder. We provide a structured inventory of all gamification mechanics observed during discovery.

Push tokens are tied to Xtremepush user profiles but Twenty CRM does not store push tokens as a native feature. We export the device token data (token string, platform, registration timestamp) as a CSV reference document. This document is handed off for the customer's mobile development team to re-register devices using the new push provider's SDK. We schedule the migration cutover to align with the app release so tokens remain valid during the transition window. We do not migrate APNS or Firebase/GCM tokens into Twenty itself.

Xtremepush behavioral events (event type, timestamp, associated user/device) export as event log records. High-volume event exports require chunking by date range. We map each distinct event type to a custom field on the Person object (event_count_<type>__c) capturing the total count and most recent timestamp, rather than creating individual Task records for every event. Significant milestone events (first_purchase, subscription_start, churn) migrate as Task records on the Person's timeline for CRM use. The event rule engine is not migratable; we document the event taxonomy for rebuild in Twenty's workflow builder.

Xtremepush geofence and iBeacon data (coordinates, radius, beacon UUIDs, venue associations) export as location metadata. Twenty CRM does not have a native location or geofencing feature. We export the location data as a structured reference CSV and document the location taxonomy (venue names, associated segments, trigger conditions) for the customer's admin to evaluate against location-enabled alternatives or custom integrations post-migration.

Xtremepush custom objects map to Twenty custom objects of equivalent name and schema. We pre-create the destination custom object in Twenty's metadata API (Object, Field, DataSource entries), configure lookup relationships to standard objects (Person, Company), and validate field types before data import. Xtremepush custom object records migrate to Twenty custom object records using the same bulk import pipeline as standard objects. Custom object naming convention in Twenty uses the metadata API object name without a suffix requirement.

Xtremepush owners (campaign managers, team leads) map to Twenty WorkspaceMember records. We resolve owners by email match. Any Xtremepush Owner without a matching Twenty WorkspaceMember is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Twenty requires all WorkspaceMembers to be invited and active before Owner references on Person records can be resolved.