Migrate from Alpine IQ to HighLevel

Alpine IQ Personas map directly to GoHighLevel Contacts. We extract all standard PII fields (first name, last name, phone, email, birthdate, gender, address, med ID) via the /api/v2/loyalty POST endpoint and POST them to GoHighLevel's Contacts API. Phone is used as the dedupe key. SMS and email opt-in flags from /api/v2/optin migrate as boolean properties on the GoHighLevel contact record. Integration source IDs are preserved in a custom field for audit.

Order records from Alpine IQ's /api/v2/orders endpoint (order ID, status, substatus, timestamps, customer PII, item data, pricing, attribution) map to a GoHighLevel Custom Object we provision during schema design. The Custom Object API v2 supports relationships, enabling Order records to link to the Contact that was migrated from the corresponding Persona. Attribution parameters (attr) preserve as a custom field for campaign reporting.

Alpine IQ Audiences are segmented contact groups with membership tied to a points multiplier per audience. We export audience membership by contact ID and map each audience to a GoHighLevel Tag. The contact's tag list is set via the GoHighLevel Contacts API. Points multipliers do not have a native GoHighLevel equivalent and are stored as a custom field aiq_audience_multipliers__c in JSON format.

Loyalty point balances and tier names stored on Alpine IQ Personas migrate to GoHighLevel custom fields: aiq_loyalty_points__c (integer) and aiq_loyalty_tier__c (text). The loyalty program rules (point expiration, tier thresholds, reward eligibility) are configuration-level in Alpine IQ and do not export. We document the current program structure during scoping and deliver a written specification for the customer's GoHighLevel admin to configure as a custom loyalty workflow or third-party integration.

Email and SMS opt-in status tracked via /api/v2/optin endpoints in Alpine IQ migrates as boolean properties on GoHighLevel Contacts: email_opt_in__c and sms_opt_in__c. We respect the opt-out flags and do not mark suppressed contacts as opted-in. The explicit opt-out records are preserved in a custom field aiq_blocklist_flag__c for audit purposes.

Alpine IQ multi-location accounts require each POS integration to be mapped to a specific store name. GoHighLevel represents locations as Locations (within the main account) or Sub-Accounts (separate workspaces). We export the store mapping configuration and deliver a location setup guide mapping each Alpine IQ store name to a GoHighLevel Location or Sub-Account. The customer configures POS webhooks or API credentials in GoHighLevel post-migration.

Alpine IQ discount groups store POS discount eligibility flags per customer. These migrate as custom fields (discount_group__c) or tags on the GoHighLevel Contact. The actual POS discount rules require manual configuration in the destination POS and GoHighLevel workflow setup, as these are not portable data values.

The attr parameter values stored on Alpine IQ Order records (tracking campaign, source, and medium) migrate as custom fields on the Order custom object: aiq_attr_campaign__c, aiq_attr_source__c, aiq_attr_medium__c. These enable the customer's GoHighLevel admin to build attribution reports using the migrated order history.

Alpine IQ supports custom fields on Persona records via override endpoints. We export all custom properties and provision matching custom fields in GoHighLevel before migration. Field type mapping: text fields to GoHighLevel text fields, numeric fields to number fields, date fields to date fields. Picklist-style custom fields map to GoHighLevel dropdown fields if the value set is enumerated, or text fields if open-ended.