Migrate from OptiPub to Microsoft Dynamics 365 Sales

OptiPub Subscribers with lifecycle status indicating active subscriber or free-tier reader map to Dynamics 365 Contact records attached to an Account. Subscribers in an early engagement stage (new, unengaged) map to Lead records if the customer wants a formal lead qualification process in Dynamics. We preserve the original OptiPub lifecycle stage in a custom field subscriber_lifecycle_stage__c on both Lead and Contact for reporting continuity.

OptiPub dynamic Segments with membership criteria map to Dynamics 365 Marketing List membership (static) or to a custom subscriber_segment__c multi-select picklist field on Contact and Lead. Static Segments with fixed membership migrate as Campaign Members in a reference Campaign record. The customer chooses the segmentation strategy during scoping based on how the segment data is used in Dynamics reporting.

OptiPub Campaign records (subject line, content body, send date, send volume, open rate, click rate) migrate to Dynamics 365 Campaign as reference records with all available engagement metrics stored in custom fields. The Campaign does not drive CRM workflow but preserves the historical send record. A/B test variants store as separate Campaign records linked by a custom ab_parent_campaign__c reference field. Send history is preserved as a custom entity field rather than a standard Dynamics object.

OptiPub email Templates (HTML and drag-and-drop) migrate to Dynamics 365 Email Template records where the Dynamics edition supports them, or to Note records with the HTML body stored as Note Body. Template usage history across campaigns migrates as a custom field on the Campaign record. We do not migrate the template rendering engine; HTML templates are static content at the destination.

OptiPub Automation Rules use publisher-specific trigger conditions (paid publication triggers, partner funnel steps, subscriber milestone events) that have no direct equivalent in Microsoft Dynamics 365 Sales . We do not migrate Automation Rules as code. We audit every active Automation Rule, document its trigger, conditions, actions, and wait steps, and deliver a written rebuild plan mapping each rule to a Power Automate flow or Dynamics workflow with recommended trigger and action equivalents. The customer's admin rebuilds them post-migration.

OptiPub Partner records with domain monitoring, partner-level stats, and revenue attribution map to Dynamics 365 Account records with custom fields for partner_domain__c, partner_tier__c, partner_referred_subscribers__c, and partner_revenue_attribution__c. Partner Funnel step data migrates as a custom entity or related list. If the customer tracks partner-specific deals, an Opportunity custom field partner__c linking to the Account enables revenue attribution reporting.

OptiPub video integration references (Wistia or YouTube video IDs, playback statistics) migrate as a custom field video_references__c on the related Campaign or Contact record. We export play stats as static data points. Video playback at the destination requires re-authentication with the video hosting account; we flag this in the handoff document and the customer reconnects their Wistia or YouTube integration post-migration.

OptiPub Owners referenced on Subscribers, Segments, Campaigns, and Automation Rules map to Dynamics 365 User records by email match. Any OptiPub Owner without a matching Dynamics User goes to a reconciliation queue for the customer's admin to provision the User before record import resumes. Inactive OptiPub Owners map to inactive Dynamics Users to preserve the assignment history.