Migrate from Alpine IQ to Zoho CRM

Personas are the primary contact object in Alpine IQ containing name, phone, email, birthdate, gender, med ID, and address. We migrate all standard PII fields via Alpine IQ's /api/v2/loyalty POST endpoint. In Zoho CRM, these map to standard Contact fields (First_Name, Last_Name, Email, Phone, Mobile). Custom fields hold loyalty-specific properties. Integration source IDs are preserved in a custom field to maintain the POS attribution trail.

Alpine IQ Order objects (order ID, status, timestamps, item data, payment, attribution) map to Zoho CRM Deals. The order total maps to Deal Amount. The associated Persona contact links via a Zoho CRM lookup relationship. Order status maps to a Zoho CRM picklist we configure to match the source status values. Attribution parameters (attr) migrate as a custom text field on the Deal.

Alpine IQ Audiences are segmented contact groups used for campaign targeting. Each contact can belong to multiple audiences with a points multiplier. We map audience membership to Zoho CRM Lists (one List per Alpine IQ Audience) and store the points multiplier as a custom field on the Contact. Multi-audience contacts generate multiple List membership records in Zoho.

Alpine IQ stores point balances and tier names on the Persona record. We export these as custom fields in Zoho CRM: a numeric custom field for loyalty_points_balance and a text field for loyalty_tier_name. The program rules (point expiration logic, tier thresholds, reward eligibility) are configuration-level settings in Alpine IQ and do not export; these require manual rebuild in Zoho CRM Blueprint or workflow rules.

Alpine IQ discount groups map to 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 membership as a multi-select picklist or comma-separated text custom field on the Zoho CRM Contact, depending on the customer's discount group count.

Email and SMS opt-in status tracked separately in Alpine IQ via /api/v2/optin endpoints migrates as boolean custom fields on the Zoho CRM Contact. Email opt-in maps to a Zoho CRM checkbox field (Email_Opt_In__c) and SMS opt-in maps to SMS_Opt_In__c. If the customer uses both, we migrate both flags separately.

Multi-location Alpine IQ accounts map each integration or data source to a specific store location by exact name matching. We extract the full store mapping configuration from the Alpine IQ account and validate that store names align with the Location records created in Zoho CRM. Misaligned store names must be corrected before contact migration begins to preserve loyalty attribution.

Alpine IQ attr parameters on orders and URLs track campaign attribution. We export attr values from the Order object and populate a custom text field on the Zoho CRM Deal. For URL-level attribution, we document the attr parameter values and recommend a UTM-compatible custom field structure in Zoho CRM for the customer's analytics team to implement post-migration.

Alpine IQ Flows trigger on events like order_created, order_completed, cart_abandoned. We export the event schemas and document the automation logic as a written inventory. Zoho CRM Blueprint and Workflow Rules can replicate the trigger logic, but the Flow automation code does not migrate. The customer's admin rebuilds the automations using the exported event documentation.

Alpine IQ supports custom fields on Persona records set via override endpoints. We export all custom properties alongside standard fields and create matching custom fields in Zoho CRM before migration. Field types are mapped by inspecting the Alpine IQ field definition (text, number, date, boolean, picklist) to the nearest Zoho CRM field type.

Every Alpine IQ contact has a source ID from the POS or ecommerce integration that created it. We preserve all source IDs in a custom field on the Zoho CRM Contact (integration_source_id__c) for audit and POS reconciliation. The /api/v1/piis/:uid/bySrcID endpoint in Alpine IQ allows lookup by source ID, which we document for the customer's integration team.