Migrate from Naviga to HighLevel

Naviga Subscribers (paying or free readers with account status, subscription type, and billing history) map directly to GoHighLevel Contacts. We extract subscriber email, name, account status, subscription type, and billing history fields, then map these to GHL native contact fields and custom fields for subscription-specific properties. Subscriber status values are translated to GHL contact tags (active, expired, paused) to support segmentation without requiring custom field creation.

Naviga Audience Members (the broader tracked reader population including non-subscribers) map to GoHighLevel Contacts with a behavioral data custom field or tag set. We extract engagement data, segmentation tags, and behavioral attributes from Naviga Audience and map them to GHL contact tags, custom fields, or smart list criteria depending on the segmentation complexity. Non-subscribing audience members land in GHL without subscription-specific fields populated.

Naviga Solicitors (field sales reps managing subscriber acquisition) map to GHL Users if they are internal team members who will log into GHL. If solicitors are external partners or agencies, they map to GHL Contacts with a solicitor-type tag. We extract the full solicitor roster during discovery and the customer decides the mapping strategy during scoping. The solicitor ID preserved in Offer Groups becomes either a GHL User lookup or a custom contact field, depending on the chosen configuration.

Naviga Offer Groups (bundles of pricing structures and special offers for subscriber acquisition campaigns) map to GoHighLevel Opportunities. Each Offer Group with its linked subscriber records becomes a Deal in GHL with the offer pricing and terms represented in the Opportunity amount and custom fields. Multiple offers within a single Offer Group can map to Opportunity line items if GHL pipeline configuration includes product items, or to custom fields capturing offer details.

Naviga Publications (the top-level organizational unit representing a news title or media brand) map to GoHighLevel Companies. We preserve the publication name, edition types, and publication-level metadata as Company fields and custom fields. Each Publication's constituent content (Articles) does not map directly to CRM records but can be referenced in the Company record via a custom field if the customer requires a link back to Naviga's content archive.

Naviga Ad campaign records (across print, digital, and broadcast channels including order management and production workflows) map to GHL Opportunities representing ad deals. For complex ad campaign metadata, we create a Custom Object (e.g., AdCampaign__c) with fields for campaign type, channel, creative assets, and production status, linked to the parent Company and Opportunity. The customer chooses the object structure during scoping based on their reporting needs.

Naviga subscription lifecycle events (subscription start, renewal, cancellation, pause, upgrade) migrate to GHL Tasks attached to the Contact record with the event type as Task subject and the timestamp as ActivityDate. This preserves the subscription engagement timeline within the GHL contact activity feed without requiring custom object creation.

Naviga Photos custom metadata fields (configured uniquely per installation with custom labels, field types, and required flags) are detected during schema discovery and mapped to GHL Custom Fields on the Contact or Custom Object. Standard XMP, IPTC, and EXIF metadata fields are mapped to GHL attachment metadata. Any Naviga custom fields that cannot be represented in GHL's native field types are flagged during discovery and documented for the customer's admin to handle post-migration.