Migrate from Iterable to Nutshell

Iterable User profiles (email, userId, dataId, and all custom fields) map to Nutshell Contact records, with the email address serving as the primary dedupe key. If the Iterable profile contains an account-level field (company name or domain), we also create a Nutshell Account record and link the Contact to it via the AccountId reference. We preserve all Iterable custom profile fields as Nutshell custom fields on Contact, flagging any field that contains behavioral or event-derived data (rather than factual contact attributes) for conversion to a notes field or a separate custom object.

Iterable Lists are audience segments used for campaign targeting. We export list names and user membership and convert these to Nutshell Contact tags or a multi-select custom field on Contact, depending on whether the customer prefers a tagging model or a field-based model. List counts per user migrate as separate tag entries; list names with segment logic do not transfer as segments because Nutshell has no native segmentation engine equivalent to Iterable Lists.

Iterable tracks channel-level opt-in/opt-out status per user across email, SMS, and push. We map these to Nutshell Contact custom fields: email_opt_in (boolean), sms_opt_in (boolean), and push_opt_in (boolean). Subscription event history (the log of status changes) migrates as a multi-line text custom field or a linked notes record because Nutshell does not have a native subscription event log object. We preserve the last status change timestamp per channel.

Iterable custom events track behavioral data (purchase, registration, feature use, cart abandonment) with arbitrary metadata payloads. Nutshell has no native behavioral event model. We assess the customer's use of custom event data: if events are used for lead scoring or segmentation in Iterable Journeys, we document the event schema and recommended Nutshell custom field equivalents. If events are used for historical record keeping, we migrate them as Nutshell Notes attached to the Contact with the event name, timestamp, and key metadata fields in the note body. High-volume event streams (tens of thousands per user) may require a data dictionary rather than individual note records.

Iterable purchase events record transaction data (orderId, total, items, associated user). We map purchase data to Nutshell Contact custom fields for summary data (lifetime_value__c, last_purchase_date__c, order_count__c) and optionally to Opportunity Line Items on a Deal if the customer uses Nutshell Deals to track customer accounts. Purchase event history beyond summary fields migrates as Notes because Nutshell does not have a native purchase history object.

Iterable Campaigns are sendable units with a channel type, template, and sending configuration. Nutshell has no campaign object. We export campaign metadata (name, channel, status, schedule, associated lists) to a written campaign inventory document that the customer's admin uses to plan rebuilds in Iterable (if retained) or in an alternative marketing automation tool. Template content migrates as HTML files saved to the customer's document store for reference.

Iterable Journeys are multi-step, multi-channel automation paths with trigger conditions, branching logic, and associated message actions. Nutshell has no workflow automation engine for cross-channel journeys. We export Journey definitions (trigger type, tiles, branching conditions, wait durations, associated templates and catalogs) to a written Journey inventory document that describes the logic in plain language so the customer's admin can rebuild in their chosen marketing automation tool. Journey re-trigger behavior is documented separately because it affects post-migration contact re-enrollment logic.

Iterable Templates define message content with HTML, plain text, and Handlebars personalization syntax. Nutshell does not have a template management system. We export template content as HTML files with Handlebars syntax preserved, saved to a shared document location for the customer's marketing team to import into their chosen marketing automation tool. Template metadata (name, channel type, associated campaigns) migrates as a template inventory spreadsheet.

Iterable Catalog is a product data store for dynamic content insertion in messages (product recommendations, pricing, inventory). Nutshell has no catalog or product content management system. We export catalog schemas and item records to a product inventory spreadsheet (CSV) that the customer's admin can import into a product information management system or map to Nutshell Products (standard object) if the customer uses Nutshell Deals for product line tracking.

Iterable email engagement records (sent, opened, clicked, bounced) migrate to Nutshell Notes attached to the Contact with email event type and timestamp in the note body. The email subject and body content migrate if the content is available in the engagement record payload. Nutshell does not have a native email engagement tracking object equivalent to Iterables event stream; Notes serve as the best-available historical record.

Iterable call engagement records (disposition, duration, recording URL) migrate to Nutshell Tasks linked to the Contact, with the call outcome and duration stored in the Task description field and the recording URL stored as a custom field or note attachment. Nutshell Tasks do not have a dedicated call subtype field, so call metadata is stored in the Task description rather than a typed field.

Iterable meeting engagement records (attendees, location, start time, end time) migrate to Nutshell Tasks linked to the Contact, with meeting details stored in the Task description field. Nutshell does not have a native calendar integration for meeting tracking; the Task description carries the meeting context.