Migrate from OptiPub to HighLevel

OptiPub Subscriber records migrate to GoHighLevel Contact as the primary record. Email address becomes the Contact Email field and the dedupe key. OptiPub lifecycle status, subscription preferences, and custom profile properties migrate to GoHighLevel custom fields. Engagement metrics (last open date, last click date, total opens, total clicks) migrate as custom numeric fields on the Contact. Subscription opt-in status maps to GoHighLevel's Email Opt Out field for deliverability compliance at the destination.

OptiPub Segments (dynamic or static subscriber groupings) translate to GoHighLevel Smart Lists with equivalent filter conditions, or to Tag assignments applied to each Contact member. Static segments become bulk Tag operations during migration. Dynamic segments with complex nested criteria (AND/OR logic across multiple properties) require configuration review because GoHighLevel Smart List conditions may not express every OptiPub segment operator 1:1. We document any non-mappable segment conditions for admin-level rebuild in GoHighLevel.

OptiPub Campaign records (subject line, send date, send count, open rate, click rate, bounce count) migrate as GoHighLevel Campaign records for historical reference. Engagement data (opens, clicks, unsubscribes) attaches as Activity records linked to the recipient Contact. A/B test variants from OptiPub migrate as separate Campaign records with a naming convention identifying the parent test. Note that OptiPub campaign content bodies migrate as static HTML blobs stored in a custom long-text field; they do not become GoHighLevel campaign email templates.

OptiPub drag-and-drop and HTML email templates migrate as GoHighLevel Email Templates. Template metadata (name, usage count, last modified date) carries over. HTML templates render as GoHighLevel HTML snippets; drag-and-drop templates require reconstruction in GoHighLevel's template builder unless the original HTML is self-contained. We preserve the original HTML as a fallback asset in a custom Template HTML field.

OptiPub Automation Rules with publisher-specific triggers (paid publication triggers, partner funnel steps) cannot migrate as functional Workflows because the trigger events do not exist in GoHighLevel. We extract every Automation Rule structure and produce a written mapping document listing each rule's trigger, conditions, actions, and recommended GoHighLevel Workflow equivalent. The customer's admin rebuilds the Workflows in GoHighLevel's visual builder; this is out of scope for standard data migration.

OptiPub Partners (affiliate and partner management records with domain monitoring and partner-level stats) migrate to a GoHighLevel Partner Custom Object with the partner-level metrics preserved. Partner-to-subscriber relationships (if the partner is also a subscriber) create a Contact record with a lookup to the Partner Custom Object. Revenue attribution fields migrate to custom currency fields on the Partner object. We pre-create the Partner custom object schema before migration begins.

OptiPub embedded video assets (Wistia, YouTube references) carry over as URL strings in custom text fields on the associated Campaign or Contact. Video playback within GoHighLevel emails depends on the destination platform's video embedding support. We document the original video hosting connection (Wistia account, YouTube channel) so the customer's admin can re-link the video integration in GoHighLevel's email builder. Play statistics migrate as static numeric data points.

OptiPub engagement records (send events, open events, click events, bounce events, unsubscribe events) migrate as GoHighLevel Activity records (Task or Log Note type) linked to the corresponding Contact. Each event type maps to a distinct Activity category field so the timeline is readable. Engagement timestamps preserve the original OptiPub timestamp for accurate historical reporting. Large engagement histories (over 50,000 events) require GoHighLevel API batching with rate-limit handling and parent-record lookup resolution before each Activity insert.