Migrate from Naviga to Nutshell

Naviga Publications represent news titles or media brands and map to Nutshell Company records. We preserve the publication name, edition types (digital, print), and URL. Publication serves as the top-level organizational container for the migrated dataset. If the customer operates multiple publications, each becomes a separate Company record with its own subscriber and solicitor rollup.

Naviga Subscribers represent paying or free readers with account status, subscription type, and billing history. We migrate Subscriber records to Nutshell Person with contact details, subscription tier stored as a custom field, and billing status preserved. Account status and renewal date migrate as custom fields if Nutshell's native Person fields are insufficient. Subscribers with an active subscription map to a Person with a corresponding tag.

Naviga Audience Members represent non-subscribing readers tracked for engagement. We merge Audience Members with Subscribers by email deduplication: if an email exists in both, the Person record retains Subscriber-level fields (subscription tier, billing) and Audience-level behavioral data as additional custom fields. Audience Members without a matching Subscriber create a new Person with a source tag indicating original Audience Member provenance.

Naviga Solicitors are field sales reps who manage subscriber acquisition. We map Solicitors to inactive Nutshell Users to preserve who was assigned to which subscriber without creating active user seats the customer does not need. The solicitor's name, ID, and contact info migrate to the User record. Active solicitor assignments (who acquired which subscriber) are preserved via the Offer Group linkage documented separately.

Naviga Offer Groups bundle pricing structures and special offers for acquisition campaigns. Since Nutshell does not have a native Offer Group object, we map Offer Group names to custom fields on the Person record (offer_group_name__c, offer_group_type__c) and create corresponding Tags in Nutshell. For customers with complex multi-tier pricing, we recommend a Custom Object for Offer Groups with a lookup to Person.

Naviga Articles include authored text, author metadata, publish date, and linked photos. We map Articles to Nutshell Notes attached to the relevant Person or Company (if the article references a subscriber or publication contact). The Note body carries the article title and author, with publish date stored as a custom Note field or embedded in the Note title. Articles are informational artifacts, not CRM activities, so this mapping preserves the reference without inflating activity counts.

Naviga Ad manages ad campaigns across print, digital, and broadcast channels. We map ad campaign records to Nutshell Deals in a dedicated Advertisements pipeline so that sales teams can track ad revenue alongside subscriber acquisition. For display advertising with line-item pricing, we recommend a Custom Object for Ad Campaigns with a lookup to Person or Company for advertiser attribution.

Naviga Photos stores media assets with XMP, IPTC, and EXIF metadata. Custom metadata fields vary by installation. We export standard photo metadata (filename, creation date, photographer) as Nutshell attachments linked to the relevant Person, Company, or Article Note. Custom metadata schemas detected during discovery map to custom fields on the attachment record or to a linked custom object depending on the metadata volume.

Naviga Photos allows each deployment to configure unique custom metadata fields with custom labels, field types, and required flags. There is no standard field dictionary. We detect the custom field schema during discovery, map each to a Nutshell custom field of the equivalent type (text, number, date, picklist), and flag any that cannot be represented in Nutshell's native field types as requiring a separate custom object or a text field with enforced formatting.

Print Edition artifacts including page layouts, InDesign blueprints, and Sophi.io-powered automated print templates are tightly coupled to Naviga Publisher's production system and are not accessible via the Open Content API. We flag Print Edition records during scoping and exclude them from the CRM migration scope. Customers requiring print-to-print migration need a separate production workflow, not a CRM migration.