Migrate from OptiPub to Freshsales

OptiPub Subscribers map to Freshsales Contacts. The subscriber email address becomes the Contact email and acts as the dedupe key. Lifecycle status from OptiPub migrates to a custom Contact field subscriber_lifecycle_stage__c. Custom subscriber properties (profile fields, subscription tier, engagement scores) map to Freshsales custom Contact fields of matching type (text, number, date, picklist). We pre-create any missing custom fields in Freshsales before the Contact import phase begins.

Subscribers who have not been qualified into a sales process map to Freshsales Lead records, while those with revenue intent or partner attribution map to Contact under an Account. We define the split rule during scoping based on OptiPub subscriber properties (engagement tier, partner status, paid publication flags). Subscribers with no engagement history default to Lead; those with click or conversion activity default to Contact.

OptiPub dynamic and static Segments map to Freshsales Contact filter views and saved Lists. We capture each segment's membership criteria as a Freshsales filter definition and replicate current membership by creating a Freshsales List for each OptiPub Segment with members added via Bulk API. Segment-to-campaign associations document separately as a configuration note for the customer's admin to reconnect post-migration.

OptiPub email campaigns (subject, body, send date, A/B variants) have no direct Freshsales CRM equivalent because Freshsales does not include native email campaign management. We migrate campaign metadata as Activity records (type=Email) linked to the Contact, with campaign name, subject line, and send date preserved in custom Task fields. A/B test variant data migrates as separate Activity records with variant labels. The customer's admin rebuilds campaign execution logic in Freshsales Workflows or in a dedicated email platform.

OptiPub Partner records (affiliate and partner management with domain monitoring and revenue attribution) map to Freshsales Account records. Partner-level stats (clicks, conversions, revenue share) migrate to custom Account fields (partner_clicks__c, partner_conversions__c, partner_revenue_share__c). Partner domain data maps to Account Website and Industry fields where applicable.

OptiPub email templates (drag-and-drop and HTML) migrate as Freshsales Document records or file attachments linked to the relevant Contact or Account. We export template HTML as a Document with a reference to its original campaign usage. Templates do not migrate as editable Freshsales templates because Freshsales does not include an email template builder at the same level as OptiPub.

OptiPub video references (Wistia and YouTube playback URLs, play statistics) migrate as Freshsales Note records linked to the Contact or Account, with the video URL stored in a custom URL field (video_playback_url__c) and play count stored in a custom number field (video_play_count__c). The video hosting connection does not migrate; re-authentication of the Wistia or YouTube integration at Freshsales is a post-migration admin task.

OptiPub Automation Rules (workflow triggers, conditional logic, paid publication triggers, partner funnel steps) are documented but not migrated as code. Freshsales Workflows use record-triggered and scheduled variants with different action types and limits. We deliver a written inventory of every active OptiPub Automation Rule with its trigger conditions, action sequence, and recommended Freshsales Workflow equivalent for the customer's admin to rebuild.

OptiPub engagement events (email opens, clicks, bounces, unsubscribes) migrate to Freshsales as Task records with custom engagement type fields (engagement_event_type__c, eng_open_count__c, eng_click_count__c) and EmailMessage records where applicable. Historical engagement data preserves the timeline by setting Task ActivityDate to the original OptiPub event timestamp. Bounce and unsubscribe flags migrate to Freshsales Contact fields (email_bounced__c, unsubscribed__c).