Migrate from Naviga to Twenty CRM

Naviga Publications (top-level organizational units representing news titles or media brands) map directly to Twenty Company records. The publication name becomes Company.displayName, edition types (digital, print, broadcast) map to custom select fields, and the publication's domain or URL becomes the Website field. We preserve the hierarchical relationship between Publications and their constituent content by storing a parent_company__c self-lookup if the customer has multi-publication structures.

Naviga Subscribers (paying or free readers with account status, subscription type, and billing history) map to Twenty People records. Contact details, subscription tier, account status, and billing history migrate as typed fields. We preserve the subscriber's link to their Publication via a lookup to the mapped Company record.

Naviga Audience Members (broader reader population including non-subscribers tracked for engagement) map to Twenty People records. Behavioral data and segmentation tags migrate to custom fields or Twenty's built-in tags. We deduplicate against existing Subscriber People records using email as the unique key.

Naviga Solicitors (field sales representatives managing subscriber acquisition) map to Twenty User records. We resolve by email match. Any Solicitor without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision the User before record import. Solicitor performance metrics (acquisition count, renewal rate) from Offer Groups migrate to custom fields on the User record.

Naviga Offer Groups bundle pricing structures and special offers for acquisition campaigns. We create a custom object in Twenty called AcquisitionCampaign__c (or use Opportunity if the customer tracks these as sales deals) with fields for offer_name, pricing_structure, campaign_start, campaign_end, and solicitor_id. The Solicitor-to-Subscriber relationship reconstructs here: we create AcquisitionCampaignMember__c records linking each acquisition campaign to the People record it acquired. The customer chooses between Opportunity and custom object during scoping based on their reporting needs.

Naviga Articles include authored text, metadata, and linked photos. Twenty CRM has no native Articles object, so we split article content across Task records (for activity-logged content like press releases or campaign coverage) and Note records (for reference content). Article body migrates as the Task description or Note body; author becomes the assigned Twenty User; publish date becomes ActivityDate. We flag Articles that represent editorial calendar entries as candidates for a custom Article__c object if the customer requires deeper content management.

Naviga Ad manages ad campaigns across print, digital, and broadcast channels. We create a custom object Advertisement__c in Twenty with fields for campaign_name, channel (print/digital/broadcast), advertiser_name, order_number, start_date, end_date, and status. Creative assets migrate as ContentDocument records linked via ContentDocumentLink to the Advertisement__c record.

Naviga Photos stores media assets with XMP, IPTC, and EXIF metadata. Custom metadata fields vary by installation. We export photos with their standard metadata as ContentDocument records. Custom metadata fields migrate to custom fields on the ContentDocument or a linked custom object depending on field count and type. Standard EXIF data (date taken, camera, GPS) maps to ContentDocument fields where Twenty supports them.

Naviga Photos allows per-installation custom metadata schemas with unique labels, field types, and required flags. We perform schema discovery on the source environment before mapping. Custom fields that map cleanly to Twenty field types (text, number, date, checkbox, select) migrate as custom fields on the relevant Twenty object. Fields using Naviga-specific picklist values migrate as custom picklists in Twenty.

Naviga Publisher's Sophi.io-powered print manufacturing workflows generate InDesign blueprints, page layouts, and print PDFs that live in a proprietary production system outside the Open Content repository. We flag Print Edition records during scoping and exclude them from CRM migration scope, notifying the customer that these assets require a separate print-to-print migration workflow or a dedicated digital asset management platform.