Migrate from Net-Results to Odoo CRM

Net-Results Contacts map to Odoo res.partner records with partner_type=contact. Standard fields (name, email, phone, website, street, city, state, zip, country) migrate directly. Lifecycle metadata and custom contact fields map to res.partner custom fields created via Odoo Studio or XML during schema setup. Opt-out status from Net-Results suppression records maps to opt_out=True on the res.partner. Email address serves as the dedupe key during import to prevent duplicate partner creation.

Net-Results Companies map to Odoo res.partner records with company_type=company. This is a structural split from Net-Results where Contacts and Companies live as peers. In Odoo, the company partner is created first, then linked Contacts reference it via parent_id. The company domain becomes the partner's website field and is used as the dedupe key during import. Any custom company fields map to res.partner custom fields.

Net-Results Contacts with a linked Company record create res.partner contacts with parent_id pointing to the matching company partner. We resolve the company partner reference at migration time using the company domain or company_id lookup. If no matching company partner exists in Odoo, we create the company partner first before importing the linked contacts.

Net-Results Deals map to Odoo crm.lead records with lead_type=opportunity. The deal name becomes crm.lead name, deal amount becomes expected_revenue, deal stage maps to crm.stage (we configure stage values during schema setup to match the source pipeline), and closing date maps to date_deadline. Partner_id links the opportunity to the res.partner Account (company partner). Team_id and user_id resolve from Net-Results owner by email lookup against Odoo Users.

Net-Results Deal stages map to Odoo crm.stage records within a specific crm.team. Each stage gets a name, sequence order, and probability percentage matching the source pipeline. Stages are scoped per team in Odoo, so multi-pipeline Net-Results accounts require multiple crm.team and stage configurations. We configure this during the schema setup phase.

Net-Results Campaigns map to crm.lead.tag records (for campaign classification on leads and opportunities) and optionally to crm.team records if the campaign represents a sales team or business unit. Campaign metadata (name, status, start and end dates, type) is preserved in tag description fields and the team record name. Customers choosing tag-based mapping can query leads by campaign across the pipeline.

Net-Results Email Send events (send timestamps, open events, click events, bounce codes) migrate as mail.message records linked to the res.partner recipient. Send events use mail_message_subtype=mail.mt_comment for sends and comment threads for opens and clicks. Bounce codes map to a custom field on mail.message for bounce classification. Note that Odoo does not have a native bulk email send model; this migration preserves the historical record of what was sent and how recipients engaged, not the send infrastructure itself.

Net-Results email template HTML and asset references export to Odoo mail.template records. However, the Net-Results drag-and-drop rendering engine produces HTML that may reflow when pasted into Odoo's QWeb template engine. We export all template assets and HTML, flag each template for manual review post-migration, and advise customers to preview email sends before launching imported templates in Odoo campaigns.

Net-Results call engagements migrate as mail.activity records with activity_type_id referencing the built-in Phonecall activity type (or a custom call type if configured in Odoo). Call duration, disposition, and recording URL preserve in custom activity fields. Activity date and responsible user map from the Net-Results engagement timestamp and owner.

Net-Results meeting engagements map to Odoo calendar.event records. Event name, start datetime, end datetime, location, and attendee list (mapped to res.partner records via email lookup) preserve. Odoo calendar.event automatically creates related mail.message records in the partner and lead activity threads. Attendee status (accepted, declined, tentative) migrates as calendar.attendee state.

Net-Results Notes attached to Contacts or Companies migrate as Odoo note.note records. The note body (rich text) migrates as the note content, and the related res.partner or crm.lead reference preserves via res_model and res_id on the note. Notes with an assigned owner map to the matching Odoo User via email lookup.

Net-Results suppression records (hard bounces, unsubscribes, manually suppressed contacts) merge with existing Odoo partner records by email address dedupe. Active contacts in Odoo receive opt_out=True on res.partner. Hard bounces also add the email address to mail.black_list to block future Odoo mailings. We run the suppression merge as a post-load cleanup pass after all contact records are imported, deduplicating against any existing suppression records in the destination to avoid false opt-out flags on valid active contacts.

Net-Results workflow automation logic cannot be exported as a portable artifact. We capture workflow name, associated contact enrollment count, step count metadata, and which contacts were enrolled in each workflow. This data becomes a written rebuild guide for Odoo IrActionsServer automated actions or base.automation rules. The customer or an Odoo implementation partner rebuilds the trigger-and-action logic post-migration. Workflow enrollment data itself migrates as a custom partner field tracking which workflow each contact participated in.

Net-Results custom fields on Contacts require explicit mapping against Odoo res.partner during discovery. We inventory all custom fields, classify by data type (text, number, date, picklist, checkbox), and create matching custom fields on res.partner via Odoo Studio or custom module XML before contact import begins. Multi-select picklists in Net-Results map to Odoo many2many or selection fields depending on whether values are open or closed sets.

Net-Results custom fields on Companies map to Odoo res.partner custom fields on the company partner record. Type mapping follows the same logic as contact custom fields. If a custom company field references a related contact or external ID, we preserve it as a Char field and flag for manual review if the relationship cannot be resolved as a native Odoo many2one.

Net-Results Owners (users who own Contacts, Companies, Deals) resolve by email match against Odoo res.users. We extract every distinct owner email from Net-Results records and cross-reference the destination Odoo User list. Owners without a matching Odoo User enter a reconciliation queue for the customer's Odoo admin to provision before record import resumes. OwnerId references on Deals and Contacts cannot insert until User resolution is complete.