Migrate from Alpine IQ to HubSpot

Loyalty tier progression cannot be modeled as a HubSpot lifecycle stage

Alpine IQ tracks loyalty tiers (Bronze, Silver, Gold, Platinum) as a progression based on points accrual and redemption events. HubSpot's lifecycle stage is a contact property designed for marketing pipeline stages (Subscriber, Lead, MQL, SQL, Customer, Evangelist) — it is not a loyalty tier model. If your team uses HubSpot lifecycle stage for marketing segmentation, the Alpine IQ loyalty tier will collide with it if mapped directly. We resolve this by mapping Alpine IQ tiers to a standalone custom picklist (Loyalty_Tier__c) and preserving tier-change timestamps in a separate audit field. This means loyalty program logic that drives tier upgrades must be rebuilt as HubSpot workflow rules — the event triggers and thresholds from Alpine IQ need to be exported and translated manually.

POS integration connections are cut off at migration and must be rebuilt

Alpine IQ's POS integrations (Dutchie, Flowhub, Jane, Headset, LeafLogix, and others) are point-to-point connections scoped to Alpine IQ's platform. These integrations do not have HubSpot equivalents — the loyalty sync, customer lookup by phone, and discount group assignment that happen in real time at the POS will not continue after migration without a rebuild. HubSpot's App Marketplace has a different set of POS and dispensary integrations that require separate contracts and setup. We scope the data migration separately from the integration rebuild. Before go-live, your team should identify which POS integration to reconnect and whether your POS vendor supports a HubSpot-native sync or requires a custom API build.

Dynamic audience rules must be translated to HubSpot Smart List filters manually

Alpine IQ dynamic audiences use event-based rules (order frequency, point balance thresholds, audience entry/exit, flow triggers) to maintain membership. HubSpot Smart Lists filter on contact properties, list membership, and engagement metrics — they do not support the same event-based trigger model. Static audiences migrate cleanly as HubSpot Static Lists with contacts pre-loaded. Dynamic audiences migrate as HubSpot Smart Lists where feasible (property-based filters translate directly), but event-driven rules like 'joined audience after placing an order in the last 30 days' require manual rebuild as HubSpot workflow enrollment triggers. We provide an audience-definition export from Alpine IQ as a reference document for your HubSpot admin.

Order history granularity is reduced — order-level detail beyond totals requires a custom object

Alpine IQ stores individual order records with line items, SKUs, discounts applied, and fulfillment status. HubSpot Deals carry an amount, stage, and close date but do not natively represent individual line items or product-level purchase history. We migrate order totals, total spent, order count, and last order date as contact-level custom properties. If your team needs per-order granularity (SKU history, item-level discount data, per-location order counts), that requires a HubSpot custom object (Enterprise-tier) or a product catalog integration. We scope the per-order custom object build as an add-on during the pre-migration audit if your team needs it.

HubSpot marketing contact flagging creates a billing distinction that Alpine IQ does not have

HubSpot bills Marketing Hub plans based on marketing contacts — contacts who have opted in to marketing emails. Alpine IQ does not have this distinction; all persona records are treated equally for platform billing. When migrating to HubSpot, contacts who were enrolled in Alpine IQ loyalty flows or SMS campaigns may need to be flagged as marketing contacts in HubSpot, which affects your HubSpot subscription tier. We do not automatically enroll all contacts as HubSpot marketing contacts — your team decides the enrollment policy post-migration. The opt-in status from Alpine IQ is preserved in a custom property (Email_Opt_In_Source__c) so your HubSpot admin can configure enrollment rules based on the original opt-in data.