Migrate from Xtremepush to Odoo CRM

Xtremepush user profiles map to Odoo CRM Contact records. The profile identifier becomes the external ID field (xxtremepush_id) on Contact for dedupe and reconciliation. Standard Contact fields (name, email, phone, address) map from Xtremepush profile attributes. Custom attributes from Xtremepush become Odoo custom fields (Char, Integer, Selection, or Text depending on data type) created in the destination schema before import. If the Xtremepush account uses company-mode profiles, we map to Contact plus a parent Company record created as an Odoo Contact with company_type=company.

Xtremepush predefined and custom attributes export as key-value pairs. We map each attribute to a typed Odoo ir.model.field record: numeric attributes become Float or Integer fields, date attributes become Date fields, boolean attributes become Boolean fields, and text attributes become Char or Text fields. Tags (multi-select attributes) map to Odoo tags on the Contact form if the destination Odoo instance has the contacts_mass_mailing module installed, or to a Char field storing comma-separated values for instances without that module.

Xtremepush consent records carry preference type (Marketing, Legitimate Interest), subscription status, last-updated timestamp, and source (manual, SDK, import). We map the Marketing subscription status to Contact.opt_out in Odoo. For high-compliance industries, we create custom Boolean fields per consent type (consent_marketing__c, consent_legitimate_interest__c) with a Date field storing the last-updated timestamp. Xtremepush consent records with import-source and no historical change trail are flagged in the handoff checklist; we recommend re-collecting consent for financial services, iGaming, or healthcare accounts.

Push device tokens are platform-specific to Xtremepush and cannot migrate to Odoo CRM. Odoo has no native push notification infrastructure. We export the device token inventory as a CSV for the customer's mobile development team to use when re-registering tokens against the new push provider (Firebase Cloud Messaging, APNS, or a third-party service like OneSignal). The re-registration workflow requires an updated app build and cannot be completed from the server side alone.

Xtremepush location objects (coordinates, radius, beacon UUIDs) have no Odoo CRM equivalent. Odoo does not have a native geofence or beacon data model. We export all location metadata as a structured CSV inventory (venue name, latitude, longitude, radius, UUID, major/minor for beacons) for the customer's admin to evaluate Odoo apps from the Odoo App Store (geolocation add-ons) or a custom development approach. Location permission state cannot migrate; users must re-opt into location tracking after any app reinstall.

Xtremepush campaigns (execution units with name, schedule, trigger conditions, channel, and content) do not have a direct Odoo CRM equivalent. We export campaign metadata as a written inventory document. The campaign name becomes a CRM Campaign record in Odoo. Active campaign schedules and trigger conditions cannot migrate because Xtremepush's trigger syntax is platform-specific. The customer's admin evaluates Odoo's Marketing Automation app or external engagement tools to replicate campaign schedules.

Xtremepush audience segments are defined by attribute, event, and tag rules. We export segment membership rules, sizes at migration time, and the segment names. Segment rule syntax is Xtremepush-specific and cannot be translated to Odoo's filter or domain syntax automatically. We create Odoo CRM Tags (using the contacts_mass_mailing module) for each Xtremepush segment and assign segment members by running the segment criteria against migrated profile data. Manual Odoo domain filters replicate the remaining segment logic.

Xtremepush behavioral events (event type, timestamp, associated user/device) migrate to Odoo CRM as Note records linked to the Contact for low-volume event histories, or as a custom crm.event model if the event volume exceeds 50,000 records. Event type names map from Xtremepush to the custom event's event_type field. Large-volume event exports require chunking; we process in batches of 5,000 records and use Odoo's XML-RPC at the 1 call/second rate limit with exponential backoff.

Loyalty points balances, tier assignments, and gamification achievements are stored as attributes on Xtremepush user profiles rather than as a standalone loyalty ledger. We export the current state snapshot as custom fields on the Contact record (loyalty_points__c, loyalty_tier__c, loyalty_badges__c). The gamification rule engine (triggers, reward thresholds, achievement conditions) is not exposed via export and cannot migrate. We provide a structured inventory of all gamification mechanics observed in the account during discovery. Odoo Loyalty app (separate subscription) is the recommended replacement.

Xtremepush SFTP and email-based automated exports run on hourly, daily, weekly, or monthly schedules. We document the export schedule, credential paths, schema of exported files, and any transformation logic applied by the export. These schedules are Xtremepush-specific and have no Odoo equivalent. We recommend the customer wire a new Odoo scheduled action (ir.cron) or external ETL tool (N8N, Airbyte, custom script) to replicate the export behavior if ongoing data flow from Odoo to a data warehouse is required.

Xtremepush owners (team members with campaign and profile access) map to Odoo CRM User records. We resolve owners by email match against the destination Odoo User table. Any Xtremepush owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owners in Xtremepush map to Odoo Users with active=False.

Encrypted push delivery and delivery receipts are a separately priced Xtremepush Enterprise add-on requiring SDK integration and encryption key management. We do not migrate encryption keys or delivery receipt configurations. This feature requires re-negotiation with the push provider and a fresh SDK integration in the destination application. We document the current encrypted push configuration as observed during discovery for the customer's technical team to evaluate against Odoo's third-party push options.