Migrate your Atlas ERP data

The COA is stored as a flat or hierarchical table in the MS SQL database with account codes, names, and types. We extract it via direct SQL read and remap account codes to the destination's COA during import. Parent-child hierarchy is preserved via the parent_account_id field.

Atlas posts all module transactions (sales, purchases, inventory movements, payroll) to the Finance module automatically. We extract the journal_lines and journal_headers tables together and map them to the destination's ledger format, flagging any multi-currency amounts that require exchange-rate handling.

Warehouses are standard master-data records with a warehouse_id, name, address, and optional cost-center linkage. We export them as-is and create corresponding inventory locations in the destination system.

Items include product masters with BOM (Bill of Materials) linkages for manufactured goods. The BOM explosion table is separate from the item master — we extract both and resolve the BOM hierarchy in the destination, flagging any item recipes that reference inactive warehouses.

Production orders link to the Production Planning module and carry a status lifecycle (planned, released, in-progress, closed). We preserve the order header, routing steps, and consumed-issued quantities, mapping the production calendar to the destination's scheduling model.

Sales orders are stored with a header and line table covering item, quantity, price, and discount. We extract the full order header, line detail, and associated client record, preserving open/closed status so that only active orders are re-created in the destination.

Purchase contracts and planned deliveries are stored in the Purchasing module. We export contract headers, line items, supplier linkage, and delivery schedule dates. Pending delivery lines are flagged for downstream PO generation in the destination system.

Employee records include name, department, position, employment status, and salary grade. We map these to the destination's HRM schema, preserving the department hierarchy and active/inactive employment state. Effective-dated salary history is extracted from the payroll history table.

Payroll history is stored in a separate payroll module with period-based gross/net breakdown, deductions, and employer contributions. We export the run summary and line-by-line detail, then map to the destination's payroll schema — noting that tax-code logic does not transfer and must be reconfigured per jurisdiction.

Atlas stores custom report definitions and dashboard configurations in a proprietary format tied to the UI layer. These are not independently exportable. We do not migrate report templates; we recommend rebuilding them in the destination system using its native reporting tools.

User-defined fields added through the system administration layer are stored in companion tables alongside the core entity tables. We detect these by inspecting the database schema before export, extract the extra columns, and map them to custom fields in the destination — handling data-type conversion for dates, numbers, and picklists.

Documents linked to orders, items, employees, or production orders are stored on the file system or in varbinary columns in MS SQL. We extract the binary blobs and recreate them as file attachments in the destination, preserving the original filename and association.

Customer and contact records from the CRM module include company name, contact persons, addresses, sales Responsible person, and lifecycle stage. We export the full contact hierarchy and map it to the destination's account or contact object, preserving any tag or segment assignments.

Service desk tickets carry a status, priority, assignee, and conversation history. We export the ticket header, linked SLA terms (which are not transferable), and conversation threads. SLA configuration must be re-created in the destination.