Migrate from Iterable to Pipedrive

Iterable user profiles map directly to Pipedrive Persons. The Iterable email field maps to Pipedrive's primary email on Person; dataId maps as an external reference in a custom field itbl_data_id__c for cross-system audit. Iterables system fields (signupSource, itblCreatedAt, itblUpdatedAt, deviceType) map to custom Person fields typed as text, date, or picklist respectively. Custom profile fields on Iterable migrate as custom Person fields in Pipedrive. We validate email format during import because Pipedrive API v2 enforces stricter input validation than Iterable's extraction API.

Iterable list memberships represent audience segments used for campaign targeting. We extract all list memberships per user and store them as comma-separated segment tags in a custom Person field iterabl_list_memberships__c. If the customer uses lists as hard segment gates rather than tags, we recommend creating Pipedrive Activities or Notes attached to each Person to document the membership history. Iterables dynamic list logic cannot be replicated in Pipedrive without manual rebuild.

Iterable custom events store behavioral data (purchase, pageview, feature_used, upgrade) with arbitrary metadata payloads. Pipedrive has no native event tracking object. We create one Activity Note per significant event type per Person, with the event name as the note title and event metadata serialized into the note body as structured text. For high-frequency events (pageviews, session events), we aggregate counts by event type and store a summary value in a custom Person field rather than individual notes. The customer receives a written event catalog documenting every event type migrated so they can decide which events warrant CRM-level activity logging.

Iterable purchase events contain orderId, total, items, and user reference. If the customer has deal-level data (which Iterable does not natively structure as Deals), we create Pipedrive Deals from the most recent purchase event per user, set the Deal value to the purchase total, and attach the full purchase item list as a Deal Note. For historical purchase tracking, we create Activity Notes on the corresponding Person with order details. We flag this as a configuration decision during scoping because Pipedrive Deals without a sales process do not automatically populate; the customer defines the pipeline and stages first.

Iterable stores per-channel subscription status (emailSubscribed, smsSubscribed, pushSubscribed, inAppSubscribed) on each user profile. We map these to custom Person checkbox fields iterabl_email_opt_in__c, iterabl_sms_opt_in__c, and iterabl_push_opt_in__c. Unsubscribes migrate as false values on the corresponding field, preserving the suppression logic so Pipedrive users do not accidentally re-market to unsubscribed contacts.

Iterable user profiles may contain a companyName or extracted from email domain. We create Pipedrive Organizations from unique company names and domain values, then perform a lookup-link to associate each Person with their Organization by domain match. If Iterables profile schema includes a separate Company object, we use that as the Organization source-of-truth. Organization-level custom fields migrate as Organization custom fields in Pipedrive.

Iterable Campaign records carry metadata (name, channel, send time, status, subject line). We create one Activity Note per Campaign on each Person who received that campaign, documenting the campaign name, send timestamp, and any available engagement signal (opened, clicked). Campaign send definitions, templates, and Journey trigger logic do not migrate; we export campaign metadata as a CSV for the customer to use when rebuilding campaign records in Pipedrive or a separate marketing platform.

Iterable Catalog stores product data for dynamic content insertion. If the customer uses Catalog items as a product catalog (rather than just personalization data), we map Catalog Items to Pipedrive Products with name, SKU (catalogId), and any numeric fields (price, stock) mapped to Product fields. Note that Pipedrive Products are not directly linked to Deals in the same way Iterable Catalog items link to message templates; the customer rebuilds any Catalog-to-Campaign associations manually.

Iterable Journeys are multi-step, multi-channel automation workflows with branching logic, wait delays, and conditional paths. Pipedrive has no equivalent automation engine for marketing or lifecycle automation. Journeys do not migrate as functional objects. We export Journey metadata (name, trigger conditions, step count, channel sequence) as a written inventory document for the customer to review. The customer rebuilds Journey logic in Pipedrive's workflow automation or in a dedicated marketing automation tool (Klaviyo, Braze, or a CDP).

Iterable Templates define message content for email, SMS, push, and in-app channels using Handlebars personalization syntax. Pipedrive does not have a message template library for outbound marketing. We export template content (HTML, subject lines, dynamic fields) as a structured JSON export for the customer's design team to port into their chosen marketing platform. Template-to-Journey associations are documented in the Journey inventory.