Migrate from Jobnimbus to Odoo CRM

JobNimbus contacts map directly to Odoo res.partner records. The primary address, phone, and email fields transfer as-is. Contact type (person vs. company) is preserved — organizations land as res.partner with is_company=True, individuals with is_company=False. Duplicate emails are merged, and the parent_id is set for contacts belonging to a company if a matching company record exists.

JobNimbus company records (distinct from contacts) map to res.partner with is_company=True and a parent link set for individual contacts belonging to that company. The company's name, website, and industry (if present) are transferred to the corresponding res.partner fields. Company hierarchy in JobNimbus (parent/branch relationships) maps to Odoo's commercial partner / child partner model, preserving the top-level parent as the commercial partner and creating child partners for branches.

JobNimbus jobs are the primary work records and carry the most business context. Each job maps to a crm.lead with type='opportunity'. Job title becomes crm.lead name, job status maps to a crm.stage via value mapping, and the primary contact on the job links to res.partner via partner_id.

JobNimbus boards represent workflow pipelines. Each board's columns (e.g., New, Active, Won, Lost) become Odoo crm.stage records scoped to a crm.team. The board itself has no direct Odoo equivalent — Odoo's pipeline is the crm.lead kanban filtered by team and stage.

JobNimbus workflow column names (e.g., Proposal, Under Review, Sold) map value-by-value to Odoo crm.stage names within each team. Stage probability and is_won flags are set in Odoo based on the JobNimbus column type — Sold becomes is_won=True, Lost becomes is_won=False with probability 0.

JobNimbus estimates attach to jobs and contain line items, tax rates, and totals. They migrate as sale.order records with order lines mapped to sale.order.line. Odoo's product catalog (product.product) must be populated first — FlitStack surfaces any unmapped line items as a reconciliation list.

JobNimbus invoices and payments migrate to Odoo account.move (type='out_invoice' or 'out_refund') and account.payment records. Each invoice creates an account.move with lines matching the original items, and each payment creates an account.payment linked to the move via payment_id. Odoo fiscal positions and payment journals must be configured before migration; the journal_id is set from the JobNimbus payment method. Historical paid status is preserved via the move state field.

JobNimbus custom fields on contacts (Date, Decimal, Number, Text types) require Odoo custom fields created via Settings > Custom Fields before migration. FlitStack creates the field definitions in the migration plan and applies the same technical field name pattern (x_jn_cf_<name>) for traceability.

JobNimbus custom fields on jobs migrate to custom fields on crm.lead. Type preservation is enforced: JobNimbus Date → Odoo date, Decimal → Odoo float, Number → Odoo integer, Text → Odoo char. Odoo custom fields cannot change type after creation — the migration plan locks these definitions.

JobNimbus suppliers map to res.partner with supplier_rank set to 1 (or higher if multiple supplier roles exist). The supplier's name, address, phone, email, and website transfer to res.partner fields. Contact persons within a supplier company migrate as child res.partner records with parent_id pointing to the supplier partner, preserving the person’s name, phone, and email on the child record. In Odoo, supplier_rank controls visibility in purchase orders and vendor dashboards.

JobNimbus file attachments (photos, PDFs, signed documents) re-upload to Odoo ir.attachment with res_model='crm.lead' or 'res.partner' and res_id pointing to the migrated record. Original filenames and MIME types are preserved. Odoo's attachment store (filestore) size limits apply — large photo sets are chunked during ingestion.

JobNimbus notes and tasks associated with jobs or contacts migrate as mail.message records on the corresponding crm.lead or res.partner. Scheduled follow-up tasks migrate as mail.activity records with the original due date preserved. Odoo's activity type (call, email, meeting) is inferred from the JobNimbus activity type field.

JobNimbus automations (triggers and actions) do not transfer to Odoo because Odoo's automation model (IrActions, server actions, automated actions) uses a different rule engine. FlitStack exports the automation definitions as a structured JSON file listing triggers, conditions, and actions — your Odoo admin or consultant uses this as a rebuild reference in Odoo Studio.

JobNimbus Engage texting logs migrate as mail.message records with message_type='comment' for reference, but the Engage inbox and phone-number-based routing have no Odoo CRM equivalent. Odoo SMS modules (if installed) can be configured for ongoing texting but historical Engage threads are preserved as read-only message history only.

JobNimbus reports and dashboard configurations do not migrate. The underlying data (contacts, jobs, estimates) is available in Odoo for rebuilding reports via Odoo's pivot view, graph view, or custom SQL queries. FlitStack exports the JobNimbus report column definitions as a reference for Odoo report rebuilds.