Migrate from SalesNexus to Odoo CRM

SalesNexus Contact maps to Odoo res.partner with is_company=False. The SalesNexus contact email becomes the partner email field and serves as the deduplication key during import. Custom fields on the Contact object migrate as custom fields on res.partner, which requires the Odoo Studio app on Standard and above plans; Community users with technical access can add fields directly via Python model inheritance. We resolve the linked Company record to a partner_id lookup on the Contact record at import time.

SalesNexus Company records map to Odoo res.partner with is_company=True. The Company name becomes the partner name, domain becomes the website field, and industry or category maps to a res.partner.category tag assignment. Company is imported before Contact so the company_id foreign key resolves correctly on each Contact row during batch import via Odoo's CSV or XML-RPC interface.

SalesNexus named Pipelines map to Odoo crm.team records. We extract the pipeline name and description and create an equivalent crm.team in Odoo with team_member assignments populated from the mapped SalesNexus user list. On Free and Starter plans, SalesNexus limits pipeline count to 3 and 10 respectively; Odoo imposes no equivalent limit.

SalesNexus Pipeline Stages are ordered integers with name and probability defaults that map to Odoo crm.lead stage_id with sequence order, probability percentage, and legend color (grey=new, blue=qualified, green=won, red=lost). We preserve the stage order and probability values. SalesNexus stage IDs are integer sequential values; Odoo uses many2one stage_id references that we resolve after creating the stage records. Closed-Lost and Closed-Won stage handling is preserved with Odoo's on_change probability auto-update rules adjusted accordingly.

SalesNexus Tasks map to Odoo project.task records attached to an Odoo Project created for the CRM context or to a dedicated Tasks project. Task fields (name, date_deadline, user_id, stage_id, priority, description) migrate directly. The SalesNexus task owner maps via email to an Odoo res.users record; unresolved owners are assigned to a default migration user and flagged for admin review. Completed status maps from SalesNexus kanban state to Odoo stage_id.

SalesNexus email templates with merge fields and HTML content map to Odoo mail.template records in the CRM app. Merge field syntax differs: SalesNexus uses {{contact.first_name}} patterns while Odoo uses {{object.partner_id.name}} Jinja2-style substitution. We convert common patterns (first_name, last_name, email, company_name) during the template body transform and flag any unrecognized merge field tokens in a template audit report for manual review in Odoo Studio.

SalesNexus Users referenced on Contacts, Companies, and Tasks map to Odoo res.users by email address match. We export the full user list from SalesNexus and cross-reference against the destination Odoo instance user table. Any SalesNexus owner without a matching Odoo user is placed in a reconciliation queue; the customer's Odoo admin provisions missing users before record import resumes to prevent orphaned owner_id references.

SalesNexus stores call recordings and transcription text linked to Contact Activity records. We export the transcription text as plain text and a URL reference to the recording. Binary audio files are not downloadable via the SalesNexus API, so we create an Odoo ir.attachment record with the transcription text as the file content and the recording URL as an external URL field on the associated crm.lead activity. The activity record is created as a note or log note on the lead.

SalesNexus email archival records (subject, body as HTML, date, direction sent/received) migrate to Odoo mail.message records linked to the corresponding crm.lead via model= crm.lead and res_id pointing to the lead ID. HTML email bodies are converted to plain text or kept as HTML depending on the Odoo version rendering capability. Email thread continuity is preserved by grouping messages with the same thread_id or subject pattern.

SalesNexus custom fields on Contacts and Companies identified by integer field IDs are exported via get-all-fields with field labels, types, and options. We create equivalent custom fields in Odoo via Settings > Technical > Database Structure > Models using the field type mapping (text to char, number to float or integer, dropdown to selection, checkbox to boolean). On Standard and above Odoo plans, the Studio app provides a UI for custom field creation; Community users require technical access or a developer to write the field definitions to the database.

SalesNexus drip automation workflow logic is not accessible via the public API. We export active contacts enrolled in each sequence with enrollment date, sequence name, and step number, then create Odoo crm.lead.tag records for each sequence name and assign the tag to the enrolled contacts. A note is appended to each contact documenting the sequence name and last enrollment date. The trigger logic, delay rules, and conditional branches must be manually rebuilt in Odoo using Automated Actions or Studio workflows; we deliver a sequence audit report listing all active automations with their enrollments for the customer's admin.

SalesNexus forms with field configurations and webhook/post URLs map to Odoo Website form definitions in the Website app. We export the form schema (field names, types, required flags) and recreate the form in Odoo Website > Contact Form. Form submission history migrates as crm.lead records created from the form, preserving submission date and field values. The iframe embed code is platform-specific and must be replaced with the Odoo Website form snippet in the customer's web properties.

SalesNexus personalized boards and dashboards (up to 10 boards and 20 dashboards depending on plan) export as metadata describing the chart type, data source object, and filter configuration. Odoo uses a different reporting model (action reports, Excel exports, and BI dashboard apps). We deliver a written report inventory document mapping each SalesNexus report to an equivalent Odoo approach: either a native Excel export definition, a custom Odoo BI view, or a documented rebuild step in Odoo Studio.

Nexi AI features (AI Email Assistant suggestions, AI Meeting Notes outputs, Smart Recommendations) are stored ephemerally in SalesNexus's AI inference layer and are not exposed via the public API. We export any suggestions stored as contact notes or activity notes that are persistent, but the AI model state and live inference outputs cannot be migrated. We document which Nexi features are active in the source account in a gap analysis report so the customer understands what will be unavailable post-migration and can evaluate Odoo AI add-on apps as replacements.

SalesNexus Nexi AI settings (AI Email Assistant tone and template preferences, AI Meeting Notes configuration, Smart Recommendation thresholds) are account-level configurations not exposed via API. We export the list of active Nexi features and their high-level configuration state as a written document. Rebuilding these settings in Odoo requires selecting an equivalent Odoo AI app or a third-party AI integration; we do not configure these as part of the data migration scope.

SalesNexus Deals within Pipelines map to Odoo crm.lead records with type=opportunity. The SalesNexus deal amount, close date, and probability map to Odoo planned_revenue, date_deadline, and probability fields. The SalesNexus pipeline and stage assignment maps to crm.lead.team_id and stage_id. We preserve the SalesNexus deal name as the Odoo lead name and any deal-level custom fields as custom fields on the crm.lead model. Lost deal reasons from SalesNexus custom fields map to Odoo's lost_reason field on the lead.