Migrate from Naviga to Pipedrive

Naviga Publications represent news titles or media brands and map directly to Pipedrive Organizations. We extract the publication name, domain, and any contact details stored at the publication level. For multi-edition publications (print, digital), we preserve edition metadata as custom fields on the Organization record. The Organization becomes the parent record for all Persons (Subscribers, Solicitors) linked to that publication.

Naviga Subscribers (paying or free readers) map to Pipedrive Persons with their contact details, subscription type, account status, and billing history. The subscriber's email address serves as the dedupe key. We preserve the original Naviga subscriber ID as a custom field naviga_subscriber_id__c for reconciliation. If the Subscriber has a linked Solicitor through an Offer Group, we resolve the solicitor ID and assign it as the Pipedrive Person's Owner.

Naviga Audience Members represent the broader tracked reader population including non-subscribers. Those with email addresses map to Pipedrive Persons. Those without verifiable contact details map to Pipedrive Leads (introduced in Pipedrive as a separate object) to preserve engagement data without requiring full Person record creation. Behavioral segmentation tags migrate as custom fields or labels on the Person or Lead record.

Naviga Solicitors are field sales representatives managing subscriber acquisition. They map to Pipedrive Users by email match. The solicitor's name, contact details, and active status migrate. Solicitors without a matching Pipedrive User account enter a reconciliation queue for the customer's admin to provision before migration resumes. Solicitor ID is preserved as a custom field for Offer Group attribution reconstruction.

Naviga Offer Groups bundle pricing structures and offers for acquisition campaigns. We map Offer Groups to Pipedrive Products if the group represents a productized subscription tier, or to Deals if it represents a campaign with associated revenue targets. The mapping decision is made during scoping based on whether the customer's reporting model treats offers as products or campaigns. Each Offer within an Offer Group becomes a Product variant or a Deal line item.

Naviga tracks which solicitor acquired which subscriber through Offer Groups rather than a direct many-to-many relationship. To preserve this linkage, we export the full Offer Group hierarchy including solicitor IDs and their linked subscriber records. During Pipedrive import, we resolve the subscriber's Person record and set the Pipedrive Owner field to the matched User (solicitor). We also write a custom field solicitor_acquisition_date__c and offer_group_id__c for audit. This step requires the Solicitor User mapping to be complete before Person import.

Naviga Ad manages ad campaigns across print, digital, and broadcast channels. We map ad campaign records to Pipedrive Deals if the campaign has associated revenue or booking value, or to Activities (custom activity type) if the campaign tracks fulfillment and delivery rather than revenue. Creative assets and order metadata migrate as notes or attachments on the Deal or Activity record.

Naviga Articles contain authored text, metadata, and linked photos. We extract the article body, author, publish date, and custom metadata, then map these to Pipedrive Activities (with custom activity type Article) or Notes. The article author maps to a User if they exist in the solicitor or internal staff pool, or to a custom text field if not. Publish date becomes the Activity date.

Naviga Photos store media assets with XMP, IPTC, and EXIF metadata. Standard metadata fields (file name, creation date, dimensions) migrate as Pipedrive attachment metadata. Any custom metadata fields configured in the Naviga Photos installation are detected during schema discovery and mapped to Pipedrive custom fields on the Activity or Note the photo is attached to. Custom field types (select, checkbox, text) are type-matched to Pipedrive field types at import time.

Print Edition artifacts including page layouts, InDesign blueprints, and Sophi.io-powered print templates live in Naviga Publisher's proprietary 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 entirely. The customer receives a written notification that these assets require a separate print-to-print or print-to-digital migration workflow outside the CRM scope.