Migrate from Alpine IQ to Pipedrive

Alpine IQ Persona records map to Pipedrive Person. Standard fields (firstname, lastname, email, phone) map directly. Birthdate migrates to Pipedrive's birth_date field where supported or a custom date field. Address components (address, city, state, zip, country) combine into Pipedrive's address field as a formatted string. Medical ID maps to a custom text field med_id__c. Gender migrates as a custom picklist field. The integration source ID on each Persona is preserved in a custom field aiq_source_id__c to maintain the record lineage from the originating POS or ecommerce integration.

Alpine IQ Order records include order ID, status, timestamps, customer PII, item data (product name, category, SKU, brand, price, discount), payment details, and attribution params. Since Pipedrive has no native order object, we map order-level fields (order ID, total, status, timestamps) to a Deal record, and item-level detail (line items, product SKU, quantity, discount) to a custom object linked via DealId. Attribution params (attr) migrate as custom fields and are also written to a linked note for pipeline attribution reporting.

Alpine IQ does not have a dedicated Company object, but store and dispensary location data is stored in the Location configuration. Multi-location accounts use the Location records to group contacts by store. We map each Alpine IQ Location to a Pipedrive Organization record with the store name as the Organization name and the store address as the address field, enabling contacts to be linked to their home dispensary location via the Person-Organization relationship.

Loyalty point balances and tier names are stored on the Persona record in Alpine IQ. We export point_balance as a custom numeric field loyalty_points__c and tier_name as a custom picklist field loyalty_tier__c. Reward overrides and point multipliers per audience are preserved as custom fields loyalty_multiplier__c and reward_override__c. The rules governing point expiration, tier progression, and reward eligibility are configuration-level settings in Alpine IQ and do not export. We instruct the customer to request a loyalty program configuration snapshot before migration and rebuild equivalent rules in Pipedrive or a loyalty integration post-cutover.

Alpine IQ Audiences are segmented contact groups used for campaign targeting. Each contact can belong to multiple audiences with a points multiplier per audience. We map audience membership to Pipedrive Tags (one tag per audience name) and write the points multiplier value to a custom field audience_multiplier__c stored on the Person. For accounts with complex multi-audience membership, we also create a custom multi-select picklist field audience_list__c listing all active audiences for quick segmentation in Pipedrive's filter view.

Alpine IQ discount groups define POS-level discount eligibility and map to customer eligibility flags in the Dutchie and Flowhub integrations. We export the discount_group name and eligibility status as a custom text field discount_group__c and a custom boolean field discount_eligible__c on the Person record. These flags help the customer's Pipedrive admin configure discount-eligible pricing in Deals if the dispensary retains a POS-integrated pricing model.

Email and SMS opt-in status in Alpine IQ is tracked via /api/v2/optin endpoints per email address or phone number. We export sms_opt_in and email_opt_in as custom boolean fields on the Pipedrive Person. The double-opt-in flow configuration is Alpine IQ-specific and does not transfer; the customer must configure equivalent double-opt-in sequences in Pipedrive or their email service provider post-migration. Suppressed contacts require querying alternative endpoints before standard GET export to avoid silent omission.

The attr parameter in Alpine IQ tracks campaign attribution (source, medium, campaign) at the order level. Attribution values migrate as custom text fields deal_attr_source__c, deal_attr_medium__c, and deal_attr_campaign__c on the Deal. We also write the full raw attr string to a linked Note on the Deal for audit purposes. The customer can use these fields to build Pipedrive report filters and campaign ROI analysis by source.

Alpine IQ supports custom fields on Persona records via override endpoints. We export all custom properties alongside standard fields and create matching custom fields in Pipedrive using the same field labels and appropriate Pipedrive field types (text, numeric, date, picklist, boolean). Pipedrive Essential limits custom fields to approximately 50; Professional and above support up to 500. During scoping we confirm the total custom field count against the target Pipedrive edition and flag any overage for the customer to resolve before migration begins.

Every Alpine IQ contact carries a source ID from the POS or ecommerce integration that created it (Dutchie, Cova, Flowhub, etc.). The /api/v1/piis/:uid/bySrcID endpoint allows lookup by source ID. We preserve all source IDs in a custom field aiq_source_id__c on the Pipedrive Person, enabling the customer to cross-reference migrated contacts against the original Alpine IQ records during the validation window. Push notification IDs (device tokens) do not transfer between platforms and are exported as a written list for the customer's mobile team to manage re-enrollment post-migration.