Migrate from OptiPub to Nutshell

OptiPub Subscribers map to Nutshell Person records as the primary mapping. Subscribers with a lifecycle status of unengaged or bounced map to Nutshell Lead if the customer wants to keep them separate from active sales contacts. Email address is the dedupe key. All OptiPub custom properties (engagement frequency, subscription tier, source channel) migrate to Nutshell custom fields on Person or Lead. Nutshell Enterprise supports unlimited custom fields; Foundation is limited to a smaller set, so custom property count determines the minimum required tier.

OptiPub Segments (dynamic or static subscriber groupings) do not have a direct Nutshell equivalent. We migrate segment membership as a tag string in a Nutshell custom field (e.g., segment_name: 'Premium_Readers' stored as a tag or text field). For static segments, we create Nutshell People Lists manually or via CSV import after the migration. Dynamic segment logic (membership criteria that update over time) cannot be replicated in Nutshell without manual list maintenance; we document the original segment criteria for the customer's admin to use when rebuilding lists.

OptiPub email Campaigns with send history, subject lines, and engagement metrics (opens, clicks, bounces) do not map to any native Nutshell object because Nutshell is a CRM, not an email marketing platform. We export campaign metadata (name, send date, subject line, send count, open rate, click rate) as a CSV-formatted custom report and attach it to the Nutshell Account or Person records as a static reference. The customer uses this as a historical record; active campaign tracking requires a separate email marketing tool post-migration.

OptiPub Partners (affiliate and partner management records with domain monitoring and partner-level stats) map to Nutshell Account. Partner-level revenue attribution fields migrate to Account custom fields. Domain monitoring data does not have a Nutshell equivalent and is documented as a custom field or exported to a separate reference document. Account Name is set to the partner domain or company name from OptiPub.

OptiPub drag-and-drop and HTML email templates migrate as HTML asset files preserved in a migration package. Nutshell supports email templates (Pro+ tier) but does not import external HTML templates directly. We deliver the template HTML files and document the recommended rebuild steps in Nutshell's template editor. Template usage history (campaign associations) is documented as a reference for the customer's admin.

OptiPub video integration references (embedded Wistia or YouTube videos in campaigns) preserve video IDs and playback statistics as static data in custom fields. Video hosting connections do not migrate; the customer re-links video accounts at the destination. Play statistics are exported as CSV data points for historical reference but do not become native Nutshell records.

OptiPub Automation Rules with publishing-specific triggers (paid publication triggers, partner funnel steps, engagement-based conditions) do not map to Nutshell sequences or automation. We deliver a written inventory of every OptiPub Automation Rule with its trigger logic, conditions, actions, and delays, mapped to a recommended Nutshell Email Sequence structure or a task-based workflow that the customer's admin rebuilds manually. Automation branching logic that relies on publisher-specific events (publication send events) has no Nutshell equivalent and is flagged as requiring process redesign.

OptiPub engagement events (email opens, link clicks, bounce records) are aggregated at the subscriber level and migrate as custom fields on the Nutshell Person record (last_open_date, last_click_date, total_opens, total_clicks, bounce_status). Individual engagement event records do not migrate as separate Nutshell activities because they lack a native storage equivalent and would exceed the activity model for a CRM use case. Aggregate metrics provide the reporting continuity needed for subscriber health scoring.