Migrate from Iterable to monday CRM

Iterable User Profiles map directly to Monday.com CRM Contacts. We preserve the full custom field map including email, userId, dataId, and all active custom fields. Iterable field names map to Monday.com column names during import. Deprecated Iterable fields (fields created during experimentation that are no longer in use) are flagged separately and mapped to inactive or archived Monday.com columns rather than dropped. Monday.com requires column names to match exactly during import, so we pre-create all destination columns with matching display names before data load. Subscription status per channel (email, SMS, push) migrates as separate boolean columns on the Contact record.

Iterable custom events track behavioral data beyond profile updates. Each event has a name, user identification, and arbitrary metadata payload. We map event names to Monday.com Activity board Items with columns capturing event type, timestamp, and key metadata fields. Events associated with a specific contact link via a connected Monday.com Contact column. High-volume event types (e.g., page views, clicks) are condensed into aggregate counts per user rather than individual rows to avoid exceeding Monday.com's item-per-board limits on activity boards.

Iterable Lists are named collections of User Profiles used for audience segmentation and campaign targeting. We export list names and memberships and map them to Monday.com CRM Groups within the Contacts board. Each list becomes a Group, and contact membership is represented by a Group assignment plus a status column indicating list origin. Journey triggers referencing specific lists require reconfiguration in Monday.com's Automation Center post-migration because Monday.com uses a different trigger model.

Iterable Campaigns (the sendable unit with channel type, template, schedule, and sending configuration) map to Monday.com CRM Deals. Campaign metadata including name, channel, status, and schedule migrates as Deal fields. Campaign performance metrics (open rate, click rate) are stored as custom columns on the Deal record for reporting continuity. Note that campaign template content does not migrate; we document template names and content for the admin to recreate in Monday.com integrations or third-party email tools.

Iterable Journeys define multi-step, multi-channel automation paths with trigger conditions, branching logic, and associated message actions. Monday.com CRM's Automation Center provides board-based trigger-and-action automations but does not have a direct Journey equivalent. We do not migrate Journey definitions as automation code. We deliver a written inventory of every active Journey including trigger conditions, step sequence, channel assignments, and branching logic so the customer's admin can rebuild equivalent automations in Monday.com's Automation Center or via Make/Zapier integrations.

Iterable Templates define message content for campaigns and Journey steps, supporting HTML email, plain text, and dynamic personalization via Handlebars syntax. Monday.com CRM does not have a native template management system for email or SMS content. We export template content and metadata as a structured document with template names, channel type, Handlebars field references, and content snapshots. The customer's admin assigns this inventory to a replacement email tool (e.g., Mailchimp, Klaviyo) or recreates content in Monday.com integrations.

Iterable Catalog stores product data used for dynamic content insertion in messages. We export catalog schemas and item records and map them to Monday.com custom columns on relevant boards. For complex catalog structures with multiple product attributes, we create a separate Products board in Monday.com and link items via the platform's board linking or lookup column features. Catalog-to-Journey step associations cannot migrate automatically and are flagged in the documentation deliverable for manual reconfiguration.

Iterable Purchase events record transaction data including orderId, total, items, and associated user. We map purchases to Monday.com CRM Deals with a Deals board capturing order total, order date, and item count as custom columns. For complex purchase records with multiple line items, we create subitems under the parent Deal to preserve item-level detail. OrderId maps to a custom text column for reconciliation with accounting systems post-migration.