Migrate from Naviga to Odoo CRM

Naviga Publications represent news titles or media brands at the top of the organizational hierarchy. We map Publication records to Odoo Account with the publication name stored as Account name, and we preserve edition types (digital, print, broadcast) in custom Account fields. Publication-level custom metadata fields migrate to corresponding Account fields or to custom fields created in Odoo Studio before import.

Naviga Subscribers represent paying or free readers with account status, subscription type, and billing history. We map Subscribers to Odoo Contact records with the subscriber's contact details, subscription tier, account status, and billing history preserved in native Contact fields and custom fields. The Contact is linked to the corresponding Publication Account via a many2one relationship on the Contact record.

Naviga Solicitors are field sales representatives who manage subscriber acquisition. We map Solicitors to Odoo CRM User records for active sales representatives, or to Contact records with a custom role field if the solicitor is an external agent. The mapping choice is confirmed during scoping based on whether the solicitor needs Odoo login access or is referenced as a Contact on acquisition records.

Naviga Subscribe maintains solicitor-to-subscriber assignments through Offer Groups rather than a direct relationship. We must export the full Offer Group hierarchy including solicitor IDs and their linked subscriber records, then reconstruct the relationship in Odoo CRM using the solicitor ID as a foreign key mapped to the destination User or Contact record. The reconstructed relationship is stored in a custom field (e.g., acquiring_solicitor_id) on the Contact record. Offer Groups themselves map to Odoo Pricelist records or to custom Quote template records depending on whether the migration scope includes pricing structures.

Naviga Audience Members represent the broader reader population including non-subscribers tracked for engagement. We map these records to Odoo CRM Lead, preserving behavioral data, segmentation tags, and engagement scores as custom Lead fields. Active Leads with subscription conversion are flagged for the customer's admin to manually convert to Contact once the subscription is formalized in Odoo.

Naviga Articles include authored text, metadata, and linked photos. We map Articles to Odoo Note records linked to the relevant Publication Account, or to Task records if the article publish date and author are relevant for sales activity auditing. Article body migrates as Note content, author migrates as a custom Note field, and publish date migrates as the Note create date. The customer chooses the strategy during scoping.

Naviga Ad manages ad campaigns across print, digital, and broadcast channels. We map Advertisements to Odoo CRM Opportunity with the advertiser name linked to an Account, campaign dates preserved, and campaign type (print/digital/broadcast) stored as Opportunity custom fields. Budget, insertion order details, and creative asset references migrate as Opportunity fields or as Notes attached to the Opportunity.

Naviga Offer Groups bundle pricing structures and special offers for subscriber acquisition campaigns. Each group contains multiple Offers with distinct pricing and terms. We map Offer Groups to Odoo Product Pricelist records for recurring pricing structures, and we also export the individual Offers within each group as separate Price List Item records linked to the parent Pricelist. If the Offers represent one-time promotional bundles, they map to custom Opportunity Product records.

Naviga Photos stores media assets with XMP, IPTC, and EXIF metadata. Custom metadata fields from Naviga Photos can be configured per installation with no standard field dictionary. We export photos with their standard metadata, map standard fields to Odoo Attachment records linked to the parent Account or Contact, and flag any custom fields that cannot be represented in Odoo's field types during discovery for customer decision on field creation or exclusion.

Naviga Photos custom metadata schemas vary by installation. We perform schema discovery on the source environment before mapping, detect all custom field names, types, and required flags, and create corresponding Odoo custom fields via Studio or via data migration scripts before import. Fields with types that have no Odoo equivalent (e.g., multi-select with more than 40 options) are flagged for the customer to decide whether to create a Char field, a selection field, or exclude the data.

Print Edition artifacts including InDesign blueprints, page layouts, and Sophi.io-powered automated print templates are tightly coupled to Naviga Publisher's 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 entirely. Customers requiring these assets need a separate print-to-print migration workflow or manual transfer of print production files.

We extract every distinct Naviga Solicitor referenced on Subscriber, Offer Group, and Advertisement records and match by email against the Odoo destination database's Users. Any Solicitor without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active solicitors get Odoo User accounts with CRM group access; inactive solicitors are mapped to Contact records with a custom role field.