Migrate from Atlas ERP to Odoo ERP

Atlas COA is stored as a hierarchical table in MS SQL with account codes, names, types, and optional parent references. 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.

Atlas posts all module transactions automatically to the Finance module. 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.

Atlas warehouses store location_id, name, address, and optional cost-center linkage. 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.

Atlas item masters store product_code, name, type (stockable, consumable, service), unit of measure, cost price, and sales price. 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.

Atlas BOM data lives in companion tables (bom_headers, bom_lines) separate from item masters, linked by item_code. 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.

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

Atlas sales orders store a header (order_id, customer, order_date, terms) and line table (item_code, quantity, price, discount). We export the full order header and line detail with associated customer record, preserving open/closed status. Open orders migrate as sale.order in draft state; the customer reviews and confirms them in Odoo to trigger procurement or production. Closed orders migrate as sale.order in done state for historical reference.

Atlas purchasing module stores contract headers, line items, supplier linkage, and delivery schedule dates. Pending delivery lines are flagged as back-orders in Odoo. Contracts with blanket order characteristics map to purchase.requisition if the customer chooses to use Odoo's blanket order flow. We preserve supplier reference numbers, payment terms, and incoterms from the Atlas purchasing module.

Atlas CRM stores customer company records with contact persons, addresses, responsible sales person, and lifecycle stage. We export the full contact hierarchy and map to Odoo res.partner (with customer_rank set for companies, supplier_rank set for vendors, and individual contact persons as child partners under the company partner). Address fields map to street, city, state_id, country_id, and zip. Sales responsible person maps to Odoo's assigned user field.

Atlas employee records include name, department, position, employment status, and salary grade. We map these to Odoo hr.employee with department preserved as hr.department (created first), job title mapped to job_id, and active/inactive status from Atlas employment status. Salary grade and compensation details migrate as hr.contract records with wage and struct from a mapped salary structure.

Atlas payroll history is stored in a separate module with period-based gross/net breakdown, deductions, and employer contributions. We export run summary and line-by-line detail and map to Odoo hr.payslip with reference to the appropriate hr.contract, salary structure, and worked_days input lines. Note that Odoo Payroll (Enterprise app) must be activated in the destination; Community deployments cannot host payroll data natively and should plan for an external payroll system or Odoo.sh Enterprise.

Atlas stores user-defined fields in companion tables or extra columns not exposed in the standard UI. We run a pre-migration schema diff against the base Atlas table definitions to detect shadow columns, then include discovered extra columns in the export scope. These migrate as Odoo custom fields (ir.model.fields with track_visibility set to oncreate) on the relevant model, or as ir.model.data XML records if they require static definition. Customers confirm known custom fields during scoping so no shadow columns are missed.