Migrate from Naviga to Mailchimp

Naviga Subscribers map directly to Mailchimp Contacts. We preserve email address, first name, last name, subscription status (active/inactive/expired), subscription type, start date, and billing history fields as Mailchimp subscriber custom fields. Opt-in status migrates to Mailchimp's subscribed/unsubscribed/bounced/changed state. The migration dedupes by email address before import to prevent duplicate contact charges under Mailchimp's contact-count pricing model.

Naviga Audience Members representing the broader non-subscriber reader population migrate to Mailchimp Contacts in a separate audience segment. Behavioral data and segmentation tags from Naviga Audience migrate as Mailchimp Tags and custom fields. Engagement scores or behavioral flags from Naviga are stored as numeric or date custom fields in Mailchimp for segmentation use post-migration.

Each Naviga Publication maps to a Mailchimp Audience, preserving the publication name as the audience name. For publishers operating multiple news titles or media brands, each Naviga Publication becomes a separate Mailchimp Audience, keeping subscriber lists isolated by brand. We import subscribers into their corresponding brand audience rather than collapsing all contacts into a single Mailchimp account.

Naviga Solicitors are field sales representatives who manage subscriber acquisition linked through Offer Groups rather than a direct many-to-many relationship. Mailchimp has no native User or Rep object. We reconstruct solicitor attribution by tagging migrated Contacts with the solicitor name or ID as a Mailchimp Tag (e.g., Tag: Solicitor_JSmith) and storing the solicitor's full name and ID in a custom field for reporting. This preserves acquisition attribution within Mailchimp's tag-based segmentation.

Naviga Photos and Subscriber configurations may include custom metadata fields with custom labels and types per installation. We detect the custom field schema during discovery, map each to the corresponding Mailchimp subscriber field type (text, number, date, checkbox, or dropdown), and flag any fields with data types that exceed Mailchimp's 30-custom-field-per-audience limit. Fields that cannot map (e.g., multi-select arrays or nested metadata) are stored as JSON text in a fallback custom field or documented for manual entry.

Naviga Ad manages ad campaigns across print, digital, and broadcast channels with order management and production workflows. Mailchimp has no advertising, display, or print ad object. We exclude Advertisements from the migration scope, document the full ad campaign record inventory in the handoff report, and recommend the customer evaluate Mailchimp's ad management integrations (if applicable) or a dedicated ad platform for rebuild.

Naviga Offer Groups bundle pricing structures and special offers tied to subscription acquisition campaigns. Mailchimp has no pricing or offer management object. We exclude Offer Groups from the migration scope. Subscriber billing tiers can be reconstructed as Mailchimp Tags (e.g., Tag: Offer_Annual, Tag: Offer_Trial) or as custom fields referencing the offer name, but the full Offer Group hierarchy requires manual rebuild in Mailchimp's automation and tagging strategy.

Print edition artifacts including InDesign blueprints, page layouts, and automated print templates generated by Naviga Publisher's Sophi.io-powered manufacturing system are not accessible via Naviga's Open Content API and have no Mailchimp equivalent. We exclude Print Editions from the migration scope and flag them as requiring a separate print-to-print migration workflow. This is documented in the handoff report with a recommendation to engage a print-specific migration service.

Naviga Articles contain authored text, metadata, and linked photos. Mailchimp has no article management object. Long-form content that was distributed as email newsletters can be reconstructed as Mailchimp Campaigns or saved as Templates in the Mailchimp builder. We export article titles, author names, and publish dates as a reference document. The article body requires manual copy-paste into Mailchimp's template editor or content block structure.