---
title: "Atlas ERP to Odoo ERP Migration: Field Mapping & Rollback"
description: "Migrate Atlas ERP to Odoo ERP with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/erp/atlas-erp/to/odoo-erp"
---

# Atlas ERP to Odoo ERP migration

We migrate Chart of Accounts, Journal Entries, Warehouses, Items with BOM linkage, Production Orders, Sales and Purchase Contracts, Employees, and Payroll from Atlas ERP into Odoo ERP by reading directly from the MS SQL Server database, resolving the inter-module posting sequencing, and loading via Odoo's XML-RPC and CSV import endpoints with dependency-ordered inserts.

Short answer

FlitStack AI migrates account.accounts, account.moves, stock.warehouses, product.product + product.templates and mrp.boms from Atlas ERP to Odoo ERP, 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: 6-10 weeks.

![](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 what moves →](https://flitstack.ai/migrations/erp/atlas-erp/to/odoo-erp#what-moves)

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

Source Atlas ERP ![](https://flitstack.ai/platforms-trim/atlas-erp.webp)

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

account.account account.move stock.warehouse product.product + product.template mrp.bom

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

## What moves from Atlas ERP to Odoo ERP?

Moving from Atlas ERP to Odoo ERP is a platform transition from a Bulgarian client-server MS SQL Server system to a Belgian open-source modular ERP running on PostgreSQL.

Read the full summary

Atlas has no public API, so every extraction requires direct MS SQL read with db\_datareader access. We sequence the migration in dependency order — master data first (Accounts, Warehouses, Items, Employees), then transactional records (Sales Orders, Purchase Contracts, Production Orders, Payroll Runs) — while suppressing Atlas's automatic inter-module posting to prevent duplicate journal entries in the destination Finance module. BOM explosion tables and routing steps migrate as separate objects and are linked to the destination Item during import. Odoo's Workflow automations, server actions, and custom modules do not migrate as code; we deliver a written inventory of these for the customer's admin to rebuild. We do not migrate custom report definitions or BPM process definitions stored in proprietary Atlas UI formats.

1:1

### Chart of Accounts → account.account

Atlas COA is stored as a hierarchical table in MS SQL with account codes, names, types, and optional parent references.

How it maps

We extract the full account tree and map to Odoo account.account with code preserved, name remapped, and user\_type\_id set by type classification (receivable, payable, asset, liability, equity, revenue, expense). Foreign currency account flags migrate if Atlas uses multi-currency; otherwise accounts default to the company's base currency. Account is created first in all migration sequences because journal entries and all financial records depend on it.

1:1

### Journal Entries → account.move

Atlas posts all module transactions automatically to the Finance module.

How it maps

We extract journal\_headers and journal\_lines together and map to Odoo account.move (with move\_type = entry for manual journals, or sale/purchase/receipt for invoice-matched entries). We suppress auto-posting on migrated operational records and migrate only open-period journal entries during migration. Historical journal entries for closed periods are exported as reference material; the customer decides whether to enter them manually or skip based on audit requirements.

1:1

### Warehouses → stock.warehouse

Atlas warehouses store location\_id, name, address, and optional cost-center linkage.

How it maps

We export as-is and create Odoo stock.warehouse records with name, code (short code from Atlas warehouse\_id), address mapped to partner\_id, and a corresponding stock.location record of type internal. Multiple warehouses in Atlas create multiple Odoo warehouses, each with their own routes and push/pull rules configured post-migration.

1:1

### Items → product.product + product.template

Atlas item masters store product\_code, name, type (stockable, consumable, service), unit of measure, cost price, and sales price.

How it maps

We export the item master and join the bom\_lines table to capture Bill of Materials for manufactured goods. The item migrates as product.template (the canonical product definition) with product.product variants if Atlas uses variant dimensions. Routing steps from the routing\_steps table attach to the mrp.bom as operations.

1:1

### Bill of Materials → mrp.bom

Atlas BOM data lives in companion tables (bom\_headers, bom\_lines) separate from item masters, linked by item\_code.

How it maps

A naive export of item masters misses production capability. We join bom\_headers and bom\_lines to the item export, preserve the bom type (kit, standard, phantom), and map each component line to mrp.bom.line with product\_id resolved to the migrated product.product reference and quantity mapped. Routing steps map to mrp.workcenter.line on the destination BOM.

1:1

### Production Orders → mrp.production

Atlas production orders link to the Production Planning module with status lifecycle (planned, released, in-progress, closed), routing steps, and consumed/issued quantities.

How it maps

We preserve the order header, routing steps, and material consumption records. We map the Atlas production state to Odoo mrp.production state (draft, confirmed, progress, done, cancel). Work orders within the production order are created from the routing steps mapped to mrp.workorder.

******What moves 12 objects

Atlas ERP Odoo ERP

- Chart of Accounts account.account 1:1
- Journal Entries account.move 1:1
- Warehouses stock.warehouse 1:1
- Items product.product 1:1
- Bill of Materials mrp.bom 1:1
- Production Orders mrp.production 1:1

\+ 6 more in the mapping below

## How Atlas ERP and Odoo ERP 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                      | Atlas ERP                                                                    | Odoo ERP                                                                                       |
| ------------------------------ | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Database architecture          | MS SQL Server, client-server on-premises                                     | PostgreSQL, cloud or self-hosted with Odoo.sh options                                          |
| API access                     | No public REST or GraphQL API; direct MS SQL read required                   | XML-RPC and JSON-RPC APIs on all editions including Community                                  |
| Market scope                   | Bulgarian and Eastern European mid-market                                    | Global, 7M+ users; Community (free) and Enterprise tiers                                       |
| Automatic inter-module posting | Sales, purchasing, warehousing, production, and payroll auto-post to Finance | Modules are loosely coupled; journal entries are created explicitly or via automation          |
| Customization model            | MS SQL stored procedures (hard to version-control)                           | Python OWL add-ons with version-controlled git repos                                           |
| Pricing model                  | Per-user-per-month, decreasing at higher tiers, no per-transaction fees      | Per-user per month; Community free; Enterprise starts at \~$35/user/mo                         |
| Holding structure              | Self-referential company table with parent\_company\_id                      | Multi-company via Odoo database sharing or separate company records with inter-company rules   |
| Module scope                   | Finance, Production Planning, Warehousing, CRM, BPM, Payroll (bundled)       | 41+ apps; each activated independently; Manufacturing, HR, Project, Helpdesk are separate apps |

## What to watch for in a Atlas ERP to Odoo ERP migration

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

high

### No Atlas API — migration requires direct MS SQL read with privileged access

Atlas ERP has no documented REST or GraphQL API.

How we handle it

All migrations read directly from the MS SQL Server database using a privileged SQL account with db\_datareader permission scoped to the Atlas database. If the customer cannot provide direct database credentials or their IT team blocks the connection, migration is blocked. We coordinate with the customer's IT team to establish a read-only connection, validate the schema against our pre-migration discovery, and proceed only after confirming we can reach all required tables (including companion and shadow tables for BOM, routing, and custom fields). VPN or remote desktop access to the Atlas server may be required for on-premises deployments.

high

### Automatic inter-module posting creates duplicate journal entries in the destination

Every transaction in Atlas's Sales, Purchasing, Warehouses, Production, and Payroll modules automatically generates journal entries in the Finance module.

How we handle it

When we migrate both the operational records (Orders, Productions, Payroll runs) AND the finance records, the automatic posting can create duplicate ledger rows in the destination if Odoo's account automatic posting is enabled for the corresponding journals. We sequence the migration to migrate operational modules first with auto-posting suppressed on the destination journals, then migrate finance records only for the open period after go-live. Historical journal entries for closed periods are exported as reference CSVs for manual entry or audit-file retention rather than loaded into Odoo.

medium

### Holding structure and multi-company setup requires parent-first insert ordering

Atlas supports multi-company and holding structures using a self-referential company table where parent\_company\_id points to the holding entity.

How we handle it

Odoo implements multi-company via the res.company model with inter-company rules and database sharing options. We walk the Atlas company tree recursively during extraction and create parent companies in Odoo first (res.company with parent\_id = null), then subsidiaries in child-first order to satisfy foreign-key constraints. Inter-company transaction accounts and elimination journals must be configured in Odoo post-migration as part of the holding-structure setup.

medium

### BOM and routing tables are separate from item masters and require a joined export

Atlas Bill of Materials and routing step definitions for production orders are stored in companion tables (bom\_lines, routing\_steps) linked by item\_code rather than as sub-objects on the item master.

How we handle it

A naive export of just the item master will drop all production capability for manufactured goods. We join the bom\_headers, bom\_lines, and routing\_steps tables to the item export during extraction and map them to Odoo mrp.bom and mrp.workcenter.line records, resolving product\_id references to the migrated product.product IDs at import time.

medium

### Odoo PostgreSQL schema differs significantly from Atlas MS SQL schema — field type mapping requires care

Odoo stores monetary amounts as numeric(19,4) in PostgreSQL, dates as date without time zone, and timestamps as timestamp with time zone.

How we handle it

Atlas MS SQL may store monetary data as money or decimal, dates as datetime2, and may use Bulgarian or regional collation settings that affect string sorting and uniqueness constraints. We normalize all monetary fields to Odoo's numeric standard, convert datetime values to Odoo's expected timezone-aware format, and validate character encoding (UTF-8) before loading. Collations and index tuning for the destination PostgreSQL database are handled separately by the customer's DBA or Odoo.sh hosting team.

## How the migration runs

1. ### Discovery and database access validation

   We audit the Atlas MS SQL Server database across all modules in use (Finance, Warehousing, Production Planning, CRM, HRM, Payroll, BPM) and validate direct SQL connectivity with a read-only account.

   What this step covers

   We run a schema diff against base Atlas table definitions to identify companion tables and shadow columns (BOM lines, routing steps, custom fields, inter-module posting tables). We document the holding structure by walking the self-referential company table, capture the full Chart of Accounts hierarchy, and inventory production orders, BOM levels, payroll runs, and open vs closed transaction counts. The discovery output is a written migration scope and a pre-migration readiness checklist confirming database access, IT approval, and go-live date constraints.

2. ### Destination Odoo schema design and configuration

   We design the destination Odoo database schema.

   What this step covers

   This includes activating the relevant Odoo apps (Accounting, Inventory, Manufacturing, CRM, HR, Payroll), configuring the Chart of Accounts to match the Atlas COA structure, setting up warehouses (stock.warehouse with corresponding stock.location), creating product categories and product templates with the migrated BOMs, configuring multi-company settings if Atlas had a holding structure, and setting up the payroll structure (salary rules, structures, contracts). For self-hosted deployments, we provision the PostgreSQL database; for Odoo.sh, we set up the project and branch. All configuration is validated in a staging environment before production migration.

3. ### Master data migration in dependency order

   We migrate master data first in strict dependency order: Users (from Atlas employee records), Departments (hr.department from Atlas organizational structure), Companies (res.company with parent-first ordering for holdings), Warehouses (stock.warehouse), Product Categories, Products and BOMs (product.template, product.product, mrp.bom, mrp.workcenter, mrp.workcenter.line), Work Centers, Employees (hr.employee with department and job linkage), and Contracts (hr.contract with salary structure).

   What this step covers

   Each phase emits a row-count reconciliation report and a spot-check of 20-30 records against the Atlas source. Corrections happen at this stage, not in production.

4. ### Transactional record migration and auto-posting suppression

   We migrate open Sales Orders (sale.order), Purchase Contracts (purchase.order), and Production Orders (mrp.production) in that order, with each record type loaded as draft in Odoo for customer review before confirmation.

   What this step covers

   We suppress Odoo's automatic journal posting on the corresponding accounts during this phase so that sales and purchase document posting does not create duplicate ledger entries alongside any separately-migrated journal lines. Production orders are loaded in confirmed state with work orders generated from the migrated routing steps. Historical closed orders migrate as done records for reporting continuity.

5. ### Financial record migration and payroll history

   Journal entries for the open accounting period migrate as account.move records with move\_type set appropriately.

   What this step covers

   We skip historical journal entries from closed periods; these are exported as reference CSVs. Payroll runs migrate as hr.payslip records with line detail (hr.payslip.line) covering gross, deductions, and net. Note that Odoo Payroll requires the Enterprise app; Community deployments should plan an alternative payroll system or Odoo.sh Enterprise subscription before this phase begins.

6. ### Cutover, delta sync, and automation rebuild handoff

   We freeze Atlas writes during cutover, run a final delta migration of any records modified during the migration window (typically within 24-48 hours of cutover), then enable Odoo as the system of record.

   What this step covers

   We deliver a written inventory of Odoo Workflows, Server Actions, and automated actions that the customer's admin rebuilds in Odoo's Studio or through custom Python add-ons. We do not rebuild Atlas BPM processes, custom stored procedures, or report definitions as code. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's team. Post-hypercare, the customer owns Odoo administration, workflow configuration, and any new integrations.

![](https://flitstack.ai/platforms/atlas-erp.png) Atlas ERP ![](https://flitstack.ai/platforms/odoo-erp.svg) Odoo ERP

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 ERP 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

**6-10 weeks** Typical, smaller accounts

**14-24 weeks** Large or heavily customised accounts

A quote scales with data volume, BOM complexity, number of companies in the holding structure, and payroll history depth. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Atlas ERP to Odoo ERP →](https://flitstack.ai/contact)

## Why teams move from Atlas ERP to Odoo ERP

- Atlas ERP has no public API, requiring direct MS SQL Server connectivity for every migration and integration. Odoo provides XML-RPC and JSON-RPC APIs across all editions including Community, enabling native integrations with Shopify, Stripe, Stripe, and third-party logistics platforms without custom middleware. Businesses outgrow Atlas when their integration requirements outpace what VPN-connected SQL access can safely support.
- Atlas ERP serves almost exclusively the Bulgarian and Eastern European market, creating talent-acquisition and vendor-lock-in risk. Odoo has a global user base of over 7 million, a mature partner ecosystem across 120 countries, and a large developer community that makes it straightforward to hire experienced administrators and consultants. Companies report that Atlas implementation and support resources are difficult to secure outside standard business hours in a single time zone.
- Odoo's modular architecture lets companies deploy only the apps they need — CRM, Inventory, Manufacturing, Accounting, HR, Project, Helpdesk — and add more without re-platforming. Atlas bundles its modules with fixed pricing per user, which becomes less cost-efficient as companies grow beyond 100 users. Odoo Community is free, and Enterprise pricing is transparent and tiered by feature set rather than user count alone.
- Atlas customizations live in MS SQL stored procedures, which are difficult to version-control, audit, and migrate during application upgrades. Odoo customizations live as Python add-ons in a standard git repository, making them portable across Odoo version upgrades and easier to hand off when development teams change. Companies with extensive Atlas custom procedure work report that the maintenance burden grows with each version upgrade.
- Odoo's global open-source community and 9,000+ apps on the Odoo Marketplace provide a broader integration and extension ecosystem than any regionally-focused ERP. Companies needing native connectors for e-commerce, payment processing, electronic invoicing compliance (EU e-invoicing mandates), or BI/reporting tools migrate to Odoo specifically because the connector ecosystem reduces the need for bespoke integration work.

Questions, answered

## Atlas ERP to Odoo ERP migration questions

How long does an Atlas ERP to Odoo ERP migration take?

Most migrations land between six and ten weeks for companies with under 15 employees, 5,000 items, and clean master data. Migrations with multi-company holding structures, deep BOM hierarchies, multiple production facilities, or multi-year payroll history move to fourteen to twenty-four weeks because of parent-record resolution complexity, BOM explosion sequencing, and inter-company transaction reconciliation. The timeline also depends on Odoo edition selection (Community vs Enterprise), hosting model (self-hosted vs Odoo.sh), and how quickly the customer's IT team grants MS SQL database access for the read-only migration account.

Do Atlas BPM processes, custom stored procedures, and report definitions migrate to Odoo?

No. Atlas BPM processes are stored in a proprietary format tied to the UI layer and cannot be exported independently. Custom stored procedures written in MS SQL T-SQL do not have an Odoo equivalent; they must be rewritten as Python Odoo add-ons. Report definitions in Atlas do not transfer to Odoo's reporting engine. We deliver a written inventory of every active BPM process, custom procedure, and report definition with a description of what it does and a recommended Odoo equivalent (automated actions, server actions, Python add-ons, or QWEB reports). The customer's admin or an Odoo partner rebuilds these post-migration. This is a standard out-of-scope item for data migration engagements.

Can we run Atlas ERP and Odoo ERP in parallel during a trial period?

Yes, we support a parallel-run validation period where we migrate a snapshot of Atlas data into Odoo on a weekly or bi-weekly schedule so that the customer's team can validate data accuracy, test workflows, and train users in Odoo without disrupting the live Atlas system. Parallel runs are scoped as a separate phase after sandbox validation and before production cutover. This approach adds two to four weeks to the overall timeline but significantly reduces go-live risk for companies with complex production planning or multi-company structures.

What happens to our historical journal entries from closed accounting periods?

Atlas automatically posts all module transactions to the Finance module, creating journal entries for closed periods that predate the migration scope. We export these historical journal entries as reference CSV files organized by fiscal year and journal, which the customer's accountant or CFO can review. We do not load closed-period journal entries into Odoo because doing so would require reopening fiscal years, potentially violating audit trail integrity. The customer decides whether to retain closed-period journals as external audit files or enter a summary balance into Odoo's opening journal entry tool. Atlas BPM processes and report definitions are not migratable; we provide a written inventory of each for your admin to rebuild post-migration. Atlas custom stored procedures written in T-SQL do not transfer to Odoo Python add-ons and must be rewritten by an Odoo developer.

Does Odoo Payroll work for companies with Bulgarian payroll compliance requirements?

Odoo Payroll (Enterprise app) supports multiple countries including Bulgaria, with statutory rules for Bulgarian social security, health insurance, and income tax calculations. However, regional payroll compliance rules change annually and Odoo Payroll's Bulgarian localization is maintained by Odoo Belgium; customers should verify the current coverage of the Bulgarian payroll rules in the Odoo version they are deploying. For companies with complex collective bargaining agreements, multiple payroll entities, or historical payroll data going back more than five years, we recommend engaging an Odoo payroll specialist or a local Bulgarian payroll consultant to validate the migrated payroll data against Bulgarian statutory requirements before going live.

How do we handle Atlas ERP custom fields that are not visible in the standard UI?

We detect user-defined fields added through the Atlas system administration module by running a pre-migration schema diff against the base Atlas table definitions. Any extra columns or companion tables not present in the standard schema are flagged as shadow columns and included in the export scope. These migrate as Odoo custom fields on the relevant model. The customer must confirm known custom fields during scoping so we do not miss any shadow columns. We recommend a schema diff run at least two weeks before extraction so that any discovered custom fields can be mapped and tested before the production migration date.

Can FlitStack AI migrate from Odoo back to Atlas ERP if the migration fails?

We do not offer a guaranteed rollback path because Atlas ERP has no import API and the migration involves irreversible data transformations (schema restructuring, COA remapping, parent-record ID reassignment). We strongly recommend a full Odoo sandbox migration and customer sign-off before production cutover, and we maintain a complete, encrypted backup of all migrated data for 30 days post-go-live. If the customer needs to return to Atlas after go-live, they revert to their Atlas backup (maintained by their IT team) and we re-migrate on a new engagement scope. We do not guarantee data rollback to the Atlas database as part of the standard migration engagement.

## Related migrations

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

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

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

[See the service →](https://flitstack.ai/services/odoo-implementation) [**ERPNext to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/erpnext/to/odoo-erp) [**Sage Intacct to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/sage-intacct/to/odoo-erp) [**Odoo Enterprise to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/odoo-enterprise/to/odoo-erp) [**NetSuite to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/odoo-erp)

## 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. [Export and import data — Odoo 14.0 documentation (Country/Database ID/External ID resolution)](https://www.odoo.com/documentation/14.0/applications/general/export_import_data.html)
3. [Definitive foolproof steps for a successful import — Odoo Forum (Many2many comma-separated)](https://www.odoo.com/forum/help-1/is-there-a-definitive-foolproof-steps-for-a-successful-import-doc-39822)
4. [Upload size limit in Odoo — Odoo Forum (64 MiB Odoo.sh, 128 MiB self-hosted)](https://www.odoo.com/forum/help-1/upload-size-limit-in-odoo-221095)
5. [Fields and widgets — Odoo 19.0 documentation (Studio)](https://www.odoo.com/documentation/19.0/applications/studio/fields.html)
6. [Batch Import — Odoo Forum (Odoo Online throttling)](https://www.odoo.com/forum/help-1/batch-import-262164)
7. [What Does Odoo Migration Really Cost? Transparent Pricing Breakdown — Aspire Softserv](https://dev.to/aspire-softserv/what-does-odoo-migration-really-cost-a-transparent-pricing-breakdown-for-2025-48fj)

Get a quote

## Moving from Atlas ERP to Odoo ERP?

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

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