Migrate from Jarvis CRM to Odoo CRM

Jarvis CRM Contacts map to Odoo CRM Contacts. We extract contact records via FileMaker export or direct table access, preserving the contact's primary key and any foreign-key links to the parent company table. Email address is used as the dedupe key during Odoo import. Custom contact fields identified in the schema audit become Odoo CRM custom fields on the res.partner model.

Jarvis CRM Company records map to Odoo CRM Accounts. The company name becomes the Account name, and the FileMaker company ID is preserved as an external reference field for relational integrity. We export the Company table before the Contact table so that Account records are available to satisfy the many2one lookup at Contact import time.

Jarvis CRM Opportunities map to Odoo CRM Opportunities (crm.lead with type='opportunity'). We extract deal values, stage names, owner assignments, and associated contact and company references. Pipeline stage names vary per Jarvis deployment; we map them to Odoo stage IDs configured during Odoo CRM setup. Lost and Won reasons from custom Jarvis fields migrate as Odoo lead custom fields.

Jarvis pipeline stages are fully customizable per deployment. We map each source stage to an Odoo CRM stage within the designated pipeline, preserving stage ordering and probability percentages where available. Odoo's Kanban view order is set by the sequence field. If the destination uses Odoo Sales Teams, pipeline ownership maps to team_id on the Opportunity record.

Jarvis CRM Projects map to Odoo Project Management (project.project). We extract project name, description, assignees, and task structure. Gantt chart layout data migrates as project metadata (tags, custom fields); raw task dependencies require manual reconstruction in Odoo because the Gantt constraint model differs. Customer (client) association maps to an Odoo partner_id on the project record.

Jarvis Tasks and activities map to Odoo Project Tasks. We extract task name, description, assignee (mapped to Odoo User via email match), due date, and linked project reference. If the task is CRM-related rather than project-related in the source, it maps to an Odoo CRM Note or the chatter on the relevant Opportunity or Contact record.

Jarvis time entries (billable and non-billable hours) map to Odoo Timesheet records (account.analytic.line) if the Odoo deployment includes the Timesheet app, or to Project Task records with time-tracking fields if only the Project app is active. We preserve the original time entry ID, the associated project or contact reference, and the billing flag to maintain audit continuity.

Jarvis CRM Product and Service catalog records map to Odoo Product Templates. We extract item names, descriptions, prices, and SKU values. Product-to-opportunity associations in Jarvis (line items on deals) map to Odoo Opportunity Line Items if the Odoo deployment includes the Sale Orders app. Pricing rules from Jarvis migrate as Odoo pricelist items.

Jarvis CRM Vendor records map to Odoo Contacts with supplier flag enabled (res.partner with supplier_rank > 0). Purchase order headers and line items migrate to Odoo Purchase Orders (purchase.order and purchase.order.line) if the destination Odoo deployment includes the Purchase app. QuickBooks Online vendor data held within Jarvis may duplicate or conflict with imported vendor records; we flag duplicates for the customer to resolve before import.

Jarvis CRM Campaign and contact group records have no direct Odoo CRM analog. We map campaign membership to Odoo CRM Tags on the Contact record, preserving the original campaign name as a tag value. If the Odoo deployment includes the Email Marketing app, contacts are added to corresponding Odoo Mailing Lists. The customer selects the preferred segmentation strategy during scoping.

Jarvis FileMaker custom fields and custom tables vary per deployment. We identify every custom property during the mandatory schema audit, classify each as either a standard-field equivalent (and map it to an Odoo standard field) or a genuine custom field (and create it as an Odoo custom field on the relevant model). Custom FileMaker tables without an Odoo equivalent require a separate custom module scope, which we estimate separately from the base migration fee.

File attachments stored within the Jarvis FileMaker instance can be exported as binary files and stored in Odoo Document Management (ir.attachment) linked to the parent record (Contact, Account, Opportunity, Project). Attachment storage paths vary by deployment; we identify them during scoping. We include file naming conventions that preserve record context (e.g., ContactID_Filename) to maintain discoverability in Odoo.

Jarvis CRM Owner assignments on records map to Odoo User records. We resolve owners by email match against the destination Odoo User table. Any Jarvis owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Odoo users are matched only if the customer specifies that historical owner assignment must be preserved.