Migrate your Alpine IQ data

Personas are the primary contact object in Alpine IQ, containing name, phone, email, birthdate, gender, address, and med ID. We migrate all standard PII fields via the /api/v2/loyalty POST endpoint and preserve custom override attributes set via the /api/v2/loyaltyContact/override endpoint. Blocklisted contacts are excluded from GET responses and we flag any suppressed records during export scoping.

Order objects include order ID, status, substatus, timestamps, customer PII, item data (product name, category, SKU, brand, price, discount), payment details, and attribution parameters. We extract the full order history including cancelled and refunded orders to preserve purchase behavior for segmentation rebuilds.

Audiences are segmented contact groups used for campaign targeting and automation triggers. Alpine IQ stores audience membership by contact ID with a points multiplier per audience. We map audience membership as a tag or custom property on the contact record since most destination CRMs do not have a native audience-equivalent object.

Loyalty point balances and tier status are stored on the contact record in Alpine IQ. Points multipliers are set per audience. We preserve point balances as a numeric custom property and tier names as a text field, but native tier logic (progression rules, expiration policies) requires manual reconfiguration in the destination system.

Alpine IQ discount groups map to specific POS discount rules and customer eligibility flags. The Dutchie integration guide shows discount groups as a mapped field in the customer profile. We export discount group assignments as a text property on the contact and note that the receiving system must have corresponding discount rules configured.

Email and SMS opt-in status is tracked separately via /api/v2/optin endpoints and can be set per email address or phone number. We migrate opt-in flags as boolean properties on the contact record, preserving the last-modified timestamp to honor consent recency.

Multi-location Alpine IQ accounts require each integration or data source to be mapped to a specific store location. The store name in Alpine IQ must exactly match the location name in the connected POS. We export store mapping configurations separately and flag mismatches that would prevent loyalty attribution from resolving correctly.

The attr parameter on URLs and order objects allows Alpine IQ to track campaign attribution and UTM-like sources. Attribution values are stored in the Order object and can be used to rebuild campaign performance reports in the destination system.

Flows are automation triggers based on events like order_created, order_completed, order_cancelled, cart_abandoned, and behavioral events. Event schemas vary by integration (POS vs ecommerce). We export the event log and map trigger conditions to equivalent automation rules in the destination platform.

Alpine IQ supports custom fields on Persona records that can be set via override endpoints. We export all custom properties alongside standard fields and map them to custom fields in the destination CRM. Field type differences (text vs number vs date) require type-safe transformation during import.

Mobile wallet push notification IDs are stored on contacts via /api/v1.1/contact/addPushID. These IDs are platform-specific (device tokens) and cannot be transferred between systems. We export the push ID as a reference field for audit purposes but note it becomes invalid in a new app environment.

Every contact has a source ID from the integration that created it (POS, ecommerce, etc.). The /api/v1/piis/:uid/bySrcID endpoint allows lookup by source ID. We preserve all source IDs to maintain the audit trail of where each contact originated.