Migrate from Alpine IQ to Salesforce Sales Cloud

Alpine IQ Personas map directly to Salesforce Contact records. We export all standard PII fields (name, phone, email, birthdate, address, med ID) via Alpine IQ's /api/v2/loyalty POST endpoint and insert into Salesforce Contact. Each Contact is resolved to a parent Account representing the dispensary location. The source integration ID is preserved in a custom field aiq_integration_source_id__c to maintain cross-reference to the originating POS record.

Multi-location Alpine IQ accounts map each retail location to a Salesforce Account record. Single-location accounts map to one Account. The Account name is set to the store name as it appears in the POS system. We validate store name alignment between Alpine IQ and the connected POS (Dutchie, Flowhub, Cova) before migration to prevent loyalty attribution failures. Store name mismatches are flagged in the discovery report for customer resolution before data moves.

Alpine IQ Order objects map to Salesforce Opportunity records. Order ID, status, substatus, and all timestamps migrate as Opportunity fields and custom date fields. Item data (product name, category, SKU, brand, price, discount) migrates as OpportunityLineItem records with the Standard Pricebook entry resolved at migration time. Attribution parameters (attr) storing campaign source and medium migrate to a custom field aiq_attr_parameters__c on the Opportunity, preserving campaign ROI reporting at the order level.

Alpine IQ stores point balances as a numeric property on the Persona record. We export point balances and map them to a custom numeric field aiq_loyalty_points__c on the Salesforce Contact. Tier names map to a custom picklist field aiq_loyalty_tier__c. Point expiration logic, tier progression thresholds, and reward eligibility rules live in Alpine IQ's configuration layer and are not accessible via API. We preserve all balances accurately but the customer must manually recreate loyalty program rules in Salesforce's Loyalty Management module or as custom Flow logic post-migration.

Alpine IQ Audiences are segmented contact groups used for campaign targeting. We map audience membership to Salesforce Campaign records with the audience name as Campaign Name, and create CampaignMember records linking each Contact to the relevant Campaign. If the customer has many audiences (over 50), we discuss prioritization during scoping and migrate the top-frequency and top-spend segments first, with a full audience map delivered as a written inventory.

Alpine IQ tracks email and SMS opt-in status separately via /api/v2/optin endpoints. Email opt-in migrates to Salesforce's standard HasOptedOutOfEmail field. SMS opt-in migrates to a custom field aiq_sms_optin__c. Compliance flags for cannabis marketing restrictions migrate to a custom picklist field aiq_compliance_status__c. Accurate opt-in migration is critical for cannabis retailers operating under state-specific SMS marketing rules.

Alpine IQ discount groups map to specific POS discount rules and customer eligibility flags. The discount group name and eligibility flag migrate as custom fields aiq_discount_group__c and aiq_discount_eligible__c on Contact. However, the POS-level discount rules themselves (percentage off, loyalty multiplier, product eligibility) live in the POS system, not in Alpine IQ or Salesforce. We export the discount group configuration as a written inventory for the customer's POS admin to reapply at the POS layer.

Alpine IQ Flows are automation triggers based on behavioral events like order_created, order_completed, and cart_abandoned. These events do not map to Salesforce Flow triggers because Salesforce Flow's record-triggered model operates on CRM object events rather than POS ecommerce events. We export Flow event history as Activity Task records for audit completeness, and deliver a written inventory of every active Flow with its trigger conditions, actions, and a recommended Salesforce Flow equivalent for the customer admin to rebuild.

Alpine IQ supports custom fields on Persona records that can be set via override endpoints. We export all custom properties alongside standard fields, map them to Salesforce custom fields on Contact using a naming convention that preserves the Alpine IQ field name where possible (aiq_custom_{fieldname}__c). Custom field data types are mapped: text to Text, number to Number, date to Date, checkbox to Checkbox.

Mobile wallet push notification IDs are stored on Alpine IQ contacts via /api/v1.1/contact/addPushID. These IDs are device tokens specific to Alpine IQ's mobile integration and cannot be transferred between systems. We export the push notification ID list as a reference document for the customer's admin to re-enroll mobile users post-migration through the new Salesforce Mobile app or a custom push notification integration.

Every Alpine IQ contact carries 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 in a custom field aiq_integration_source_id__c on Contact to maintain cross-reference to the originating POS customer record. This enables reconciliation during the validation step and supports data quality checks if the customer runs dual-system periods.

The attr parameter on Alpine IQ order objects tracks campaign attribution and UTM-like sources. Attribution values are stored in the Order object and preserved in a custom field aiq_attr_parameters__c on the Opportunity during migration. The customer uses this field to rebuild campaign ROI reporting in Salesforce Reports or a connected BI tool post-migration. We do not parse the attr string into separate UTM fields unless requested during scoping.