Migrate from Alpine IQ to Twenty CRM

Alpine IQ Personas are the primary contact unit with name, phone, email, birthdate, med ID, and custom properties. We migrate Personas to Twenty CRM Contacts by default. If the customer uses Twenty's Person object for individual records without an associated Company, we configure that at scoping. Loyalty point balance maps to a numeric custom field, tier name to a text custom field, and the original alpine_iq_uid preserves as an external ID for reconciliation.

Order records in Alpine IQ include order ID, status, timestamps, customer PII, item data (product name, category, SKU, brand, price, discount), payment details, and attribution parameters. We map Orders to Twenty Opportunities with custom line-item fields capturing product name, category, SKU, brand, unit price, and discount. The Order total becomes the Opportunity amount, and the original alpine_iq_order_id preserves for audit.

Loyalty point balances and tier names are stored as properties on the Alpine IQ Persona record. We create two custom fields on the Twenty CRM Contact: loyalty_points_balance (number) and loyalty_tier_name (text). Point expiration rules, tier progression thresholds, and reward eligibility are configuration-level settings in Alpine IQ and do not export; we request a loyalty program snapshot from the customer and deliver it as a written configuration reference for manual rebuild.

Alpine IQ Audiences are segmented contact groups used for campaign targeting. Audience membership is stored by contact ID with a points multiplier per audience. We export audience membership as tag records on the Twenty CRM Contact using the audience name as the tag label. The customer decides during scoping whether to preserve the points multiplier as a secondary tag field or as a note on the contact.

Email and SMS opt-in status is tracked via Alpine IQ's /api/v2/optin endpoints per email address or phone number. We migrate opt-in flags as boolean custom fields on the Twenty CRM Contact: email_opt_in and sms_opt_in. The opt-in timestamp migrates as an additional date field if the source record contains it.

Multi-location Alpine IQ accounts map each integration or data source to a specific store location with exact name matching between Alpine IQ and the connected POS. We create a Dispensary Location custom object in Twenty CRM with fields for store_name, pos_integration_type, pos_location_id, and favorite_store_count. The customer validates that all location names in Alpine IQ exactly match the destination Twenty Location names before migration begins.

The attr parameter on Alpine IQ orders tracks campaign attribution and UTM-like sources at the order level. We preserve attribution values in custom fields on the Twenty CRM Contact: original_source, original_utm_campaign, original_utm_medium, and original_utm_content. Attribution parameters also exist on individual Order records as custom Opportunity fields.

Alpine IQ discount groups map to specific POS discount rules and customer eligibility flags, visible in the Dutchie integration guide as mapped customer profile fields. We export discount group names as a multi-value tag or custom picklist field on the Twenty CRM Contact. POS discount rule configuration does not export; we document the discount group-to-rule mapping for the customer to rebuild in the POS.

Alpine IQ supports custom fields on Persona records set via override endpoints. We export all custom properties alongside standard fields and create matching custom fields in Twenty CRM using the schema API. Custom field type mapping follows: text to text, number to number, date to date, boolean to boolean, and multi-select to multi-select where supported.

Every Alpine IQ contact has 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 on the Twenty CRM Contact for debugging and reconciliation. Push notification device tokens do not transfer between platforms because they are device-specific and platform-specific.

Alpine IQ Flows are automation triggers based on events like order_created, order_completed, cart_abandoned, and behavioral events. Event schemas vary by integration. We do not migrate Flow configurations as code. We export a written inventory of all active Flows with their trigger event, conditions, and action sequence for the customer's admin to rebuild in Twenty via workflow tools or Zapier.