Migrate your Insider data
AI-powered customer engagement platform with a native CDP and multi-channel orchestration (SMS, WhatsApp, email, app, web) for mid-market and enterprise brands.
In its favor
Why people choose Insider
The signal that keeps Insider on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Multi-channel orchestration from one platform — native SMS, WhatsApp, email, app push, and web personalization mean teams consolidate tools rather than stitching together point solutions.
Behavioral segmentation across user attributes and events — customers use Insider's CDP to build audience segments based on product views, purchase history, lifecycle stage, and custom properties without SQL.
Automated journey orchestration with AI assist — journey builders chain triggers, conditions, and channel steps into lifecycle flows for onboarding, win-back, and loyalty programs.
Strong onboarding and customer success support — reviews repeatedly cite the Onboarding and Customer Success teams as a reason to stay, particularly for teams without dedicated technical resources.
Established track record with 2,000+ enterprise customers — the platform's scale and longevity in the market reassures teams evaluating long-term vendor commitments.
Steep learning curve and onboarding complexity — multiple reviews mention feeling overwhelmed by numerous options, difficult setup, and a lack of guided templates for smaller teams without in-house technical staff.
Long implementation timelines and contract lock-in — the spendbase article notes ~3+ months to fully roll out and annual/multi-year contract terms, which frustrates teams wanting faster time-to-value.
Pricing opacity and traffic-based cost model — there is no public pricing page; costs appear to scale with traffic volume, making budget forecasting difficult for growing teams evaluating the platform.
Advanced features gated behind higher tiers — SMB customers report that more sophisticated personalization, AI-driven suggestions, and deep analytics require a level of technical resource or enterprise plan they do not have.
Difficult migration path when leaving — no automated export of journeys, automations, or custom segments means leaving requires manual reconstruction of all campaign logic in the new platform.
Reasons to switch
Why people leave Insider
The recurring reasons buyers give for replacing Insider. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Insider fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Insider pricing overview
Insider does not publish public pricing. Costs appear to scale with traffic volume (message sends, user events, and profile activity) rather than flat per-seat or per-feature tiers. Annual or multi-year contract commitments are standard. Prospective customers must engage sales for a custom quote, and implementation typically spans 3+ months before the platform is fully operational.
Custom Enterprise
Tier 1 of 1
Not publicly disclosed — requires sales contact
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Insider's schedule — see our quote-based pricing →
What gets migrated
Insider object support
Object-by-object support for Insider migrations. Per-pair details surface during scoping.
Users (Profiles)
Fully supportedUsers are the primary object in Insider's CDP. Standard profile attributes (email, phone, name, device identifiers) map 1:1 via the Unification API upsert endpoint. Custom user attributes are preserved but require explicit field mapping since the schema is tenant-specific.
Events (Behavioral)
Fully supportedEvents and their associated parameters are exported via the Raw Export API. We preserve the full event stream including event_name, timestamp, and all attached event_parameters. Events can be filtered at export time by date range or user segment.
Segments
Mapping requiredSegments are defined by attribute rules and event conditions stored in Insider's CDP. When migrating out, we export the member list and the segment's rule definition as metadata. The rule logic itself must be manually reconstructed in the target platform's equivalent segmentation engine.
Journeys (Automations)
Mapping requiredJourneys are multi-step event-driven workflows. Each journey contains entry triggers, conditional gates, channel steps (email/SMS/WhatsApp/push), and exit conditions. We export journey definitions as structured metadata but the automation logic must be manually rebuilt in the target platform since no export/import API exists.
Products (Catalog)
Fully supportedProduct catalog data including sku, name, price, category, images, and custom attributes is accessible via Insider's listing/product objects and the Website Integration Wizard. These map directly to standard e-commerce product schemas in destination platforms.
Transactions (Orders)
Fully supportedTransaction objects capture order_id, total, items, currency, and timestamps. These are passed via the transaction sub-object and preserved in exports. We map them to the destination platform's order or purchase object on a field-by-field basis.
Channels (SMS/WhatsApp/Email/Push/Web)
Mapping requiredInsider natively supports SMS, WhatsApp, Email, App Push, and Web channels. Channel configuration (sender IDs, templates, opt-in/opt-out settings) is platform-specific and requires re-registration or re-verification in the destination. We preserve channel assignment metadata per user but not the channel credentials themselves.
Custom Attributes
Mapping requiredUsers can have arbitrary custom properties beyond the standard schema. These are stored as key-value pairs in the user profile. We export all custom attributes as flat key-value columns; mapping to the destination's equivalent custom field system requires a field-mapping pass per customer.
Lists
Mapping requiredLists are static user collections beyond segment-based dynamic membership. We export list membership (user ID + list ID) and recreate list membership in the target platform by creating corresponding static groups or segments there.
Tags
Mapping requiredUsers can be tagged with arbitrary string labels. Tags export as an array per user. We preserve tag arrays and recreate them as groups, labels, or custom properties in the destination depending on what that platform supports.
| Object | Support | Notes |
|---|---|---|
| Users (Profiles) | Fully supported | Users are the primary object in Insider's CDP. Standard profile attributes (email, phone, name, device identifiers) map 1:1 via the Unification API upsert endpoint. Custom user attributes are preserved but require explicit field mapping since the schema is tenant-specific. |
| Events (Behavioral) | Fully supported | Events and their associated parameters are exported via the Raw Export API. We preserve the full event stream including event_name, timestamp, and all attached event_parameters. Events can be filtered at export time by date range or user segment. |
| Segments | Mapping required | Segments are defined by attribute rules and event conditions stored in Insider's CDP. When migrating out, we export the member list and the segment's rule definition as metadata. The rule logic itself must be manually reconstructed in the target platform's equivalent segmentation engine. |
| Journeys (Automations) | Mapping required | Journeys are multi-step event-driven workflows. Each journey contains entry triggers, conditional gates, channel steps (email/SMS/WhatsApp/push), and exit conditions. We export journey definitions as structured metadata but the automation logic must be manually rebuilt in the target platform since no export/import API exists. |
| Products (Catalog) | Fully supported | Product catalog data including sku, name, price, category, images, and custom attributes is accessible via Insider's listing/product objects and the Website Integration Wizard. These map directly to standard e-commerce product schemas in destination platforms. |
| Transactions (Orders) | Fully supported | Transaction objects capture order_id, total, items, currency, and timestamps. These are passed via the transaction sub-object and preserved in exports. We map them to the destination platform's order or purchase object on a field-by-field basis. |
| Channels (SMS/WhatsApp/Email/Push/Web) | Mapping required | Insider natively supports SMS, WhatsApp, Email, App Push, and Web channels. Channel configuration (sender IDs, templates, opt-in/opt-out settings) is platform-specific and requires re-registration or re-verification in the destination. We preserve channel assignment metadata per user but not the channel credentials themselves. |
| Custom Attributes | Mapping required | Users can have arbitrary custom properties beyond the standard schema. These are stored as key-value pairs in the user profile. We export all custom attributes as flat key-value columns; mapping to the destination's equivalent custom field system requires a field-mapping pass per customer. |
| Lists | Mapping required | Lists are static user collections beyond segment-based dynamic membership. We export list membership (user ID + list ID) and recreate list membership in the target platform by creating corresponding static groups or segments there. |
| Tags | Mapping required | Users can be tagged with arbitrary string labels. Tags export as an array per user. We preserve tag arrays and recreate them as groups, labels, or custom properties in the destination depending on what that platform supports. |
Gotchas
What to watch for in Insider migrations
Issues we've hit on past Insider migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API rate limit of 25,000 requests per minute is shared across endpoints
No automated journey export — automations must be rebuilt manually on exit
Pricing is traffic-based with no public tiers, leading to billing surprises
Contract lock-in with annual or multi-year terms
Long implementation ramp complicates early-stage migrations
| Severity | Issue |
|---|---|
| High | API rate limit of 25,000 requests per minute is shared across endpoints |
| High | No automated journey export — automations must be rebuilt manually on exit |
| Medium | Pricing is traffic-based with no public tiers, leading to billing surprises |
| Medium | Contract lock-in with annual or multi-year terms |
| Low | Long implementation ramp complicates early-stage migrations |
Leaving Insider?
Where Insider customers move next
12 destinations Insider can migrate to.
How a Insider migration works
Four steps, Insider-specific
Connect
Partner ID and API key authentication — credentials issued per Insider account and scoped to the organization's partner identifier. into Insider. Scopes limited to read-only on the data we move.
Map
We translate Insider-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Insider quirks before production.
Migrate
Full migration with Insider rate-limit handling. Rollback available throughout.
FAQ
Insider migration FAQ
Answers to the questions buyers ask most during Insider migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Insider migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Insider.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Insider setup and destination — written quote back within a business day.