Migrate from Atlas ERP to Dolibarr ERP

Atlas stores the COA as a hierarchical MS SQL table with account_code, account_name, and account_type. We extract the full account tree via direct SQL, preserving the parent-child hierarchy, and create corresponding Account records in Dolibarr's comptabilité module. Account codes migrate as-is or are remapped if Dolibarr's account code format differs. Account types (asset, liability, equity, revenue, expense) map to Dolibarr's categorie_comptype values.

Atlas journal_lines and journal_headers are extracted together to preserve the debit/credit balance per entry. We load these after operational records (orders, inventory movements, payroll runs) to avoid duplication because Atlas auto-posts every module transaction to Finance. We suppress the auto-posting flag during operational migration, then load only the open-period journal entries at cutover. Closed-period entries are archived in Dolibarr with a locked flag.

Atlas warehouses are master records with warehouse_id, name, address, and optional cost-center linkage. We export as-is and create corresponding Entrepôt records in Dolibarr's Stock module. If Atlas warehouses are linked to specific cost centers that do not map directly to Dolibarr's structure, we attach them as extrafields on the Entrepôt record.

Atlas item masters carry sku, description, unit of measure, cost price, and sales price. We export the item header and map to Dolibarr Product with type=0 for goods, type=1 for services. Unit of measure migrates to Dolibarr's unit_of_measure field. Price information maps to Prix de Revient (cost) and Prix de Vente (selling price) on the Product record.

Atlas BOM data lives in companion tables linked to item_code. Each BOM header and its bom_lines are exported as a unit and mapped to Dolibarr's Nomenclature (BOM) structure in the MRP module. Routing steps map to Dolibarr workstations and工序 (operations). If Atlas routing steps define production sequence and work centers, we create Dolibarr workstations with corresponding operation order and duration. This object requires the MRP module to be activated in Dolibarr.

Atlas production orders carry a header, linked BOM, routing steps, consumed-issued quantities, and a status lifecycle (planned, released, in-progress, closed). We preserve the order header, consumed quantities, and status. Status values are mapped to Dolibarr OF status constants (Draft, Validated, In Progress, Completed). Output quantities migrate to the OF's produced quantity field. The BOM reference is resolved to the migrated Dolibarr nomenclature ID.

Atlas sales_order_header and sales_order_lines are extracted with client linkage, line item, quantity, price, and discount. We create Dolibarr Commande Client records with line-by-line detail preserved. Open orders migrate with status = draft or validated (customer confirms which to activate at go-live); closed orders migrate as historical records. Customer linkage is resolved to the migrated Dolibarr third-party ID.

Atlas purchasing module stores contract headers, line items, supplier linkage, and delivery schedule dates. We export the full contract with line detail and map to Dolibarr Commande Fournisseur. Pending delivery lines are flagged as open; completed lines migrate as closed. Supplier linkage is resolved to the migrated Dolibarr third-party (Fournisseur) record.

Atlas CRM stores company name, contact persons, addresses, responsible person, and lifecycle stage. We export the full contact hierarchy and map to Dolibarr Tiers with the Client checkbox enabled. Contact persons become Dolibarr contacts linked to the Tiers record. Addresses migrate as Dolibarr address records. Atlas responsible person maps to Dolibarr commercial (sales representative) on the Tiers record.

Atlas supplier records from the purchasing module map to Dolibarr Tiers with the Fournisseur checkbox enabled. Supplier addresses, contact persons, and payment terms migrate as Tiers records. If Atlas stores supplier-specific catalogue pricing, we preserve it in Dolibarr's Prix Spéciaux (special pricing) extrafields.

Atlas employee records include name, department, position, employment status, and salary grade. We map to Dolibarr's HRM module if activated, creating a Dolibarr User record (for system login) plus an Employee record with department, job title, and contract type. Active/inactive employment status migrates as-is. Department hierarchy is preserved as Dolibarr establishments or departments.

Atlas payroll history stores period-based gross/net breakdown, deductions, and employer contributions in a separate payroll module. We export run summary and line-by-line detail, mapping gross, deductions, and net to Dolibarr salary record fields if the HRM payroll module is activated. If the payroll module is not activated, we create the salary data as a Dolibarr third-party extrafield table or a dedicated import CSV for the customer's HR team to enter post-migration.

Atlas user-defined fields added through the system administration layer exist in companion shadow tables or extra columns not exposed in the standard UI. We run a pre-migration schema diff against the base Atlas table definitions to identify these columns, then create matching Dolibarr extrafields (type-mapped: varchar to varchar, int to int, date to date) on the corresponding Dolibarr object before loading data. Customers must confirm known custom fields during scoping so we do not miss shadow columns.

Atlas stores documents linked to orders, items, employees, or production orders either on the file system or in varbinary MS SQL columns. We extract binary blobs and recreate them as file attachments in Dolibarr's documents directory, linked via the document element type and ID to the migrated record. We preserve original file names and timestamps.