Migrate from Xtremepush to monday CRM

Xtremepush user profiles map to Monday.com CRM People records. The profile identifier becomes the Person's ID, email address maps to the Email column, first name and last name map to Name components, phone maps to Phone, and timezone maps to a custom text column. We flag any profiles without email addresses as requiring manual completion in Monday.com CRM before import because People records require an email as the unique identifier.

Xtremepush key-value attributes map to Monday.com CRM custom columns on the People board. String attributes become Text columns; numeric attributes become Number columns; date attributes become Date columns; boolean attributes become Checkbox columns. We define the column schema during scoping and deploy it to the destination board before import. Attributes with multi-value arrays are serialized as comma-separated text or placed in a dedicated Tags column depending on the attribute's cardinality.

Xtremepush tag sets migrate to the Monday.com CRM Tags column on People. Tags are a native column type in Monday.com, so no custom column definition is required. We export tags as a delimited list and import them in bulk via Monday.com's CSV import or API batch endpoint.

Xtremepush consent preference records (Marketing, Legitimate Interest types with subscribed/unsubscribed status) map to Monday.com CRM's Email column permission toggle. We set the permission value based on the consent status at migration time. Records with only an import-source consent origin are flagged in the migration report as potentially requiring re-collection for high-compliance industries such as iGaming or financial services.

Xtremepush campaign records (name, schedule, channel, trigger conditions) map to Monday.com CRM board items on a dedicated Campaigns board. Campaign metadata is stored in item name, status column (channel type), and description column (trigger conditions and schedule). We do not migrate campaign content bodies or creative assets; these are documented in the campaign inventory so the customer admin can re-author in Monday.com or an external content tool.

Xtremepush audience segments are defined by attribute, event, and tag rules that produce a membership list. We export the segment name, rule logic, and member count. In Monday.com CRM, we create a Group per segment or document the filter criteria as a named Filter View so the customer can recreate the segment membership logic in their own board structure. Segment rule-building syntax does not transfer because it is Xtremepush-specific.

APNS and Firebase GCM device tokens stored against Xtremepush user profiles have no equivalent in Monday.com CRM, which does not support push notification infrastructure. Device token data cannot be migrated. Teams relying on mobile push campaigns must implement a separate push notification solution post-migration and re-register device tokens as part of the app update workflow. We document the token count and associated profiles in the migration handoff checklist.

Xtremepush event types, timestamps, and associated user/device identifiers have no Monday.com CRM equivalent. Monday.com CRM is a record management and task tracking platform, not an event tracking system. Event volume data is documented in the migration inventory so the customer can assess whether a separate analytics or event pipeline tool is needed to replace Xtremepush's behavioral data collection.

Xtremepush loyalty points balances, tier assignments, and gamification achievements are stored as attributes on user profiles. We export these as attribute values and place them in Monday.com CRM custom Number columns (for points balance), Status columns (for tier), and Text columns (for achievements). The gamification rule engine, reward triggers, and threshold logic are not exposed via export and must be rebuilt manually in Monday.com's automation builder or as a separate loyalty application.