Migrate from Alpine IQ to Odoo CRM

Alpine IQ Personas map directly to Odoo CRM Contacts. We extract every standard PII field (name, phone, email, birthdate, gender, address) via the /api/v2/loyalty POST endpoint and POST each contact to Odoo's /res.partner endpoint. The Alpine IQ med_id (medical cannabis patient ID) migrates to a custom contact field med_id that must be created in Odoo before migration begins. We also map Alpine IQ source integration IDs (tracking which POS created the contact) to a custom field legacy_source_id for audit continuity.

Alpine IQ Orders carry the richest migration signal: order ID, status, timestamps, customer PII, item data (product name, category, SKU, brand, price, discount), payment details, and attribution parameters. We map order data to an Odoo custom sale_order record linked to the Contact via partner_id. The Alpine IQ attr parameter (campaign attribution) migrates as a custom field on the order record for campaign ROI reporting. POS integration source ID on the order migrates to a custom field for multi-location reconciliation.

Email and SMS opt-in status from Alpine IQ's /api/v2/optin endpoints migrates as boolean fields on the Odoo Contact. We set opt_in_email and opt_in_sms custom fields and set Odoo's standard blocking fields (block_email, block_sms) if the contact has suppressed status. GDPR consent timestamps migrate to a custom field consent_date for compliance audit.

Loyalty point balances and tier names are stored on the Alpine IQ Persona record. We extract both as numeric and text custom fields (loyalty_points__c, loyalty_tier__c) on the Odoo Contact. Point expiration rules, tier progression thresholds, and reward eligibility are configuration-level settings in Alpine IQ that do not export; we flag these as a rebuild requirement and recommend the customer request a loyalty program export snapshot before migration to document reward structures.

Alpine IQ discount groups define customer eligibility for POS discount rules. We export discount group membership as a multi-select text custom field on the Odoo Contact (discount_group__c). The Odoo Pricelist module can replicate discount eligibility logic, but the customer's admin must configure the discount rules post-migration based on the exported snapshot.

Alpine IQ Audiences are segmented contact groups used for campaign targeting. Audience membership (contact ID plus points multiplier per audience) migrates as Odoo Contact Tags. Multiplier values migrate to a custom field audience_multiplier__c per tag. Dynamic behavioral segmentation rules in Alpine IQ do not transfer; Odoo Tags are static lists that require manual rebuild by the customer's marketing team.

Multi-location Alpine IQ accounts map each integration or data source to a specific store location, with exact name matching required between Alpine IQ and the connected POS. We extract the full store mapping configuration and store it as a custom field favorite_store__c on each Contact. The customer's admin must validate store name alignment in Odoo POS before loyalty redemption functions. Mismatched store names between Alpine IQ and Odoo POS will break attribution and customer lookup.

The attr URL parameter and order-level attribution tracking in Alpine IQ store campaign attribution values in the Order object. We migrate these as custom fields on the Odoo sale_order record (campaign_source__c, campaign_medium__c, campaign_name__c) so the customer's admin can rebuild campaign ROI reporting in Odoo without referencing Alpine IQ.

Alpine IQ supports custom fields on Persona records that can be set via override endpoints. We export all custom properties alongside standard fields and create matching custom fields on the Odoo Contact object before migration. Field type mapping follows Odoo's allowed types: text fields for strings, numeric fields for integers and floats, date fields for dates. Boolean custom properties map to Odoo boolean fields.

Every Alpine IQ contact carries a source ID from the POS or integration that created it. The /api/v1/piis/:uid/bySrcID endpoint allows lookup by source ID. We preserve all source IDs as a custom field legacy_source_id on the Odoo Contact for cross-reference and audit purposes. This field cannot be used as a dedupe key in Odoo but serves as a backstop for reconciliation.

Alpine IQ Flows are automation triggers based on events like order_created, order_completed, cart_abandoned, and behavioral signals. We export the event history as Odoo Note records linked to the Contact for audit completeness. Odoo has no native Flow automation equivalent; the customer's admin must evaluate Odoo Server Actions or a third-party automation app (such as Automate2) to rebuild behavioral triggers.

Mobile wallet push notification IDs are device-specific platform tokens stored via Alpine IQ's /api/v1.1/contact/addPushID. These tokens cannot transfer between systems and are invalid once the customer moves to a new CRM. We export push ID records as a reference file for the customer's admin to re-enable push notifications post-migration in Odoo's mobile app context.