Migrate from Genius ERP to Microsoft Dynamics 365 Business Central

Genius ERP Work Orders are the central production and financial tracking object, combining production operations, costing, and status in one record. Dynamics 365 separates these into Sales Orders, Production Orders, and Projects. We use the Work Order's job number and customer reference to reconstruct the linkage: open work orders map to Production Orders (Production module) linked via the Sales Order, and historical cost-tracking work orders map to Project Transactions if the Project module is in scope. The original work order number migrates as a custom field on the Production Order or Project for audit continuity.

Genius ERP stores multi-level BOMs with nested assemblies, subassemblies, and CAD-linked component relationships in a single structure. Dynamics 365 separates BOM (component list) from Route (routing operations, work centers, and setup/cycle times). We split the Genius ERP BOM into a D365 BOM header with line-level components, and a corresponding D365 Route with operation sequences. Revision numbers and effectivity dates map to the BOM version and route version entities. CAD-linked component notes migrate as BOM line comments.

Job Costing in Genius ERP tracks actual-versus-estimated costs per work order across labor, materials, and overhead. We export the full cost ledger per job and import to D365 Production Journal lines with Cost Group assignments. Estimated costs from the original job quote map to Production Forecast lines; actuals from production consumption map to Production Journals. Genius ERP cost categories map to D365 Cost Groups, and the costing sheet dimension structure is replicated for reporting continuity.

Items, stock quantities, warehouse locations, and reorder points migrate to D365 Released Products with warehouse-specific on-hand quantities. Serial and lot number traceability migrates where present. Open purchase order expected receipts create inbound inventory reservations in D365 before the PO line is fulfilled. Closed inventory transactions are scoped as historical records separate from the current on-hand load.

Genius ERP customer records map to D365 Customer (the header entity) and Contact (individual contact persons). Account hierarchies from Genius ERP map to Customer hierarchies in D365. Where Genius CRM fields differ from the D365 Contact schema, we apply field-level mapping and preserve any custom fields. Customer-specific pricing from Genius ERP migrates to D365 Customer Price Groups.

Genius ERP Sales Orders and Quotes map to D365 Sales Orders with pricing, line items, and status preserved. Lines referencing BOMs link to the D365 BOM introduced during BOM mapping. Status is preserved: draft, confirmed, and in-progress orders migrate with open quantities; completed and cancelled orders migrate as historical records with all quantities closed.

Open purchase orders migrate to D365 Purchase Orders with vendor details, line items, expected delivery dates, and received-versus-ordered quantities preserved. Each line's received quantity creates a corresponding D365 receipt transaction. Closed POs migrate as historical records and are scoped separately from open PO scope. Multi-vendor POs are handled as single D365 PO records with all lines intact.

Genius ERP's basic G/L chart of accounts maps to D365 Main Account structure. Because the source G/L is intentionally lightweight, the migrated account structure is straightforward. Multi-entity or multi-jurisdiction Dynamics 365 configurations require separate legal entity setup beyond the migration scope and are flagged as a manual post-migration step. Any journal entries referencing Work Orders or inventory movements are flagged as potentially orphaned and require a separate accounting export for reconciliation.

User accounts, role assignments, and active/inactive status migrate to D365 Users with permission sets mapped to the destination role model. Because Genius ERP's role structure does not map one-to-one to D365's organizational security model, we preserve the role name and description in a custom field for the customer's admin to reassign during post-migration security configuration. Inactive users migrate with status preserved for historical reporting continuity.

Genius ERP custom field definitions and current values migrate together. Field types (text, numeric, date, picklist) are mapped to D365 extension field types on the target entity. Custom field values on production records (Work Order, BOM, Item) are loaded after the standard field migration phase completes, ensuring that all target entity records exist before custom field data is applied.

Quality management records including inspection results, non-conformance logs, and lot traceability data migrate as D365 Quality Journals and inventory lot records. Inspection results and pass/fail data map to quality journal lines with the corresponding inventory transaction reference. Lot traceability chains are preserved as D365 inventory lot records linked to the original production and purchase transactions. Unstructured inspection notes are flagged for manual entry or document attachment.

Documents attached to Work Orders, BOMs, or Customers export as binary blobs via the Genius ERP REST API or server-side file share access. We preserve the original filename and object association and import to D365's document handling via SharePoint integration or Dataverse attachments. Large CAD files are chunked during export and reassembled on the destination side. We do not migrate the internal CAD viewer state; the files are available for download in the new system.