Migrate from Alpine IQ to Microsoft Dynamics 365 Sales

Alpine IQ Personas map to Dynamics 365 Contact for qualified customers and Lead for prospects that have not been assigned to a sales rep. We use the Persona is_customer flag and order history to determine routing: contacts with at least one completed order become Dynamics Contact; all others become Lead. Standard PII fields (name, phone, email, birthdate, address, med ID) map directly; loyalty point balance and tier status migrate to custom fields aiq_loyalty_points__c and aiq_loyalty_tier__c.

Alpine IQ Order records contain order ID, status, timestamps, customer PII, item data (product name, category, SKU, brand, price, discount), payment details, and attribution parameters. Microsoft Dynamics 365 Sales has no native Order object; we create a custom entity aiq_order__c with the relevant fields, or map to Opportunity with Line Items if the customer prefers an Opportunity-centric sales process. The choice is made during scoping based on the customer's revenue recognition workflow.

Alpine IQ audiences are segmented contact groups used for campaign targeting. We export audience membership (contact ID plus audience name and points multiplier) and create a static Marketing List in Dynamics 365 for each audience. The points multiplier migrates to a custom field aiq_audience_multiplier__c on the MarketingListMember record or as a custom field on the Contact if the customer prefers per-contact audience scoring.

Loyalty point balances and tier names are stored as custom fields on the Contact record: aiq_loyalty_points__c (number), aiq_loyalty_tier__c (text), and aiq_reward_override__c (boolean). The rules governing point expiration, tier progression thresholds, and reward eligibility are configuration-level settings in Alpine IQ and do not export. We deliver a loyalty program snapshot document listing all reward structures for manual rebuild in Dynamics 365 Power Automate or a loyalty management ISV.

Alpine IQ discount groups map to POS discount rules and customer eligibility flags. We export the discount group name and eligibility status as a custom picklist field aiq_discount_group__c on the Contact. The POS-side discount rule configuration does not migrate; we provide a written handoff document listing each discount group with its eligibility criteria for the customer's POS admin to reconfigure.

Email and SMS opt-in status tracked via Alpine IQ /api/v2/optin endpoints migrates to Dynamics 365 Contact. Email opt-in becomes HasOptedOutOfEmail (false = opted in); SMS opt-in becomes a custom boolean field aiq_sms_optin__c. Each opt-in record is timestamped and we preserve the last opt-in date in aiq_email_optin_date__c and aiq_sms_optin_date__c custom fields.

Multi-location Alpine IQ accounts map each integration to a specific store. We extract the full store mapping configuration and validate that store names in Alpine IQ match the Account names in Dynamics 365. Mismatched store names require correction before migration because Dynamics 365 does not have Alpine IQ's integration-name-to-store resolver. We flag discrepancies during scoping and provide a store-name reconciliation worksheet.

Alpine IQ's attr parameter on order objects stores campaign attribution values (UTM-like sources). We export the raw attr string and parse it into structured custom fields: aiq_attr_source__c, aiq_attr_medium__c, aiq_attr_campaign__c, and aiq_attr_content__c on the order or Opportunity entity. This enables campaign ROI reporting in Dynamics 365 without a separate analytics export.

Alpine IQ supports custom fields on Persona records. We export all custom properties alongside standard fields and map them to custom fields in Dynamics 365 with API names prefixed aiq_ (for example, aiq_preferred_strain__c, aiq_visit_frequency__c). Field types are matched to Dynamics 365 equivalents: text to Text, numbers to Number, dates to Date, and multi-select to Choice.

Every Alpine IQ Persona carries a source ID from the integration that created it (POS, ecommerce, etc.). We preserve all source IDs in a custom field aiq_source_id__c (text) and aiq_source_system__c (text) on the Contact record. This maintains the integration audit trail and enables reconciliation if the customer later re-connects POS integrations to Dynamics 365.