Migrate from Naviga to Zoho CRM

Naviga Publications represent news titles or media brands as the top-level organizational unit. We map Publications to Zoho CRM Accounts with the publication name preserved in Account Name and edition types (print, digital, broadcast) stored as a multi-select picklist in a custom field publication_editions__c. Website URL maps to Account Website if the publication maintains a digital presence URL distinct from the Naviga platform URL.

Naviga Subscribers represent paying or free readers with account status, subscription type, and billing history. We map Subscribers to Zoho CRM Contacts with first name, last name, email, subscription type, and billing status preserved. The parent Publication is stored as a lookup to the Account record created from the parent Publication. Subscription tier and renewal date migrate to custom Contact fields subscription_type__c and renewal_date__c.

Naviga Solicitors are field sales representatives who manage subscriber acquisition. We map Solicitors to Zoho CRM User records using the solicitor's email and name. Any Solicitor record that cannot be matched to an active Zoho User goes into a reconciliation queue for the customer's admin to provision before the Subscriber import phase begins, because Subscriber records reference Solicitors via Offer Group linkage.

Naviga Offer Groups bundle pricing structures and special offers for subscriber acquisition campaigns. Offer Groups do not have a direct Zoho CRM equivalent, so we map them to Zoho CRM Campaigns with the Offer Group name as Campaign Name and the offer terms and pricing stored in custom fields offer_terms__c and base_price__c. The key function of the Offer Group—linking Subscribers to Solicitors—is preserved by also creating CampaignMember records that tie the migrated Subscriber Contact to the migrated Solicitor User.

Naviga Audience Members represent the broader reader population including non-subscribers tracked for engagement. We split at migration time based on engagement criteria: readers with a subscription record map to Zoho CRM Contact; readers without a subscription but with email and engagement history map to Zoho CRM Lead with the original Audience Member engagement score preserved in a custom field engagement_score__c. Segmentation tags migrate as multi-select picklist values or Zoho Tags.

Naviga Articles include authored text, metadata fields, and linked photos. We map article records to Zoho CRM Tasks with the article title as Subject, article body stored as Task Description, publish date as Activity Date, and author name in a custom field article_author__c. Articles are treated as CRM Activities against the parent Publication Account to maintain a content-production timeline view within the CRM.

Naviga Ad manages ad campaigns across print, digital, and broadcast channels. We map active ad campaign records to Zoho CRM Potentials with Campaign Name, deal amount (advertising revenue), and sales stage representing the campaign status. Advertiser company name maps to an Account lookup if the advertiser is a known organization, or to the Contact Company field if the advertiser is an individual contact.

Naviga Photos store media assets with XMP, IPTC, and EXIF metadata. We export photos with their standard metadata and attach them to the relevant Account (Publication), Contact (Subscriber), or Potential (Deal) record in Zoho CRM. Custom metadata fields vary by installation; we detect the custom schema during discovery and create matching custom fields in the target Zoho module before import. Fields that cannot be represented as Zoho field types are flagged for customer decision on handling.

Naviga Photos custom metadata schemas vary by installation with no standard field dictionary. We perform schema discovery on the source environment before mapping. Custom fields that map cleanly to Zoho field types (text, number, date, picklist, checkbox) are created as custom fields in the target Zoho module. Select and checkbox types map to Zoho picklist and checkbox respectively. Any custom field that cannot be represented in Zoho's supported field types is flagged in the discovery report for the customer's admin to decide whether to store as a long-text note field or exclude.

Naviga Print Edition artifacts including page layouts, InDesign blueprints, and automated print templates are tightly coupled to Naviga Publisher's Sophi.io-powered print manufacturing system and are not accessible via the Open Content API. We flag Print Edition records during scoping, exclude them from CRM migration scope, and notify the customer that these assets require a separate print-to-print migration workflow. This is explicitly outside Zoho CRM's scope as a CRM cannot store InDesign or print-production artifacts.