Migrate from Naviga to Salesforce Sales Cloud

Naviga Publications (news titles or media brands) map directly to Salesforce Account. We preserve the publication name, edition types (digital, print, broadcast), and the top-level organizational hierarchy. Each Publication becomes an Account with Type = 'Publisher' and a custom field publication_id__c carrying the Naviga source identifier for audit and future sync.

Naviga Subscribers (paying or free readers with account status, subscription type, and billing history) map to Salesforce Contact. The Contact's AccountId is set to the parent Publication Account. Subscription tier (digital, print, bundle) migrates to a custom field subscription_type__c, and billing history is preserved as related Opportunity or Case records depending on the customer's reporting needs.

Naviga Audience Members represent the broader reader population including non-subscribers tracked for engagement. We apply a qualification split during migration: active subscribers (indicated by subscription status fields) map to Contact under the parent Publication Account; non-subscribers with engagement history map to Salesforce Lead for nurture. Any existing email opt-out flag migrates to HasOptedOutOfEmail on both Lead and Contact.

Naviga Solicitors are field sales representatives managing subscriber acquisition. We map Solicitor records to Salesforce User, using email as the dedupe key. Inactive or departed Solicitors in Naviga map to Salesforce Users with Active = false to preserve historical assignment records without consuming a paid license. The customer's Salesforce admin provisions the actual User accounts before migration validates.

Naviga Offer Groups bundle pricing structures and special offers for subscriber acquisition campaigns. Each Offer Group maps to a Salesforce Pricebook2 with a custom field offer_group_id__c. The Offers within each group map to Product2 records with Standard Pricebook entries, preserving pricing, terms, and duration fields. The solicitor assignment that created the Offer Group is preserved as a custom field for commission reporting.

The relationship between a Subscriber, their Soliciting User, and the Offer Group that acquired them is reconstructed during migration. We export the full Offer Group hierarchy including solicitor IDs and their linked subscriber records, then create Salesforce Opportunity records representing each active subscription as a 'Subscription' record type. The Opportunity's Description field carries the original Offer Group and solicitor context for audit trails.

Naviga Ad manages ad campaigns across print, digital, and broadcast channels including order management, creative assets, and production workflows. We map ad campaign records to Salesforce Campaign with Campaign Type set by channel (Print, Digital, Broadcast). Campaign StartDate and EndDate migrate from Naviga ad flight dates, and BudgetedCost migrates to Campaign Budget.

Individual ad line items (placements, sizes, positions) from Naviga Ad map to Salesforce Campaign Member records linked to the parent Campaign Account or Contact. If Naviga tracks which subscriber or audience member saw the ad, that relationship migrates to Campaign Member Status with a custom field ad_placement__c identifying the specific insertion.

Naviga Articles (authored text with metadata, linked photos) map to Salesforce Task representing the editorial workflow if the goal is activity tracking. For publishers requiring full article archival, we create a custom Article__c object with fields for Title, Author__c (lookup to User), PublishDate__c, Publication__c (lookup to Account), ContentBody__c (long text), and Status__c (draft, published, archived). The customer selects the strategy during scoping.

Naviga Photos store media assets with XMP, IPTC, and EXIF metadata. We export photos with standard metadata fields (filename, creation date, dimensions) mapped to Salesforce ContentDocument (Title, CreatedDate, ContentSize). Custom metadata fields (configurable per Naviga installation) migrate to custom fields on ContentDocument or a linked ContentVersion custom object. Schema discovery is required before field creation because custom field labels and types vary by installation.

Naviga Photos supports installation-specific custom metadata fields with custom labels, types (select, checkbox, text), and required flags. We perform schema discovery on the source environment before mapping, and we flag any custom fields that cannot be represented in Salesforce's native field types (e.g., multi-value select maps to multi-select picklist; boolean maps to checkbox; free-text maps to text area). Unrepresentable fields are documented for manual entry or excluded.

Print edition artifacts including InDesign blueprints, Sophi.io page layouts, and print PDFs 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 and exclude them from the CRM migration scope. The customer is notified that these assets require a separate print-to-print migration workflow or manual archiving. If the publisher wants to reference print editions in Salesforce, we create a placeholder Note record with the edition identifier and a manual entry note.

Naviga Subscriber records include billing history fields (payment method, billing cycle, renewal date). We map active subscription billing to Salesforce Opportunity records with a 'Subscription Renewal' record type linked to the Contact and parent Account. For publishers with complex multi-year or tiered billing, we create a custom Subscription__c object to preserve the full billing timeline independent of Opportunity stage transitions.

Naviga Audience tracks behavioral data including article opens, email clicks, and read frequency. We map aggregate engagement metrics to Salesforce Campaign Member custom fields (LastEngagementDate__c, OpenCount__c, ClickCount__c). For detailed per-article engagement history, we create a custom Engagement__c object with lookups to the Contact/Lead, Article__c (if migrated), and Campaign, preserving timestamp and interaction type for segmentation and reporting.