Migrate from Genius ERP to Dolibarr ERP

Genius ERP Work Orders map to Dolibarr Manufacturing Orders (mrp module) if the production complexity is straightforward single-level assembly. Multi-level nested Work Orders with sub-assemblies map to Dolibarr Projects with nested Project Tasks representing each sub-assembly production stage. Work Order status (Draft, Released, In Process, Complete, Closed) maps to Dolibarr status values. Open Work Orders at cutover carry the highest migration risk — we batch-lock recently modified records during extraction and flag any Work Orders with mid-export edits for reconciliation.

Genius ERP multi-level BOMs with nested assemblies and subassemblies map to Dolibarr Products with the BOM/kit structure recorded in the MRP module. CAD-linked component relationships and revision numbers migrate as Dolibarr Product Technical Notes. BOM versions are captured as Dolibarr BOM revisions. We preserve the full hierarchy tree by resolving parent-Product and child-Component relationships during import, using the Product reference as the dedupe key. Note: Dolibarr MRP is a basic extension — teams with complex routing and operation-level scheduling should scope this as a configuration review post-migration.

Genius ERP Job Costing tracks actual vs. estimated costs per Work Order including labor, materials, and overhead allocations. We map each Work Order's cost ledger to a Dolibarr Project with Project Tasks representing cost phases. Labor hours migrate as Project Task time entries linked to Users; material costs migrate as expense lines. Overhead allocations are calculated as a percentage uplift applied per Project Task based on the Genius ERP cost breakdown. Dolibarr's Project module does not have a native estimated-vs-actual variance report, so we deliver a written cost comparison sheet in CSV for the customer's admin to load into a spreadsheet.

Genius ERP Items, stock quantities, warehouse locations, and reorder points map to Dolibarr Products with Stock Warehouse entries. Serial and lot number traceability migrates where present. Open purchase orders are flagged separately as supplier order records rather than stock entries, since they represent future inventory obligations. Multi-warehouse configurations in Genius ERP map to multiple Dolibarr Stock Locations under the same Product record. We validate that warehouse codes in Genius ERP have corresponding Dolibarr Stock Locations created before import begins.

Genius ERP Customer records map directly to Dolibarr Third Parties with the Customer category. Contact information, account hierarchies, and address details migrate as Dolibarr contact and address records linked to the Third Party. Where Genius CRM custom fields differ from Dolibarr's default Third Party schema, we apply field-level mapping and preserve custom field values in Dolibarr extrafields.

Genius ERP Sales Orders carry pricing, line items, and links to Work Orders. Open Sales Orders migrate to Dolibarr Customer Orders (statut Commandee client). Historical quotes that were never converted require explicit scoping — we migrate them to Dolibarr Proposals (statut Brouillon or Ouvert) only if the customer confirms they need quote history in the destination. Each Genius ERP Sales Order line item maps to a Dolibarr OrderLine with Product reference and quantity resolved. Sales Order status (Open, Closed Won, Closed Lost) maps to Dolibarr Order status values.

Open Purchase Orders migrate to Dolibarr Supplier Orders with vendor details, line items, expected delivery dates, and received-vs-ordered quantities. Closed POs are treated as historical records and migrated as Completed Supplier Orders with a historical flag so that they appear in Dolibarr's reporting but do not affect open liability. Vendor Third Parties are created or matched before the Purchase Order import so that the fk_soc foreign key on the Dolibarr supplier order is satisfied at insert time.

Genius ERP's General Ledger is intentionally lightweight. We export all posted journal entries, but the chart of accounts structure is limited compared to dedicated accounting systems. We flag all journal entries that reference Work Orders or inventory movements as potentially orphaned — these links require manual reconciliation or a separate accounting export from Genius ERP before migration. GL entries that do not have a Work Order reference map to Dolibarr Accounting Entries with the General Ledger account code preserved. Multi-entity posting is not supported in Genius ERP and therefore does not require inter-company consolidation mapping in Dolibarr.

Genius ERP User accounts, role assignments, and permission sets export as Dolibarr User records. Active vs. inactive status is preserved. Permissions are mapped to Dolibarr's permission model (which controls module access and CRUD per entity type). We resolve by email match where possible. Users without a matching Dolibarr account go to a reconciliation queue for the customer's admin to provision before record import resumes.

Genius ERP custom field definitions and current values migrate together to Dolibarr extrafields. We map field types (text, numeric, date, picklist) to the corresponding Dolibarr extrafield column type. Picklist values in Genius ERP map to Dolibarr varchar or integer extrafield values depending on the source type. Custom field values are loaded after the parent object migration is complete so that the extrafield columns exist in the Dolibarr database before data insert.

Documents attached to Work Orders, BOMs, or Customers are exported as binary files via the REST API or server-side file share. We preserve the original filename and Dolibarr entity association (fk_product for BOM attachments, fk_project for Work Order attachments). Large CAD files are chunked before upload to respect Dolibarr's file size limits. Dolibarr's document directory permissions must be verified before migration begins — forum threads document that incorrect write permissions on the /documents/ directory cause validation failures when Dolibarr attempts to rename document folders during approval workflows.

Quality management records including inspection results, non-conformance logs, and lot traceability data have no native equivalent in standard Dolibarr. We migrate the record headers and the links to their parent Work Order or Product. Unstructured inspection notes are migrated as Dolibarr Project Notes or Ticket Notes depending on the customer's chosen QM configuration. Dolibarr's Ticket module (if activated) can serve as a lightweight non-conformance tracking system; the customer confirms the configuration during scoping.