Migrate from Insider to Nutshell

Insider user profiles with email, phone, name, and device identifiers map to Nutshell Person records. The Insider user_id becomes a legacy_id field for deduplication. Custom user attributes from Insider export as key-value pairs; we write these to a Nutshell Notes field and recommend creating custom Person fields for any attributes that recurred consistently across the user base. The mapping requires splitting multi-value arrays (such as phone numbers) into individual fields or a comma-separated string in the custom_notes field.

Insider Company records map directly to Nutshell Company. The company domain name from Insider becomes the Nutshell domain field. We use company name as the primary match key. If Insider has no company object, we extract company information from the user profile's last_seen_domain or company_name field and create Nutshell Companies during Person import, linking each Person to its Company via the Nutshell company_name match.

Insider behavioral events (product views, cart actions, purchase events, custom events) cannot map to typed Nutshell CRM fields because Nutshell does not have an event object. We convert recent and high-signal events (last 90 days of key lifecycle events) into Nutshell Notes attached to the Person record, preserving event_name and timestamp in the note body. Historical bulk event exports beyond 90 days are flagged as data-loss candidates during scoping. The customer decides whether to include event notes based on the Nutshell custom field plan.

Insider segments defined by attribute rules or event conditions export as a member list. We export the member list and recreate it as a static People List in Nutshell. The segment rule logic (attribute conditions, event triggers) has no Nutshell equivalent and is documented in the journey inventory deliverable for manual rebuild if the customer requires dynamic segmentation logic.

Insider Journeys with multi-step triggers, conditional gates, and channel actions have no Nutshell equivalent. We export a structured journey audit during discovery documenting every active Journey, its entry trigger, step logic, channel actions, and exit conditions. The customer uses this inventory to manually rebuild lifecycle automations in Nutshell's activity and task model post-migration. This is explicitly out of migration scope as code.

Insider product catalog data (sku, name, price, category, images) has no native Nutshell product management module. We map product data to Nutshell custom fields on Deals, storing sku, product_name, and price as text or currency fields. If the customer requires a product library, we recommend a separate product management integration (QuickBooks, Cin7) post-migration.

Insider transaction records (order_id, total, items, currency, timestamps) map to Nutshell Deals. The transaction total becomes the Deal value. Order metadata (item count, currency, order date) stores in a custom Notes field or custom Deal fields. The related Person and Company are linked via Nutshell's deal association to the corresponding Person and Company records resolved during import.

Insider user tags (string labels stored as arrays per profile) map to Nutshell Tags. Tag arrays export as a comma-separated string per Person. Nutshell Tags are not hierarchical and do not support tag metadata, so tag groupings from Insider are flattened into tag names or documented in the custom notes field. Tag-based audience logic is noted for manual rebuild as static Nutshell lists.

Insider static Lists (named user collections beyond dynamic segments) export as member lists. We recreate each list as a Nutshell People List with the same name, matching members by email against the migrated Person records. Lists without a clear Nutshell equivalent are mapped to static People Lists with a naming convention preserving the original list name.

Insider's channel configuration (SMS sender IDs, WhatsApp business account settings, email sender domains, push notification credentials) is platform-bound and not portable across systems. We document the channel configuration for each active channel so the customer can re-register sender credentials in Nutshell or an alternative channel platform post-migration. Channel-specific contact preferences (SMS opt-in, WhatsApp consent) migrate as custom fields on the Person record.