Migrate from OptiPub to Pipedrive

OptiPub Subscribers map directly to Pipedrive People. The email address serves as the dedupe key during import. We migrate standard profile fields (name, company association, lifecycle status) and any custom subscriber properties as Pipedrive custom fields on the Person object. Publisher-specific fields like subscription tier, engagement frequency score, and partner attribution source become typed custom fields (text, number, or picklist). If OptiPub records include a partner reference, we resolve the partner-to-Organization mapping before Subscriber import.

OptiPub Segments are dynamic or static subscriber groupings with membership criteria. We export segment definitions as a reference table and map segment membership as Pipedrive Labels on People (for visual categorization) and or as a multi-select picklist field for segment-overlap tracking. Static segments become explicit label assignments; dynamic segments are documented with their criteria for reimplementation as Pipedrive filter views.

OptiPub Campaigns with send history, subject lines, open rates, and click rates have no native Pipedrive equivalent. We map each campaign to a Note attached to the relevant People (the recipients) and to an Activity record capturing send date, open rate, and click rate as custom Activity fields. For campaigns tied to a specific partner or content initiative, the Note also references the relevant Organization. The campaign content body migrates as a Note attachment or URL reference. Note that Pipedrive's Campaigns feature (Advanced plan) handles marketing contact tracking rather than email campaign history.

OptiPub automation rules use publisher-specific triggers (paid publication events, partner funnel steps, segment-change conditions) that have no structural equivalent in Pipedrive Workflow Automations. We do not migrate automation rules as code. We deliver a written inventory of every OptiPub Automation Rule covering its trigger type, conditions, actions, and timing, with a recommended Pipedrive Workflow equivalent for each. The customer's admin rebuilds the automations post-migration using Pipedrive's Automation feature on the Advanced plan or above.

OptiPub email templates (drag-and-drop or HTML) have no direct Pipedrive equivalent at the Essential or Advanced tiers. We export template assets and metadata as a written inventory with HTML content preserved in a reference document. Pipedrive Professional plan includes an email template feature; teams on Professional can rebuild templates using the built-in editor or import HTML templates. We flag template rebuild as a post-migration task in the handoff document.

OptiPub Partner records (affiliate and partner management with domain monitoring and partner-level revenue attribution) map to Pipedrive Organizations. Partner-level stats (revenue, attribution, domain) migrate as custom fields on the Organization. If partners are individual contacts (not companies), they map to People with the Organization relationship established via the Organization Lookup field. Partner domain monitoring is not a Pipedrive native feature; we document it as a post-migration integration consideration.

OptiPub engagement events (email opens, link clicks, unsubscribe events) have no native Pipedrive equivalent as a marketing timeline. We transform engagement data into Activity records: a send activity logged against each recipient Person, with open and click counts stored as custom number fields on the Activity. Unsubscribe events become Activity records with an unsubscribe flag custom field on the Person. Engagement aggregation metrics (campaign-level open rate, click rate) migrate as Note attachments on the relevant campaign Activity.

OptiPub campaigns embedding Wistia or YouTube videos store integration credentials and playback statistics. We export play statistics as static custom fields on the Person record (video_title, play_count, last_played_date). Video hosting integrations cannot transfer; we document the video assets and their playback links for re-authentication and re-embedding in the customer's new email marketing system (Pipedrive does not support embedded video in emails natively).

OptiPub subscriber records may carry publisher-specific custom properties beyond standard profile fields. We migrate these as Pipedrive custom fields on the Person object. Pipedrive requires custom fields to be pre-created in the destination account before any import maps to them; we coordinate field creation with the customer during the schema design phase. Field type mapping follows: text properties to text fields, numeric properties to number fields, date properties to date fields, and list properties to picklist or multi-select picklist fields.

OptiPub subscriber subscription metadata (plan name, start date, renewal date, payment status) maps to custom fields on the Pipedrive Person. Plan name becomes a picklist field, start and renewal dates become date fields, and payment status becomes a picklist or text field. If the publishing operation sells subscriptions as Deals, the subscription metadata also appears on the relevant Deal as custom fields with a person-to-deal lookup established during migration.