Migrate from Alpine IQ to Freshsales

Alpine IQ Personas map directly to Freshsales Contacts. Standard PII fields (firstname, lastname, email, phone, birthday, birthdayday, birthdaymonth, birthdayyear, gender) migrate to Freshsales Contact fields. Medical ID and compliance fields migrate to custom Contact fields (med_id__c, compliance_state__c, customer_type__c for veteran/police/local status) that the customer configures post-migration. Birthdate parsing from Alpine IQ's three-field format (birthday, birthdayday, birthdaymonth) combines into Freshsales Date_of_Birth.

Alpine IQ stores SMS and email opt-in status separately via /api/v2/optin endpoints. We export both email opt-in and SMS opt-in as boolean contact properties: email_opt_in__c and sms_opt_in__c. For email, Freshsales uses the standard HasOptedOutOfEmail field (inverted logic: true means opted out). For SMS, Freshsales does not have a native SMS opt-out field, so we use a custom field sms_opt_in__c. Blocklisted contacts are silently excluded from standard GET responses; we query alternative endpoints where available and cross-reference opt-in flags on returned records to build a complete suppression list.

Alpine IQ Order objects carry customer PII, item-level data (product name, category, SKU, brand, price, discount), payment details, attribution parameters, and timestamps. We split each Order into a Freshsales Deal (Opportunity) at the header level (order ID, status, timestamps, totals, tax, tip) and individual Deal Line Items for each product line. The attr attribution parameter on each order migrates to a custom Opportunity field attribution_source__c for campaign ROI reporting.

Order line items (product name, SKU, brand, category, price, discount) map to Freshsales Deal Product records. We create Product2 records in Freshsales for each distinct SKU, set Standard Price Book entries, and link line items to the parent Opportunity during migration. Discount values migrate as custom line-item fields if the destination Freshsales edition supports them.

Alpine IQ stores point balances and tier status on the Persona record. We export point_balance as a numeric custom field loyalty_points__c and tier_name as a text field loyalty_tier__c. The rules governing point expiration, tier progression thresholds, and reward eligibility are configuration-level settings in Alpine IQ and are NOT exported as data. We deliver a written loyalty-program inventory document listing all point tiers, earning rates, expiration rules, and reward structures so the customer's Freshsales admin can rebuild equivalent logic using Freshsales Workflows or a third-party loyalty app.

Alpine IQ Audiences are segmented contact groups used for campaign targeting. Each contact's audience membership (with points multiplier) is stored by contact ID. We map each Alpine IQ Audience to a Freshsales Static List and populate it with the matching Contacts. Dynamic List behavior (auto-updating membership based on criteria) cannot be replicated without Freshsales dynamic filter logic, which requires post-migration configuration. Audience points multipliers migrate as a custom field audience_multiplier__c on the Contact.

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 as a text field discount_group__c on the Contact record. Discount rule logic (percentage off, buy-one-get-one, member-only pricing) does not migrate as configuration; the customer reviews and rebuilds discount eligibility in Freshsales.

Multi-location Alpine IQ accounts require each integration or data source to be mapped to a specific store location. Store names in Alpine IQ must exactly match location names in the connected POS (Dutchie, Cova, Flowhub, etc.). We extract the full store mapping configuration from Alpine IQ and create Account records in Freshsales representing each location. The contact's preferred store or favorite-store attribution migrates as a lookup field store_location__c pointing to the corresponding Account. Store name mismatches between Alpine IQ and POS are flagged during scoping and must be resolved before migration begins.

Alpine IQ supports custom fields on Persona records set via override endpoints. We export all custom properties alongside standard fields. Custom property names in Alpine IQ map to Freshsales custom Contact fields using the same label (with spaces removed and underscores substituted). Field types are mapped: text to Text, number to Number, date to Date, boolean to Checkbox. We pre-create all custom fields in Freshsales before migration begins.

The attr parameter on Alpine IQ orders stores campaign attribution (UTM-like sources, campaign IDs). Attribution values are stored in the Order object and migrate to Freshsales Opportunity custom fields: attribution_source__c, attribution_campaign__c, and attribution_medium__c. These fields enable campaign ROI reporting at the opportunity level in Freshsales reporting.