---
title: "Jonas Enterprise Service &… to Odoo CRM Migration"
description: "Migrate Jonas Enterprise Service & Construction Software to Odoo CRM: field-level mapping, a sample run, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/jonas-enterprise-service-construction-software/to/odoo-crm"
---

# Jonas Enterprise Service & Construction Software to Odoo CRM migration

Moving from Jonas Enterprise Service & Construction Software to Odoo CRM requires translating construction-specific job costing, service management, and work order data into Odoo's crm.lead and res.partner object model. FlitStack AI handles the schema translation, preserving original timestamps, owner assignments, and relational integrity across both platforms so your Odoo instance opens with a complete operational picture on day one.

Short answer

FlitStack AI migrates res.partners, crm.leads, project.tasks, sale.subscriptions and account.analytic.line + project.projects from Jonas Enterprise Service & Construction Software to Odoo CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 72–96 hours for under 25,000 records with standard field mapping.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/jonas-enterprise-service-construction-software/to/odoo-crm#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Jonas Enterprise Service & Construction Software ![](https://flitstack.ai/platforms-trim/jonas-enterprise-service-construction-software.webp)

Destination Odoo CRM ![](https://flitstack.ai/platforms-trim/odoo-crm.webp)

res.partner crm.lead project.task sale.subscription account.analytic.line + project.project

Mapped field by field · sample run · one-click rollback

## What moves from Jonas Enterprise Service & Construction Software to Odoo CRM?

Jonas Enterprise bundles construction accounting, job costing, service dispatch, and CRM into a single SQL Server-backed platform targeting mechanical and specialty contractors with $2M–$200M revenue.

Read the full summary

Odoo CRM exposes a separate crm.lead object for pipeline management, res.partner for contacts and companies, and project.task for service work orders — meaning Jonas's unified job-cost and service contract records must split across multiple Odoo objects during migration. We extract Jonas data via SQL Server export or Jonas API, then transform job-cost records into Odoo project records, service agreements into Odoo sale.subscription or project contracts, and dispatch logs into crm.lead activities. Jonas equipment and inventory linkages become Odoo product.product and stock.location records where applicable. The migration omits Jonas workflows, Procore integrations, and payroll linkages as those are destination-side rebuilds. We run a test migration against a representative slice before committing the full dataset, with a 24–48 hour delta pickup covering in-flight changes during cutover. Owner resolution maps Jonas user emails to Odoo res.users logins by exact match; unmatched owners receive a flagged fallback assignment.

direct

### Customer (Jonas Contact) → res.partner

Jonas stores customer records with name, address, phone, email, and primary contact flags.

How it maps

Odoo res.partner serves as the unified contact and company record. We map Jonas customer fields to res.partner using name, street, city, phone, email, and function fields. Jonas's primary-contact flag becomes a res.partner contact\_type value. Multi-contact accounts require creating a parent res.partner (company) with child contact records.

merged

### Customer Site / Location → res.partner (address)

Jonas associates service records with customer sites that may differ from the billing address.

How it maps

We merge site-specific address fields into a separate res.partner address record linked to the customer partner, preserving the Jonas site name as a contact name at that location. Site-level contact persons become child res.partner records with the site address as their street value.

transformed

### CRM Quote / Quote Header → crm.lead

Jonas CRM Quote Management creates quote headers with line items, pricing, and status.

How it maps

Odoo crm.lead models the opportunity as a pipeline record before a sale order is generated. We transform Jonas quote headers into crm.lead records with the quote value mapped to Odoo's expected\_revenue field and the Jonas quote status mapped to the nearest Odoo crm.stage value. Line-item detail is preserved as a custom text field or linked product.product records.

transformed

### Work Order → project.task

Jonas work orders carry dispatch information, assigned technician, service description, and completion status.

How it maps

Odoo project.task models work items under a project. We map Jonas work order records to project.task entries under a 'Field Service' project, preserving the Jonas work order number as task name, technician assignment as user\_id, and original scheduled date as date\_deadline. Task description maps to the Odoo description field with HTML formatting preserved.

transformed

### Planned Maintenance Agreement (PMA) → sale.subscription

Jonas PMAs define recurring service contracts with billing frequency and coverage scope.

How it maps

Odoo sale.subscription handles recurring contracts with automatic renewal tracking. We transform Jonas PMA records into sale.subscription entries, mapping contract value to recurring\_list\_price, billing frequency to recurring\_interval, and coverage description to description. Active/inactive status maps to sale.subscription state. Recurring line items become sale.subscription.line records.

merged

### Job Cost Record → account.analytic.line + project.project

Jonas Job Cost tracks cost categories, WIP amounts, and change orders against specific jobs.

How it maps

Odoo project.project holds the job as a project, and account.analytic.line holds the cost entries. We map Jonas job records to project.project with the job number as project name and job description as the project description. Each Jonas cost category entry becomes an account.analytic.line linked to the project, preserving cost amount, category, and posting date.

******What moves 12 objects

Jonas Enterprise Service & Construction Software Odoo CRM

- Customer res.partner 1:1
- Customer Site res.partner merged
- CRM Quote crm.lead transformed
- Work Order project.task transformed
- Planned Maintenance Agreement sale.subscription transformed
- Job Cost Record account.analytic.line merged

\+ 6 more in the mapping below

## How Jonas Enterprise Service & Construction Software and Odoo CRM differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                | Jonas Enterprise Service & Construction Software                                                                                                                                           | Odoo CRM                                                                                                                                                                           |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Data architecture        | Jonas Enterprise stores contacts, companies, job cost, and service records in a single normalized SQL Server database. CRM is a Quote Management submodule, not a standalone object graph. | Odoo CRM exposes crm.lead for opportunities and res.partner for contacts/companies as separate model objects. Sales orders and project tasks reference these through foreign keys. |
| Construction job costing | Jonas Job Cost module tracks WIP, cost categories, and change orders at the job level with direct payroll and inventory integration.                                                       | Odoo project.project and account.analytic models handle project tracking; construction-specific cost categories require custom fields and configuration.                           |
| Service management       | Jonas Service module covers dispatch, work orders, PMAs (planned maintenance agreements), and field time capture (eMobile) as an integrated stack.                                         | Odoo uses project.task for work orders, sale.subscription for recurring service contracts, and field service requires additional OCA modules or custom development.                |
| Accounting integration   | Jonas integrates AP/AR, payroll, and job cost in one ledger with certified payroll and union payroll support baked in.                                                                     | Odoo accounting is a separate module (account.account) linked to partners and projects but not directly coupled to field service or construction cost categories.                  |
| Export mechanism         | Jonas runs client-server on Microsoft SQL Server 2022; data export requires SQL Server native backup, linked server, or Jonas API with custom query build-out.                             | Odoo exposes data via XML-RPC or JSON-RPC API and native CSV export/import. Bulk imports use res.partner and crm.lead model endpoints.                                             |
| Customization model      | Jonas customizations are handled through Jonas Forms and J-Mail with limited API exposure for third-party tools.                                                                           | Odoo supports Python-based custom modules, OCA community addons, and Studio-based no-code customization; Enterprise adds proprietary modules not available in Community.           |

## Jonas Enterprise Service & Construction Software to Odoo CRM field mapping

The 30 most-used fields of 45 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/jonas-enterprise-service-construction-software/to/odoo-crm.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Jonas Enterprise Service & Construction Software Odoo CRM

1. `custname` Customer `name` res.partner
2. `address1` Customer `street` res.partner
3. `city` Customer `city` res.partner
4. `state` Customer `state_id` res.partner
5. `zip` Customer `zip` res.partner

| Jonas Enterprise Service & Construction Software field | Odoo CRM field                           | Mapping                 | Note                                                                                                                |
| ------------------------------------------------------ | ---------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------- |
| `Customer.custname`                                    | `res.partner.name`                       | direct                  |                                                                                                                     |
| `Customer.address1`                                    | `res.partner.street`                     | direct                  |                                                                                                                     |
| `Customer.city`                                        | `res.partner.city`                       | direct                  |                                                                                                                     |
| `Customer.state`                                       | `res.partner.state_id`                   | value\_mapping          | Jonas state abbreviations map to Odoo res.country.state records by country.                                         |
| `Customer.zip`                                         | `res.partner.zip`                        | direct                  |                                                                                                                     |
| `Customer.phone`                                       | `res.partner.phone`                      | direct                  |                                                                                                                     |
| `Customer.email`                                       | `res.partner.email`                      | direct                  |                                                                                                                     |
| `Customer.fax`                                         | `res.partner.fax`                        | direct                  |                                                                                                                     |
| `Customer.contactperson`                               | `res.partner.function`                   | direct                  |                                                                                                                     |
| `Customer.custtype`                                    | `res.partner.customer_rank`              | value\_mapping          | Jonas customer type codes (Contractor, Owner, GC) map to Odoo partner category tags.                                |
| `Customer.dateadded`                                   | `res.partner.create_date`                | custom\_field\_required | Original Jonas create date preserved as a custom field for reporting continuity.                                    |
| `Customer.jonas_id`                                    | `res.partner.jonas_customer_id`          | custom\_field\_required | Jonas internal ID stored as a custom Char field for traceability and delta-run de-duplication.                      |
| `Customer Site.sitename`                               | `res.partner.name`                       | direct                  | Site name becomes the contact name at that location under the parent customer partner.                              |
| `Customer Site.siteaddress`                            | `res.partner.street`                     | direct                  |                                                                                                                     |
| `Customer Site.sitephone`                              | `res.partner.phone`                      | direct                  |                                                                                                                     |
| `Work Order.wonum`                                     | `project.task.name`                      | direct                  |                                                                                                                     |
| `Work Order.description`                               | `project.task.description`               | direct                  |                                                                                                                     |
| `Work Order.status`                                    | `project.task.stage_id`                  | value\_mapping          | Jonas work order status (Open, Dispatched, Completed, Invoiced) maps to Odoo project.task stage values.             |
| `Work Order.scheddate`                                 | `project.task.date_deadline`             | direct                  |                                                                                                                     |
| `Work Order.technician`                                | `project.task.user_id`                   | transformed             | Jonas technician ID resolved by email match to Odoo res.users. Unmatched technicians flagged for manual assignment. |
| `Work Order.custom_field_wo_priority`                  | `project.task.x_wo_priority`             | custom\_field\_required | Jonas work order priority field migrated as a custom Char field on project.task.                                    |
| `PMA.contractnum`                                      | `sale.subscription.code`                 | direct                  |                                                                                                                     |
| `PMA.contractvalue`                                    | `sale.subscription.recurring_list_price` | direct                  |                                                                                                                     |
| `PMA.billingfrequency`                                 | `sale.subscription.recurring_interval`   | value\_mapping          | Jonas billing frequency codes (Monthly, Quarterly, Annual) map to Odoo recurring\_rule\_period values.              |
| `PMA.startdate`                                        | `sale.subscription.date_start`           | direct                  |                                                                                                                     |
| `PMA.enddate`                                          | `sale.subscription.date`                 | direct                  |                                                                                                                     |
| `Job Cost.jobnum`                                      | `project.project.name`                   | direct                  |                                                                                                                     |
| `Job Cost.jobdescription`                              | `project.project.description`            | direct                  |                                                                                                                     |
| `Job Cost.customerid`                                  | `project.project.partner_id`             | transformed             | Jonas customer ID resolves to Odoo res.partner ID via the customer mapping performed first.                         |
| `Job Cost.wipamount`                                   | `account.analytic.line.amount`           | direct                  | WIP amount maps as a negative (cost) entry in Odoo analytic lines.                                                  |

## What to watch for in a Jonas Enterprise Service & Construction Software to Odoo CRM migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Construction job-cost data has no native Odoo equivalent and requires multi-object mapping

Jonas Job Cost records combine WIP tracking, cost categories, and change orders in a single table linked to the job.

How we handle it

Odoo splits this across project.project (the job header), account.analytic.line (cost entries), and project.task (change order tasks). Migrating a Jonas job-cost record requires creating all three Odoo objects and maintaining their relational links via project\_id on the analytic line and task\_id on change orders. Teams that skip the multi-object planning step end up with orphaned cost entries that do not roll up to the project, breaking Odoo project reports. We map Jonas cost categories to Odoo analytic account records and link every analytic.line to the project during migration so the Odoo project shows accurate WIP from day one.

high

### Jonas service contracts (PMAs) require Odoo sale.subscription setup before data lands

Jonas Planned Maintenance Agreements store recurring billing amounts, coverage scopes, and customer-linked terms in a format that does not map directly to any Odoo native object without first configuring the sale.subscription module.

How we handle it

Odoo subscription requires an active subscription template and product to be defined before records can be created via API or import. If the Odoo subscription template is not configured before migration, all PMA records fail to insert and land in a skipped-records report. We deliver a subscription-template setup checklist as part of the pre-migration workstream so the sale.subscription model is ready when the migration run executes.

medium

### Jonas eMobile field-time data maps to Odoo mail.message, not timesheet records

Jonas eMobile and Field Time capture labor hours against work orders with time-in, time-out, and break deductions.

How we handle it

Odoo's native timesheet model (account.analytic.line with unit\_amount) requires an Odoo project and timesheet encoding via the timesheet app — not a default Odoo CRM installation. Teams that expect field-time data to appear in Odoo timesheets without the project.timesheet module installed will see the records land in mail.message instead, creating a mismatch between expectations and what Odoo displays. We flag the need for the Odoo timesheet module during discovery and migrate field-time as mail.message records on project.task if the module is not present.

medium

### Jonas SQL Server export requires linked server or custom query; Odoo XML-RPC import enforces per-request rate limits

Jonas runs on SQL Server with a client-server architecture — there is no public REST API for bulk record extraction.

How we handle it

Exporting Jonas data for migration requires either a SQL Server linked server connection from our migration server, a Jonas API query built against their documented endpoints, or a Jonas-native export using their report writer. Odoo's XML-RPC API enforces concurrent request limits that vary by Odoo edition and hosting provider; Community edition typically allows 10–20 concurrent API calls before returning a rpc\_error. We throttle Odoo API writes to stay within these limits and batch records into groups of 500 to avoid request queue overflow during the migration run.

low

### Odoo Community vs Enterprise determines which CRM features are available post-migration

Odoo Community provides the core CRM module with crm.lead, pipeline kanban, and activity scheduling.

How we handle it

Odoo Enterprise adds crm\_enterprise features including advanced forecasting, sales team hierarchy, and the Odoo Studio tool for visual field customization. Migration planning that assumes Odoo Enterprise features (such as opportunity territory management or advanced stage automation) will break if the destination Odoo instance is Community edition. We verify the target Odoo edition during discovery and scope field mappings to Community-compatible objects unless Enterprise is confirmed. Teams upgrading from Community to Enterprise post-migration can re-enable the crm\_enterprise module without re-migrating data.

## How the migration runs

1. ### Extract data from Jonas SQL Server using native query or linked server connection

   FlitStack AI connects to the Jonas SQL Server instance using read-only credentials scoped to the Jonas database.

   What this step covers

   We run discovery queries against all Jonas tables identified in the scoping questionnaire — dbo.Customer, dbo.WorkOrder, dbo.PMA, dbo.JobCost, dbo.Equipment, dbo.Inventory, dbo.Employee, and any user-defined tables from Jonas Forms. Data is extracted in CSV format with foreign key IDs preserved. For Jonas Cloud deployments, we coordinate with the Jonas support team to enable API-based extraction where available. The extraction produces a data manifest listing record counts per table and a data quality report flagging records with null required fields, duplicate external IDs, and orphaned foreign keys.

2. ### Build Odoo custom fields and configure subscription/project templates before data mapping

   Before any records are written to Odoo, we create the custom fields required for Jonas-specific data that has no native Odoo equivalent.

   What this step covers

   This includes x\_jonas\_customer\_id on res.partner, x\_wo\_priority on project.task, and x\_equipment\_location on product.product. We also configure the sale.subscription template for PMA migration and the project.project record that serves as the parent for all Jonas work orders and job-cost entries. Odoo field creation uses the Settings > Technical > Database Structure > Fields interface or direct PostgreSQL INSERT into ir.model.fields for bulk custom field deployment. This step runs in parallel with the Jonas data extraction.

3. ### Resolve owner and user mappings by email match across both systems

   Jonas stores technician IDs, sales reps, and dispatchers as Employee records with email addresses.

   What this step covers

   Odoo res.users records provide the login for any user who will interact with migrated records. We match Jonas Employee.email to Odoo res.users.login using exact string comparison. Records where no Odoo res.users exists for the Jonas email are flagged in a pre-migration report — your team either creates the Odoo user before migration or designates a fallback Odoo user as the owner. Owner resolution is a prerequisite for writing project.task and crm.lead records since those models require a user\_id foreign key.

4. ### Run test migration on a representative slice and generate field-level diff

   A representative slice of Jonas records — typically 200–500 records covering a customer, their work orders, a job-cost entry, an equipment record, and a PMA — is migrated to Odoo in a test environment.

   What this step covers

   We generate a field-level diff comparing the source value from the Jonas CSV extract against the destination value in Odoo for every mapped field. The diff is delivered as a spreadsheet highlighting mismatches, truncated values, and any records that failed to insert. You review the diff and approve or adjust the field mapping configuration before the full migration runs. Test migration is included at no additional cost.

5. ### Execute full migration with ordered record writes and delta-pickup window

   The full migration runs against Odoo using the tested mapping configuration.

   What this step covers

   Records are written in dependency order: res.partner first (customers and sites), then project.project (job-cost headers), then product.product (equipment and inventory), then project.task (work orders), then sale.subscription (PMAs), then mail.message (activity logs). This ordering ensures foreign key constraints are satisfied — a res.partner must exist before a project.task can reference its partner\_id. During the cutover window (typically 24–48 hours after the full migration commits), a delta pickup captures any records created or modified in Jonas since the migration snapshot was taken. FlitStack logs every insert and update operation to an audit trail; one-click rollback reverts the Odoo database to its pre-migration state if reconciliation fails.

![](https://flitstack.ai/platforms/jonas-enterprise-service-construction-software.png) Jonas Enterprise Service & Construction Software ![](https://flitstack.ai/platforms/odoo-crm.svg) Odoo CRM

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Odoo CRM Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**72–96 hours for under 25,000 records with standard field mapping** Typical, smaller accounts

**2–3 weeks for 100,000+ records or complex job-cost and service-contract data requiring custom field setup** Large or heavily customised accounts

Jonas-to-Odoo migration pricing scales with the number of Jonas records to translate, the count of custom Jonas fields requiring Odoo custom field creation, and the degree of construction-specific schema divergence requiring post-migration rebuild. Job-cost and work-order data that must split across Odoo project and crm.lead objects adds mapping complexity. Service contract (PMA) data and Jonas eMobile field-time logs require custom field handling and fall in the upper price tier. The typical range covers data extraction from Jonas SQL Server, schema translation into Odoo res.partner and crm.lead models, owner resolution, test migration with diff, delta pickup, and audit log. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Jonas Enterprise Service & Construction Software to Odoo CRM →](https://flitstack.ai/contact)

## Why teams move from Jonas Enterprise Service & Construction Software to Odoo CRM

- Jonas Enterprise's limited third-party integration ecosystem has become a bottleneck as teams adopt modern tools for field tracking, proposal generation, and financial reporting. Users report that integration to project management side of construction requires significant workaround effort, and the client-server architecture makes API-based connectivity unreliable. Moving to Odoo CRM offers a REST/XML-RPC API and a larger partner ecosystem for connecting construction-specific workflows that Jonas does not natively support.
- Jonas Construction Software is priced on a per-module, per-user model with mandatory SQL Server licensing and Jonas Core User License fees. Contractors with growing field-service headcounts find the seat-cost scaling unpredictable. Odoo Community offers its CRM module at no license cost, with Odoo Enterprise at a flat per-user rate. Reviewers on construction forums note that Jonas's total cost of ownership including server maintenance and per-module upgrades exceeds comparable Odoo deployments at equivalent scale.
- Jonas's overcomplicated housekeeping procedures and set-up requirements frustrate operations teams that need straightforward CRM workflows. Users describe glitchy accounting entries, complex payroll rounding issues, and a steep configuration learning curve that delays team adoption. Odoo CRM's Kanban-based pipeline interface, drag-and-drop stage management, and standard crm.lead model provide a more familiar sales workflow without the construction-specific overhead Jonas imposes on every record.
- Jonas runs as a client-server application on premise or Jonas Cloud (Microsoft Azure), which means version upgrades require coordination with Jonas support and sometimes a full migration to a newer major version. Reddit threads in r/Odoo discuss companies leaving platforms with EOL version constraints — a pattern that applies to Jonas shops on older SQL Server versions. Odoo's open-source upgrade path and Odoo.sh cloud hosting offer more control over when and how version upgrades are applied.

Questions, answered

## Jonas Enterprise Service & Construction Software to Odoo CRM migration questions

How long does a Jonas Enterprise to Odoo CRM migration take?

Most Jonas-to-Odoo migrations complete within 72–96 hours of migration run time for setups under 25,000 records. Complex migrations involving Jonas Job Cost data, PMAs, and equipment records with 100,000+ total records extend to 2–3 weeks, primarily because of the multi-object mapping and Odoo custom field setup required before data can land. The longest single step is typically Odoo custom field configuration and subscription template setup — not the data migration itself. Discovery and test migration add 3–5 business days before the migration run starts.

Will my Jonas service workflows and PMAs migrate to Odoo?

No. FlitStack AI migrates data and schema only — Jonas workflows, dispatch rules, Jonas Forms automation, and eMobile routing configurations do not transfer to Odoo. Planned Maintenance Agreements migrate as data records (sale.subscription) but the billing automation logic and service scheduling rules require manual rebuild in Odoo's sale.subscription and project modules. We export Jonas workflow definitions as a reference document your Odoo administrator can use to configure equivalent rules in Odoo's Automate menu and Studio tool. Jonas integrations with Procore, QuickBooks, and field hardware do not migrate and must be re-established via Odoo's API or third-party connectors.

Can I migrate Jonas custom fields and user-defined data to Odoo?

Yes. Jonas custom fields created via Jonas Forms are identified during the discovery phase and recreated as custom fields in Odoo via Settings > Technical > Database Structure > Fields. The field type is matched to the closest Odoo equivalent — Jonas date fields become date fields, pick-lists become selection fields, and numeric fields become float or integer depending on precision. After creation, custom field values are included in the migration run. Odoo imposes a naming convention (x\_\<fieldname>) for custom fields that Jonas does not enforce; we handle the naming translation automatically.

Does the Jonas to Odoo migration affect my Jonas account during the cutover?

No. FlitStack AI uses read-only access to Jonas — either via SQL Server query or scoped API read — which does not interfere with your team's day-to-day operations in Jonas. Your dispatchers, technicians, and office staff continue working in Jonas during the entire migration. A delta-pickup window of 24–48 hours after the full migration commits captures any new work orders, customer records, or service activities created or modified during the cutover period so Odoo reflects Jonas's final state at go-live. Jonas accounts are not suspended, locked, or altered during migration.

What happens to Jonas equipment and inventory records in Odoo?

Jonas equipment records become product.product entries with the equipment asset ID stored as default\_code and the serial number as barcode. Maintenance history for equipment is migrated as project.task records under a dedicated 'Equipment Maintenance' project, linked to the corresponding product.product record. Jonas inventory items (parts, materials) map to product.product with the Jonas unit cost stored as standard\_price and on-hand quantities loaded into stock.quant after your Odoo warehouse and location configuration is complete. If you use Odoo inventory tracking, a stock.location hierarchy must be set up before the on-hand quantity migration step runs.

What Odoo edition is required for this migration?

The Jonas-to-Odoo migration runs on both Odoo Community and Odoo Enterprise editions. The core migration — res.partner, crm.lead, project.project, project.task, sale.subscription, and mail.message — is supported in Community. Odoo Enterprise adds crm\_enterprise features (territory management, advanced forecasting, Odoo Studio field customization) that are not required for the base migration but may be relevant if you plan to use Odoo for territory-based CRM workflows post-migration. We scope the migration to Community-compatible objects unless you confirm Enterprise is deployed at the destination.

## Related migrations

[![](https://flitstack.ai/platforms-trim/odoo-crm.webp) Migrate to **Odoo CRM** Every source we move into Odoo CRM, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/odoo-crm)

### [Odoo implementation](https://flitstack.ai/services/odoo-implementation)

[Set up Odoo CRM and migrate into it as one engagement.](https://flitstack.ai/services/odoo-implementation)

[See the service →](https://flitstack.ai/services/odoo-implementation) [**Mailchimp to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/mailchimp/to/odoo-crm) [**SuiteCRM to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/suitecrm/to/odoo-crm) [**Zendesk Sell to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zendesk-sell/to/odoo-crm) [**HubSpot to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/hubspot/to/odoo-crm) [**Pipedrive to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/pipedrive/to/odoo-crm) [**Salesforce to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/odoo-crm) [**Jonas Enterprise Service & Construction Software to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jonas-enterprise-service-construction-software/to/dynamics-365-sales)

## Sources: official documentation

1. [Export and import data — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/applications/essentials/export_import_data.html)
2. [Import products — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/applications/sales/sales/products_prices/products/import.html)
3. [Odoo Online programmatic throughput limits — Odoo Forum](https://www.odoo.com/forum/help-1/odoo-online-throughput-limits)
4. [Data Cleaning — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/applications/productivity/data_cleaning.html)
5. [Datetime field reference — Odoo 19.0 documentation](https://www.odoo.com/documentation/19.0/developer/reference/backend/orm.html#datetime-fields)
6. [Upload size limit in Odoo — Odoo Forum (128 MiB cap)](https://www.odoo.com/forum/help-1/upload-size-limit-in-odoo-221095)
7. [Fields and widgets — Odoo 19.0 documentation (Studio)](https://www.odoo.com/documentation/19.0/applications/studio/fields.html)

Get a quote

## Moving from Jonas Enterprise Service & Construction Software to Odoo CRM?

Tell us roughly how many records and objects you have. We scope the mapping and the Odoo CRM setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
