Migrate from Naviga to Microsoft Dynamics 365 Sales

Naviga Publications (news titles or media brands) map directly to Microsoft Dynamics 365 Sales Account records. The Publication name becomes Account Name; edition types and publication domain map to standard Account fields. Publication serves as the top-level organizational anchor for all content, subscriber, and advertiser data. We create Accounts before any related Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert.

Naviga Subscribers with active paid or free subscription status map to Dynamics 365 Contact records attached to the relevant Account. Subscribers with trial-only status or no confirmed acquisition source map to Lead records. We apply the split during the export transform based on the subscription status and billing history fields. The original Naviga subscription tier and billing status are preserved in custom fields on the destination Contact or Lead for reporting continuity.

Naviga Solicitors (field sales representatives) map to Microsoft Dynamics 365 Sales User records. We match by email during migration. The solicitor ID is preserved in a custom field solicitor_id__c on the User record so that Offer Group attribution can be reconstructed. Any Solicitor without a matching Dynamics 365 User is placed in a reconciliation queue for the customer's admin to provision before Contact import resumes.

Naviga Offer Groups bundle pricing structures and solicitor assignments for subscriber acquisition campaigns. We map Offer Groups to a custom Offer_Group__c object with fields for group name, pricing structure, and campaign period. The solicitor-to-subscriber linkage is reconstructed by exporting the full Offer Group hierarchy including solicitor IDs and linked subscriber records, then populating a junction object Offer_Group_Member__c that links each Contact to its acquiring Offer Group. This preserves the acquisition attribution that Naviga maintains through Offer Group membership rather than a direct foreign key.

Naviga Audience Members represent the broader reader population including non-subscribers tracked for engagement. We split by engagement depth: highly engaged readers with behavioral data map to Lead; readers with established subscription or conversion intent map to Contact. The Naviga behavioral segmentation tags migrate to custom multi-select picklist fields or Topics in Dynamics 365 so the customer's marketing team can continue audience segmentation post-migration.

Naviga Articles with authored text, metadata, and linked photos map to Dynamics 365 Task records or a custom Article_Activity__c object, depending on whether the customer needs to preserve editorial output as a sales engagement artifact. Article body migrates as rich text; author name resolves to a CRM User; publish date maps to ActivityDate. Articles with no engagement or revenue attribution become read-only historical records in the destination.

Naviga Ad manages print, digital, and broadcast ad campaigns with order management and production workflows. We map active ad campaign records to Dynamics 365 Opportunity objects with a custom record type for advertising revenue. Campaign start and end dates map to Opportunity Close Date and a custom field campaign_period_start__c. Line-item ad units map to OpportunityLineItems against a Product2 record representing the ad inventory. Completed campaigns become historical Opportunities with Closed Won or Closed Lost stage.

Naviga Photos with XMP, IPTC, and EXIF metadata map to SharePoint or OneDrive document libraries linked to the relevant Account, Contact, or Opportunity via Microsoft Graph. Standard photo metadata fields map to custom fields on the document record. Per-installation custom metadata fields on Photos are discovered during schema mapping, and each custom field is recreated as a typed custom field in Dynamics 365 before migration. Any custom field that cannot be represented by a Dynamics 365 field type is flagged for the customer's admin to resolve.