Migrate from OptiPub to Salesforce Sales Cloud

OptiPub Subscribers with no purchase history or early engagement lifecycle stage (subscribed, trial) map to Salesforce Lead. Subscribers with paid publication status, active subscription, or partner affiliate designation map to Salesforce Contact tied to an Account. We compute the split at migration time using OptiPub's lifecycle stage and subscription_type properties, and preserve the original OptiPub status in a custom field optipub_lifecycle__c on both Lead and Contact for audit. Subscriber email address becomes Email on Contact or Email on Lead. Custom subscriber properties migrate as Salesforce custom fields with equivalent data types.

OptiPub Segments (dynamic or static subscriber groupings) map to Salesforce Campaign records with the segment name as Campaign Name. Static segment membership migrates as Campaign Member records linked to the Salesforce Contact or Lead. Dynamic segment definitions (criteria-based membership) cannot replicate in Salesforce without rebuild as Salesforce Reports with filters; we document each dynamic segment's criteria for the customer's admin to reconstruct as a Salesforce Report or Campaign-based segmentation strategy.

OptiPub Campaign records (subject line, content body, scheduling metadata, send history) map to Salesforce Campaign. The campaign type in Salesforce is set to Email based on the OptiPub source. A/B test variants and subject line test results migrate as Salesforce Campaign Custom Fields capturing test_name, variant, open_rate, and click_rate as numeric fields. Historical send-frequency and cadence data migrate as campaign custom fields for reporting continuity.

OptiPub Partner records (domain monitoring, partner-level stats, revenue attribution) map to Salesforce Account with Account Type set to Partner for organizations tracking partner data without a custom schema. Publishers with complex partner revenue attribution (commission tracking, partner-tier discounts, affiliate funnel attribution) require a custom Partner object in Salesforce with fields for partner_tier__c, commission_rate__c, and affiliate_revenue__c. We design the custom Partner schema during scoping based on the OptiPub partner data fields present in the source export.

OptiPub Automation Rules use publisher-specific trigger conditions (paid publication triggers, partner funnel steps, segment-based delays, publication-date-based sends) that do not map to Salesforce Flow action types. We do not migrate Automation Rules as code. We deliver a written inventory of every active Automation Rule with its trigger condition, branching logic, delay steps, and action sequence. Each rule in the inventory includes a recommended Salesforce Flow equivalent (record-triggered Flow for lead-based triggers, scheduled Flow for date-based triggers) so the customer's admin or a Salesforce partner can rebuild them post-migration.

OptiPub drag-and-drop and HTML email templates migrate as Salesforce Classic Email Templates or Salesforce Content Workspace assets depending on the destination org's template strategy. We export template HTML and metadata including usage history across campaigns. Templates that use OptiPub-specific merge tags (subscriber.first_name, segment.name) require field mapping to Salesforce merge field equivalents ({!Contact.FirstName}, {!Campaign.Name}) before use. The customer's admin tests each migrated template in Salesforce before activating.

OptiPub video assets (Wistia, YouTube) store integration credentials and per-subscriber play statistics. We export play stats (video title, total plays, last played date, completion rate) as Salesforce custom fields on the Contact or Lead record. The video hosting connection (Wistia API key, YouTube channel ID) does not migrate; the customer's admin must re-authenticate video hosting accounts in the destination platform. Video playback within Salesforce email templates depends on the destination's video embedding support.

OptiPub send history (which subscriber received which campaign, delivery status, open timestamp, click timestamp, bounce reason) migrates to Salesforce Campaign Member records. Each send record creates a Campaign Member linked to the Contact or Lead and the corresponding Campaign. Open rate, click rate, and bounce reason migrate as Campaign Member custom fields for reporting continuity.

OptiPub paid publication records (if present as a custom data type) migrate to a Salesforce custom object named Paid_Publication__c with fields for publication_name, publish_date, revenue_amount, subscriber_segment, and partner_attribution. We pre-create the custom object schema during discovery based on the OptiPub data export, including any lookup relationships to Account (for partner attribution) and Contact (for subscriber segment).

OptiPub subscription records (subscription tier, billing frequency, start date, renewal date, MRR) map to Salesforce Opportunity if the subscription renewal process follows a sales-cycle model (new, upsell, renewal). If the customer manages subscriptions in a separate billing system and uses Salesforce only for account tracking, subscription metadata migrates as custom fields on Account or as a Subscription__c custom object with lookup to Account.

OptiPub Owners (user records associated with campaigns, segments, partners) map to Salesforce User by email match. Any OptiPub Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner-level permissions and territory assignments require separate configuration in Salesforce after migration.

OptiPub subscriber engagement events (email opens, link clicks, page views tracked within OptiPub) migrate as Salesforce Task records linked to the Contact or Lead. Each activity record captures activity_type (open, click, page_view), campaign_reference, and timestamp. High-volume engagement data (hundreds of thousands of records) uses the Salesforce Bulk API 2.0 with chunking and parent-record lookup resolution to avoid API timeouts.