Migrate from OptiPub to Twenty CRM

OptiPub Subscribers map to Twenty People records. We extract email address, engagement history fields (last_open_date, last_click_date, total_sends), lifecycle status (active, unsubscribed, bounced), and any custom subscriber properties. The subscriber's subscription status becomes a custom picklist field on People. If OptiPub tracks subscriber source attribution, we map it to a custom text or picklist field in Twenty. The People record is created first so that any subsequent segment, campaign, or activity references can resolve the lookup.

OptiPub Segments (dynamic or static subscriber groupings) map to Twenty Tags attached to People records. For segments with complex membership criteria (behavioral triggers, date-based rules), we document the segment definition and recommend rebuilding as a Twenty filter view rather than static tags, since Twenty does not have a native dynamic segment equivalent. If OptiPub segments are small in number (under 20) and used for campaign targeting, we create a custom multi-select picklist field (segment_name__c) on People to preserve the segment label. Segment-to-campaign associations migrate as Note records describing the campaign targeting rule.

OptiPub Campaigns (with subject, content body, send date, A/B test variants, and engagement metrics) do not have a direct Twenty CRM equivalent. We create a Note record for each campaign, attach it to the relevant People records, and populate the Note body with campaign subject, send timestamp, open rate, click rate, and A/B test variant details. If the campaign was sent to a known segment, the segment membership Note serves as the campaign targeting record. Customers needing campaign reporting in Twenty should plan for a custom Campaign object built in Settings -> Data Model before migration.

OptiPub email templates (drag-and-drop or HTML) migrate as Note records attached to the originating admin's workspace. We preserve the template name, HTML source, and last-used date. The template HTML does not become a live asset in Twenty (Twenty has no native email template builder in the base CRM); the Note serves as an archive and reference for rebuilding in the customer's chosen email delivery tool post-migration.

OptiPub Automation Rules with publisher-specific triggers (paid publication triggers, partner funnel steps, engagement-based sequences) do not map to Twenty Workflows because the trigger conditions and branching logic are structurally different. We do not migrate automation rules as code. We deliver a written inventory of every active OptiPub automation with its trigger, conditions, actions, and recommended Twenty Workflow equivalent, including the specific record-triggered or scheduled flow variant that matches the use case. The customer's admin rebuilds them post-migration.

OptiPub Partners (affiliate and partner management records with domain monitoring and partner-level stats) map to Twenty Companies with custom fields. We create a custom object or custom fields on Company for partner-specific metrics: partner_revenue__c, domain__c, partner_tier__c, and referral_source__c. Partner funnel step status becomes a custom picklist field. Partner-to-subscriber relationships (if tracked in OptiPub) map to Twenty's standard link between Company and People records.

OptiPub campaigns embedding Wistia or YouTube videos store integration credentials and play statistics. We export play statistics as static data points in a Note attached to the relevant campaign record. The video URL itself migrates as a text field; playback within emails depends on the customer's chosen email delivery tool, not Twenty CRM. Video hosting credentials require re-authentication at the destination email tool.

OptiPub engagement events (opens, clicks, unsubscribes) map to Twenty Task records attached to the relevant People record. We preserve the engagement timestamp, event type, and campaign reference. The engagement count summary (lifetime opens, lifetime clicks) migrates as custom number fields on the People record. This gives sales and editorial teams a view of subscriber engagement history within the CRM without a native campaign object.

OptiPub's custom subscriber properties (publisher-specific fields beyond the standard schema) map to Twenty custom fields on People. We create these fields in Settings -> Data Model before migration. Field type mapping follows: text to TEXT, number to NUMBER, date to DATE, true/false to CHECKBOX, and dropdown values to SELECT. If a custom property references another object (e.g., a linked partner), we create the corresponding lookup relationship in Twenty first.

OptiPub Owner records (user assignments on subscribers, campaigns, and automations) map to Twenty User records. We resolve owners by email match against the Twenty workspace. Any OptiPub owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Twenty requires users to accept their invitation before Owner lookups can resolve, per Twenty's documentation.