Migrate from Iterable to Zoho CRM

Iterable User Profiles with email, phone, and behavioral data map to Zoho Leads for prospects and Contacts for qualified buyers. We use Iterables subscription status, last engaged date, and custom lifecycle stage fields to determine the split: subscribed prospects with no purchase history go to Zoho Lead; users with purchase events or subscription-paid status go to Zoho Contact attached to an Account. The original Iterable dataId and email hash migrate to custom fields iter_data_id__c and iter_email_hash__c for reconciliation.

Iterable does not have a native Company object but Company data stored within User Profile fields (company name, domain, industry) extracts to Zoho Account records. The Account Name maps from the company field; domain extracts to the Website field. Account is created before any Contact or Lead import so that the Account-Contact lookup relationship is satisfied at insert time.

Iterable Custom Events carry behavioral data (event name, timestamp, user identification, arbitrary metadata). Zoho CRM has no native equivalent for arbitrary event payloads. We transform each event name and its key metadata into Zoho Task records with custom fields capturing event_name__c, event_timestamp__c, and serialized JSON payload in event_data__c for reporting queries. The Task links to the corresponding Lead or Contact via WhoId. Events without a matching user go to a dead-letter queue.

Iterable Lists are audience segments used for campaign targeting. We map list memberships as Zoho CRM Tags on Lead and Contact records (using Zohos native tagging feature). List names preserve as tag values prefixed with iter_list_. For lists used as suppression audiences, we set HasOptedOutOfEmail = true on the corresponding Zoho records. If the customer uses lists as static audience groups rather than tags, we can create a custom module for list management during migration scoping.

Iterable Campaigns (email, SMS, push) with metadata (name, channel, status, schedule, template reference) map to Zoho CRM Campaigns. Campaign type from Iterable maps to Zoho Campaign Type; campaign ID preserves in custom field iter_campaign_id__c. Note that Zoho Campaigns track marketing campaign performance but do not execute sends natively. The customer's admin configures the send mechanism post-migration using Zoho Email Templates and mass email actions.

Iterable Templates (HTML email, plain text, dynamic personalization via Handlebars syntax) export as content files with metadata. We import the template content into Zoho CRM Email Templates, preserving HTML structure and Handlebars-style placeholders where the Zoho template syntax supports them. Where Handlebars syntax is incompatible, we document the personalization tokens for the admin to re-implement using Zohos merge field syntax.

Iterable Catalog items (product data for dynamic content insertion) map to Zoho CRM Products. The catalog schema fields map to Product fields: name, SKU (from catalog item id), price, description, and custom fields. Inventory quantities map to the Quantity field. We preserve catalog-to-Journey associations in a custom field iter_catalog_journey__c so the admin can relink after rebuilding Journeys in Zoho Workflows.

Iterable Purchase events (orderId, total, items, associated user) map to Zoho CRM Potentials when the customer uses Zoho for sales pipeline tracking. The purchase total maps to Potential Amount; purchase date maps to Closing Date; orderId maps to a custom field iter_order_id__c. Line items from the purchase attach to the Potential via Products linkage. If the customer does not use Zoho Deals, purchases migrate as custom fields on the Contact record.

Iterable subscription status tracks opt-in and opt-out per channel (email, SMS, push). We map each channel status to Zoho CRM Contact-level fields: Email Opt-out (HasOptedOutOfEmail), SMS Opt-out, and Push Opt-out as custom Boolean fields with iter_email_subscription__c, iter_sms_subscription__c, and iter_push_subscription__c storing the original Iterable values. Subscription event history migrates as Task records for audit trail.

Iterables system fields (dataId, email, userId, createdAt, updatedAt, itery_user_id) map to Zoho standard fields: Email Address maps directly; dataId preserves in iter_data_id__c; createdAt maps to Created Time. Custom profile fields on Iterable map to Zoho custom fields of matching type (string to text, number to big integer, date to date picker, boolean to checkbox). We validate type compatibility during schema design before field creation.

Iterables Journey definitions (multi-step, multi-channel automation paths with branching logic and AI decisioning) have no direct Zoho CRM equivalent. We export Journey metadata including trigger conditions, branching paths, associated templates, and wait-action configurations. This becomes a written inventory document delivered to the customer for manual rebuild in Zoho Workflows and Blueprint. We do not execute Journey logic during migration.

Iterable Data Sync is a warehouse export feature gated behind Customer Success requiring IP allowlisting. If the customer has active Data Sync records, we export the most recent snapshot but note that Data Sync requires CSM coordination to access and cannot be automated as a standard migration step. We recommend the customer export full Data Sync history before initiating the migration window.