How long does an Alpine IQ to Nutshell migration take?

Most migrations land between two and four weeks for accounts under 15,000 Personas and 10,000 Orders with loyalty balances and opt-in flags stored as custom fields. Accounts with high blocklist volumes requiring supplemental export, large order histories exceeding 50,000 records, or multi-location store mapping configurations requiring name reconciliation move to five to eight weeks. The primary time variable is the scope of the loyalty program snapshot review and the number of custom properties requiring field creation in Nutshell before migration begins.

Do Alpine IQ Audiences and Flow automations migrate to Nutshell?

No. Alpine IQ Audiences are dynamic behavioral segments driven by POS-synced purchase activity; Nutshell has no dynamic segmentation engine and audience membership cannot be replicated as live, auto-updating segments. We export audience membership as a static text list stored in a custom field at migration time, but the list becomes static. Flow automations (event-triggered workflows like order_created, order_completed, cart_abandoned) have no Nutshell equivalent and do not migrate. We deliver a written inventory of every active Audience and Flow with a description of the trigger, conditions, and actions for the customer's admin to rebuild using Nutshell's standard workflows and manual list management.

What happens to our loyalty points and tier program after migration?

Point balances and tier names transfer as custom fields on each Nutshell People record. However, the rules governing point expiration, tier progression thresholds, minimum redemption amounts, and reward eligibility are configuration-level settings in Alpine IQ that do not export via API. We preserve all point balances accurately, but the destination Nutshell instance has no automated loyalty logic. Customers must request a loyalty program export snapshot from Alpine IQ before migration and manually configure equivalent rules in Nutshell using custom fields and workflows, or accept that loyalty management becomes a manual process post-migration.

What does an Alpine IQ to Nutshell migration typically cost?

Migrations under 15,000 Personas and 10,000 Orders with loyalty data stored as custom fields land between $3,500 and $5,500 and complete in two to four weeks. Accounts with high blocklist volumes, large order histories (over 50,000 records), or multi-location store mapping requirements move to $6,500-$9,000 and five to eight weeks. Nutshell subscription cost ($25-$42 per user per month) and any Zapier/Make integration fees for POS data flow after migration sit outside the migration fee and remain the customer's recurring cost.

Can we keep using our POS integrations after moving to Nutshell?

No. Alpine IQ's bidirectional POS integrations (Dutchie, Flowhub, Cova, Treez, Blaze) do not transfer to Nutshell. After migration, Nutshell has no native POS integration layer. Customer data in Nutshell is disconnected from the POS; new orders and loyalty transactions do not flow automatically. Teams relying on POS-synced enrichment (updated purchase history, point balance changes, tier changes triggered by new orders) must implement a Zapier or Make integration between their POS and Nutshell after migration, or accept that CRM data becomes stale unless updated manually.

What happens to SMS compliance data during migration?

We migrate SMS opt-in flags from Alpine IQ's /api/v2/optin endpoints to custom boolean fields on Nutshell People records. However, Alpine IQ's purpose-built compliance tools for regulated industries—including carrier filtering rules, SMS suppression management, and state-specific restrictions for cannabis-adjacent markets—do not transfer. Migrated opt-in flags in Nutshell are stored values only; they do not trigger compliance checks or suppression list management. If the customer plans to send SMS from Nutshell, they must implement a dedicated SMS compliance vendor and re-verify consent with that vendor post-migration.

How do you handle blocklisted contacts that Alpine IQ excludes from the API?

Alpine IQ's Personas API explicitly filters out blocklisted contacts from standard GET responses. We mitigate this by querying via alternative endpoints where available and cross-referencing opt-in status flags on returned records. During scoping we ask the customer to estimate their blocklist volume and adjust the export strategy accordingly. We deliver a blocklist reconciliation report listing any contacts that were excluded from the export, the suppression reason where known, and the opt-in flag status for each. The customer reviews this report and can request that excluded contacts be added manually to Nutshell if appropriate.

Do we lose order history and attribution data during migration?

No. Alpine IQ Order records (order ID, status, timestamps, customer PII, item data, pricing, discounts, and attribution parameters) transfer to Nutshell Deals. Line item data is stored as JSON in a custom Deal field because Nutshell has no native Order or Line Item object. Attribution parameters (the attr field used for campaign attribution) transfer to a custom field on the Deal for reporting reconstruction. The full order history is preserved; however, Nutshell's reporting for order-level analysis requires using custom reports and filters on the Deal fields rather than a native order management interface.

Alpine IQ to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Alpine IQ and Nutshell serve fundamentally different markets. Alpine IQ is a purpose-built customer engagement platform for regulated retail, particularly cannabis dispensaries, with native loyalty points, tier management, POS integrations, and compliance tooling for SMS. Nutshell is a general small-to-mid-market CRM that tracks People, Companies, Deals, and Activities without a native loyalty or POS integration layer. Moving from Alpine IQ to Nutshell means accepting the loss of automated loyalty program management and cannabis-specific compliance tools in exchange for a simpler CRM structure and predictable per-seat pricing. We extract all Personas and Order records via Alpine IQ's REST API, preserve point balances and tier names as Nutshell custom fields, migrate opt-in status flags, and document every loyalty program rule and automation for manual rebuild. We do not migrate Audiences, Discount Groups, or Flow automations as code; we deliver a written inventory for your admin.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Alpine IQ

What's pushing teams away

Steep learning curve with a complex, layered interface makes onboarding staff time-consuming and delays realizing value from advanced segmentation and automation features.
Reporting tools lack customization and flexibility—dashboards are difficult to parse at a glance and loading times for filtered reports frustrate marketing teams.
SMS deliverability and compliance requirements in regulated markets can limit campaign effectiveness, especially as carriers tighten filtering on cannabis-adjacent content.
Multi-location store mapping requires exact name matching between Alpine IQ and POS systems, creating friction during rollout and causing sync failures when locations are renamed.
Per-store and per-contact pricing model historically inflated costs for growing dispensary chains, prompting operators to evaluate alternatives when expanding across new markets.

Choosing

Nutshell

What's pulling them in

Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Alpine IQ objects map to Nutshell

Each row shows how a Alpine IQ object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Alpine IQ

Personas (Contacts)

maps to

Nutshell

People

1:1

Fully supported

Alpine IQ Personas map to Nutshell People records. All standard PII (first name, last name, phone, email, birthdate, address, medical ID) migrates to matching Nutshell People fields. We query via /api/v2/loyalty POST for full contact export and cross-reference blocklist suppression flags to ensure suppressed contacts are not silently omitted from the standard GET response.

Alpine IQ

Orders

maps to

Nutshell

Deals

1:1

Fully supported

Alpine IQ Order records map to Nutshell Deals. The order ID becomes a custom field, order status and substatus become custom picklist fields, and line item data (product name, category, SKU, brand, price, discount) is stored as a formatted text block or JSON custom field because Nutshell has no native Order or Line Item object. Attribution parameters (attr field) migrate as a text custom field for campaign reporting reconstruction.

Alpine IQ

Loyalty Programs (Points and Tiers)

maps to

Nutshell

People (custom fields)

lossy

Mapping required

Alpine IQ stores point balances and tier names on the Persona record. We export point_balance as a numeric custom field loyalty_points__c and tier_name as a text custom field loyalty_tier__c. The rules governing point expiration, tier progression thresholds, and reward eligibility are configuration-level settings in Alpine IQ that do not export; we deliver a loyalty program snapshot document for the customer's admin to manually reconfigure equivalent rules in Nutshell.

Alpine IQ

Opt-In Records

maps to

Nutshell

People (custom fields)

1:1

Fully supported

Alpine IQ tracks email and SMS opt-in status via /api/v2/optin endpoints. We migrate sms_optin as a boolean custom field sms_opt_in__c and email_optin as email_opt_in__c on the Nutshell People record. Opt-in status must be re-verified post-migration if the destination SMS vendor requires fresh consent records.

Alpine IQ

Audiences

maps to

Nutshell

Tags and Lists

1:1

Mapping required

Alpine IQ Audiences are segmented contact groups with membership and points multipliers per contact. We export audience membership as a text list stored in a custom field audiences__c on the Nutshell People record. Dynamic behavioral segments do not replicate; the customer recreates static segments as Nutshell Tags or manual Lists post-migration. Points multipliers per audience are documented separately for manual rebuild.

Alpine IQ

Discount Groups

maps to

Nutshell

People (custom fields)

1:1

Mapping required

Alpine IQ Discount Groups map to POS discount rules and customer eligibility flags. We export the discount group name as a text custom field discount_group__c on the Nutshell People record. The POS-level discount rules themselves are not transferable and require reconfiguration in the connected POS and in any Nutshell-integrated pricing tool.

Alpine IQ

Custom Contact Properties

maps to

Nutshell

People (custom fields)

lossy

Mapping required

Alpine IQ supports custom fields on Persona records. We export all custom properties alongside standard fields and map them to Nutshell People custom fields created before migration. Field type mapping is done at scoping: text to text, numeric to number, date to date, boolean to boolean.

Alpine IQ

Store/Location Mappings

maps to

Nutshell

Accounts (custom fields)

lossy

Mapping required

Alpine IQ multi-location accounts require store-to-integration name matching. We extract the full store mapping configuration from the Alpine IQ account during scoping and document it as a location reference table. The destination Nutshell implementation uses Account records for locations, with a custom field store_name__c for name matching. Exact name alignment between Alpine IQ store names and POS location names is preserved in the documentation for manual reconfiguration.

Alpine IQ

Integration Source IDs

maps to

Nutshell

People (custom fields)

1:1

Fully supported

Every Alpine IQ contact has a source ID from the integration that created it (POS, ecommerce). The /api/v1/piis/:uid/bySrcID endpoint allows lookup by source ID. We preserve all source IDs in a text custom field source_ids__c on the Nutshell People record for reference. These IDs have no functional role in Nutshell but support audit and reconciliation.

Alpine IQ	Nutshell	Compatibility
Personas (Contacts)	People1:1	Fully supported
Orders	Deals1:1	Fully supported
Loyalty Programs (Points and Tiers)	People (custom fields)lossy	Mapping required
Opt-In Records	People (custom fields)1:1	Fully supported
Audiences	Tags and Lists1:1	Mapping required
Discount Groups	People (custom fields)1:1	Mapping required
Custom Contact Properties	People (custom fields)lossy	Mapping required
Store/Location Mappings	Accounts (custom fields)lossy	Mapping required
Integration Source IDs	People (custom fields)1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Alpine IQ gotchas

Medium

Blocklist contacts excluded from standard API GET

High

Store name matching required for loyalty attribution

Low

Initial integration sync delay up to 24 hours

Medium

Points and tier expiration logic not exported

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Alpine IQ gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
Medium	Blocklist contacts excluded from standard API GET	High	Contact tier limits enforced on import
High	Store name matching required for loyalty attribution	Medium	No bulk API endpoint requires paginated extraction
Low	Initial integration sync delay up to 24 hours	Medium	Email sequences not exportable via API
Medium	Points and tier expiration logic not exported	Medium	Foundation plan disables key sales features

Pair-specific challenges

Loyalty program rules and tier logic do not transfer

Alpine IQ stores point balances and tier names on contact records, but the rules governing point expiration, tier progression thresholds, minimum redemption amounts, and reward eligibility are configuration-level settings that do not export via API. We preserve all point balances and tier names accurately during migration, but the destination Nutshell instance will have no automated loyalty logic. Customers must request a loyalty program export snapshot before migration and manually configure equivalent rules in Nutshell using custom fields, workflows, and third-party tools, or accept that loyalty management becomes a manual process post-migration.
Blocklisted contacts excluded from standard API export

Alpine IQ's Personas API explicitly filters out any blocklisted contacts from GET responses. Suppressed contacts are silently omitted from the standard export, which means the migrated Nutshell People list may be missing contacts who opted out or were manually blocked. We mitigate this by querying the full list via alternative endpoints where available and cross-referencing opt-in status flags on returned records. During scoping we confirm whether the customer has a high blocklist volume and adjust the export strategy accordingly. Any missing contacts are documented for manual review.
Nutshell has no native loyalty or POS integration layer

Alpine IQ is deeply integrated with POS systems (Dutchie, Flowhub, Cova, Treez) and syncs customer records and transaction data bidirectionally in real time. Nutshell has no native POS integration. After migration, customer data in Nutshell is disconnected from the POS; new orders and loyalty transactions do not flow automatically. Teams relying on POS-synced enrichment (purchase history, point balance updates, tier changes) must implement a Zapier or Make integration between their POS and Nutshell, or accept that CRM data goes stale unless manually updated.
SMS compliance tooling does not transfer

Alpine IQ includes purpose-built SMS compliance tools for regulated industries, including opt-in management, carrier filtering rules, and state-specific restrictions for cannabis-adjacent messaging. Nutshell has no native SMS or compliance tooling. Migrated SMS opt-in flags in Nutshell are stored values only; they do not trigger carrier compliance checks or suppression list management. Customers using Nutshell for SMS campaigns must implement a dedicated SMS vendor (such as Attentive, Klaviyo SMS, or a cannabis-specific SMS platform) and re-verify consent with that vendor post-migration.
Audiences and Flow automations do not migrate as code

Alpine IQ Audiences are dynamic behavioral segments updated by purchase activity and tied to POS integration events. Nutshell has no dynamic segmentation engine; audience membership cannot be replicated as live, auto-updating segments. We export audience membership as a static list stored in a custom field at migration time, but the list becomes static. Flow automations (order_created, order_completed, cart_abandoned triggers) similarly have no Nutshell equivalent and do not migrate. We deliver a written inventory of every active Audience and Flow for the customer's admin to rebuild using Nutshell's standard workflows and manual list management.

Migration approach

Six steps for a successful Alpine IQ to Nutshell data migration

Discovery and Alpine IQ export audit

We audit the Alpine IQ account across Personas, Orders, Audiences, Loyalty Programs, Discount Groups, Opt-In records, Custom Contact Properties, and Store Mappings. We query the /api/v2/loyalty and /api/v1/piis endpoints to assess export volume, blocklist suppression rate, and the presence of custom properties. We extract the full store mapping configuration and validate POS location name alignment. We request a loyalty program snapshot document from Alpine IQ support before migration begins so that the customer has a reference for manual rebuild. The discovery output is a written migration scope document with record counts, custom field schema for Nutshell, and a loyalty program snapshot checklist.
Nutshell schema design and custom field creation

We design the Nutshell People, Account, and Deal custom field schema before any data transfer. This includes loyalty_points__c (numeric), loyalty_tier__c (text), sms_opt_in__c (boolean), email_opt_in__c (boolean), audiences__c (text), discount_group__c (text), source_ids__c (text), medical_id__c (text), and attr_params__c (text). For Deals, we create line_items__c (text), order_id__c (text), and attr_params__c (text). Custom fields are created in the Nutshell account before migration begins. We also configure Deal status picklist values to align with Alpine IQ order status values.
Blocklist reconciliation and contact export

We run the Personas export via Alpine IQ's API, using alternative endpoints to capture suppressed contacts not returned by the standard GET. We cross-reference opt-in status flags on returned records to identify any discrepancies between the suppressed list and the opt-in flag values. The export is chunked into API-safe batches (Alpine IQ does not publish public rate limits, so we use conservative 100-record batches with exponential backoff). We deliver a blocklist reconciliation report listing any contacts that were excluded from the export, the count by suppression reason, and the opt-in flag status for each.
Order export and Deal migration

We export all Order records from Alpine IQ via the Orders API endpoint, including order ID, status, timestamps, customer PII, item data, pricing, discounts, and attribution parameters. Orders are chunked into batches and mapped to Nutshell Deals with composed Deal names (order ID plus date), status values translated per the agreed mapping, and line items stored as JSON in the line_items__c custom field. Attribution parameters are stored in attr_params__c for campaign reporting reconstruction. Customer PII is linked to Nutshell People records via email match.
Loyalty and audience migration

We extract point balances and tier names from each Alpine IQ Persona record and write them to loyalty_points__c and loyalty_tier__c on the corresponding Nutshell People record. Audience membership is written as a text list to audiences__c. Discount group names are written to discount_group__c. Integration source IDs are written to source_ids__c for audit reference. The loyalty program rules (expiration windows, tier thresholds, redemption logic) are not data-migrated; they are documented from the Alpine IQ snapshot and handed off to the customer's admin for manual rebuild.
Cutover, validation, and automation inventory delivery

We freeze writes to Alpine IQ during the cutover window, run a final delta export of any records modified during migration, and push the delta to Nutshell. We validate record counts (People in Nutshell vs Personas in Alpine IQ, Deals vs Orders), spot-check 25-50 records for field-level accuracy, and deliver a migration summary report. We deliver the written inventory of Audiences and Flow automations for the customer's admin to rebuild in Nutshell using standard workflows, tags, and lists. We do not rebuild automations or loyalty program rules as part of the migration scope.

Platform deep dives

Context on both ends of the pair

Alpine IQ

Source

Strengths

Purpose-built compliance tooling for regulated industries including cannabis marketing restrictions and SMS carrier rules.
Deep bidirectional POS integrations that sync customer records and transaction data without manual reconciliation.
Flexible audience segmentation combining purchase frequency, product category, visit recency, and custom behavioral signals.
Order attribution tracking with attr parameters enables campaign ROI reporting at the order level.
BigQuery integration provides a documented bulk data export path for organizations with data warehouse infrastructure.

Weaknesses

Steep learning curve and complex interface delay time-to-value for new users and smaller teams without dedicated ops resources.
Reporting and dashboard tooling lacks customization, filtering depth, and suffers from slow load times on large datasets.
API rate limits are not publicly documented, creating uncertainty for large-scale migration batch planning.
SMS deliverability in cannabis-adjacent markets is constrained by carrier filtering, limiting campaign reach despite opt-in compliance.
Blocklist suppression is handled server-side on GET but the full blocklist is not accessible via API, complicating audit completeness.

Nutshell

Destination

Strengths

Simple, intuitive interface with minimal learning curve for sales teams new to CRM
Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
Full data export tool available for all account data including backups
Open JSON-RPC API allows programmatic access to all core objects
Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

	Alpine IQ Source	Nutshell Destination
Strengths	Purpose-built compliance tooling for regulated industries including cannabis marketing restrictions and SMS carrier rules. Deep bidirectional POS integrations that sync customer records and transaction data without manual reconciliation. Flexible audience segmentation combining purchase frequency, product category, visit recency, and custom behavioral signals. Order attribution tracking with attr parameters enables campaign ROI reporting at the order level. BigQuery integration provides a documented bulk data export path for organizations with data warehouse infrastructure.	Simple, intuitive interface with minimal learning curve for sales teams new to CRM Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost Full data export tool available for all account data including backups Open JSON-RPC API allows programmatic access to all core objects Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication
Weaknesses	Steep learning curve and complex interface delay time-to-value for new users and smaller teams without dedicated ops resources. Reporting and dashboard tooling lacks customization, filtering depth, and suffers from slow load times on large datasets. API rate limits are not publicly documented, creating uncertainty for large-scale migration batch planning. SMS deliverability in cannabis-adjacent markets is constrained by carrier filtering, limiting campaign reach despite opt-in compliance. Blocklist suppression is handled server-side on GET but the full blocklist is not accessible via API, complicating audit completeness.	Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Alpine IQ and Nutshell.

Object compatibility
B
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
Alpine IQ: 5 requests per second, 120 per minute, and 2,000 per hour per documented developer guide..
Data volume sensitivity
B
Alpine IQ doesn't expose a bulk API — REST + parallelization used for high-volume runs.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Alpine IQ to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Alpine IQ

Nutshell

How Alpine IQ objects map to Nutshell

What specifically takes care here

Six steps for a successful Alpine IQ to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Alpine IQ to Nutshell migration cost

What are you migrating?

Frequently asked questions about Alpine IQ to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from Alpine IQ.
Land in Nutshell, intact.

Migrate from Alpine IQ to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Alpine IQ

Nutshell

How Alpine IQ objects map to Nutshell

What specifically takes care here

Six steps for a successful Alpine IQ to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Alpine IQ to Nutshell migration cost

Frequently asked questions about Alpine IQ to Nutshell data migrations

Can't find your answer?

How long does an Alpine IQ to Nutshell migration take?

Do Alpine IQ Audiences and Flow automations migrate to Nutshell?

What happens to our loyalty points and tier program after migration?

What does an Alpine IQ to Nutshell migration typically cost?

Can we keep using our POS integrations after moving to Nutshell?

What happens to SMS compliance data during migration?

How do you handle blocklisted contacts that Alpine IQ excludes from the API?

Do we lose order history and attribution data during migration?

Related migrations to explore

Move from Alpine IQ. Land in Nutshell, intact.

Move from Alpine IQ.
Land in Nutshell, intact.