Migrate from NetHunt CRM to Odoo CRM

NetHunt Folders are the top-level organizational container in NetHunt, each containing Records of potentially mixed types (Contacts, Companies, Deals) plus custom Views and Filters. We enumerate every accessible Folder during discovery, documenting folder names, record counts, and custom field schemas per folder. Each Folder maps to a separate Odoo CRM Pipeline with its own stage configuration. Folder-level Views and Filters do not migrate as Odoo views; we document them as a written filter reference for the customer to configure Odoo Search and Group By views post-migration.

NetHunt Records of contact type (standard name, email, phone, company link) map directly to Odoo res.partner records with address_type=contact. The contact-to-company linkage in NetHunt maps to the partner_id parent relationship in Odoo. Custom fields on the NetHunt Record become Odoo custom fields on res.partner using the ir.model.fields model. We preserve the NetHunt record ID in a custom field nethunt_record_id__c for cross-system audit.

NetHunt Records explicitly tagged as Lead type map to Odoo crm.lead with type=lead. Lead-specific fields (lead source, lifecycle stage, score, status) migrate to crm.lead standard fields (source_id, stage_id, priority) with custom fields for any NetHunt-specific lead attributes. Leads in NetHunt that have no associated Deal are imported as leads only; leads with deal history carry a reference to the migrated Opportunity.

NetHunt Company records map to Odoo res.partner with address_type=company. The NetHunt contact-to-company linkage becomes the partner_id parent relationship on the linked contact records. Company-level custom fields migrate as custom fields on res.partner. If a NetHunt Company record has no linked Contact records, it imports as a standalone company partner in Odoo.

NetHunt Deals map to Odoo crm.lead with type=opportunity. Deal fields (value, stage, probability, expected close date, responsible user) map to Odoo standard fields (planned_revenue, stage_id, probability, date_deadline, user_id). The NetHunt pipeline and stage assignment maps to Odoo's crm.stage within the relevant Odoo Sales Team. Closed-won and closed-lost reasons from NetHunt custom fields become Odoo stage change custom fields.

NetHunt Pipelines with their stage configurations map to Odoo crm.team records, each containing a sequence of crm.stage values. Stage probabilities, names, and sequence order migrate to Odoo stage definitions. If NetHunt uses multiple pipelines (e.g., one per product line or region), we create corresponding Odoo Sales Teams so that pipeline visibility is scoped to the relevant team.

NetHunt email engagements, notes, and meeting records attached to Contacts, Companies, and Deals migrate as Odoo mail.message records posted to the record's chatter (mail.thread). Email body content migrates as HTML-formatted mail.message content. Meeting records create mail.message entries with subtype=mt_meeting and calendar.event records for the meeting details. Activity timestamps preserve as mail.message create_date for accurate timeline ordering.

NetHunt Call Logs (duration, direction, notes, linked contact) map to Odoo crm.activity records with activity_type_id set to the Phone/Call activity type. Call duration, disposition, and outcome notes migrate to custom fields on the crm.activity record. Call logs are linked to the migrated Contact or Lead via the res_model and res_id fields on the activity record.

NetHunt custom fields are defined per-folder and vary across Folders, meaning the same logical field (e.g., Industry) may exist with different types or picklist values across different Folders. We capture the field definition for each Folder before migration and create Odoo custom fields on the corresponding object (res.partner for Contact/Company fields, crm.lead for Lead/Deal fields). Picklist fields migrate as selection fields or many2one relations depending on the value count.

NetHunt tags are string values on Records used for segmentation. Tags on Contact and Company records migrate as Odoo res.partner.category entries (the standard Odoo contact tag model). Tags on Deal records migrate as Odoo crm.tag entries linked via crm.tag.rel. We flag any tag name collisions with existing Odoo tags during scoping and prefix conflicting tags with the original folder name.

NetHunt file attachments linked to Records migrate as Odoo ir.attachment records linked to the corresponding res.partner or crm.lead via res_model and res_id. We migrate attachment filenames, MIME types, and URLs. For attachments stored in integrated third-party services (e.g., DocHub), we preserve the URL as a custom field on the linked Odoo record rather than attempting to download and re-host the file. Customers should verify DocHub and similar integration URLs remain accessible post-migration.

NetHunt Users referenced as record owners map to Odoo res.users by email match. We extract every distinct NetHunt user_id referenced on Contact, Company, Deal, and Activity records and match against the destination Odoo instance's user list. Any NetHunt owner without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record import continues, because OwnerId (user_id) references are required on Opportunity and Activity records.

NetHunt Workflows are automation rules operating inside Gmail and the NetHunt web UI with no API export mechanism. They do not map to Odoo Server Actions or Automated Actions because the execution models differ. We document every active NetHunt Workflow during discovery (trigger, conditions, actions, folder scope) in a written handoff document. The customer's Odoo admin or an Odoo implementation partner rebuilds them post-migration using Odoo's Studio or server action builder.

NetHunt Custom Roles define per-user permission sets within NetHunt's internal permission model. Odoo uses a separate access rights and record rules system (under Settings > Users > Access Rights) that does not have a direct structural equivalent. We document the NetHunt role assignments during discovery but do not migrate them. The customer's Odoo admin configures Odoo access rights and Sales Team visibility rules post-migration.