Migrate from Manu Online to Microsoft Dynamics 365 Business Central

Manu Online Products (manufactured, resold, purchased variants) map to Dynamics 365 Item records in the Product Information Management module. The manuonline_ product table supplies item number, description, unit of measure, cost method (FIFO, Average, or Standard), and default warehouse. We translate Manu Online's FIFO cost layers to the destination item's costing model during the mapping phase and flag any items where the layered unit cost diverges significantly from the migrated average or standard cost for customer review. Multi-currency unit costs from Manu Online migrate to the Dynamics 365 item's cost price fields in the base currency, with the original currency stored in a custom field if the customer requires it.

Manu Online BOMs (single-level in Mini Enterprise, multi-level in Enterprise Edition) map to Dynamics 365 BOM or Formula records. Multi-level BOMs from Enterprise Edition may require flattening or expansion depending on whether the destination uses route-based production orders. We inventory all BOM structures during scoping, identify any Enterprise-tier-only features (parallel production orders, co-products, by-products), and handle them as separate configuration items in Dynamics 365. BOM versions migrate with the active BOM version flagged.

Manu Online on-hand quantities per product per warehouse map to Dynamics 365 on-hand inventory. The warehouse and location dimensions translate directly; serial and lot numbers attach to inventory transactions (InventTrans) in Dynamics 365. We run a pre-migration traceability audit to identify what percentage of stock lines carry complete lot or serial numbers. Blank lot numbers in Manu Online create a traceability gap in Dynamics 365 that we surface in the scoping report before migration begins.

Manu Online Customer records map to Dynamics 365 Customer Master (CustTable in Finance and Supply Chain, Customer page in Business Central). Address, contact, tax registration number, payment terms, and price list assignment transfer directly. Open sales orders and credit limits migrate as related records. Customer addresses in Dynamics 365 support separate Invoice Address and Delivery Address roles per address record; we map Manu Online's address usage flags to the appropriate Dynamics 365 address roles.

Manu Online Supplier records map to Dynamics 365 Vendor Master. Address, contact, lead time, preferred unit of purchase, and payment terms transfer directly. Outstanding purchase orders carry forward with their receipt state to avoid duplicate ordering at cutover. Vendor addresses in Dynamics 365 support the same separate invoice and delivery address roles as customers.

Manu Online Sales Orders map to Microsoft Dynamics 365 Sales Orders. Line items, quantities, pricing, and dispatch instructions transfer at the line level. Partially despatched lines in Manu Online are resolved by setting the Dynamics 365 line delivery status to the equivalent partially shipped state. Sales order status (Confirmed, Despatched, Invoiced) maps to the corresponding Dynamics 365 confirmation and delivery status fields. The sales agreement or blanket order equivalent in Dynamics 365 is identified during scoping if the customer uses long-term sales commitments.

Manu Online Purchase Orders map to Dynamics 365 Purchase Orders. Expected delivery dates and received-versus-ordered quantities carry forward with the receipt state. Open POs are flagged with their receipt status to prevent duplicate ordering at cutover. If Manu Online POs reference a supplier item number, we map it to the Dynamics 365 vendor product number on the item's vendor collaboration data.

Manu Online Works Orders reference a BOM, allocate stock, and record labour time and completed quantities. They map to Dynamics 365 Production Orders. The mapping depends on the destination product: Finance and Supply Chain Management uses ProdTable with route and job scheduling; Business Central uses production orders with BOM and work centre routing. We map work order stages and unfinished progress to the destination's production order status, flagging any operations recorded in Manu Online that have no direct equivalent in the Dynamics 365 production model. Enterprise-tier parallel production orders from Manu Online may require manual recreation as separate production orders or as job scheduling lines in Dynamics 365.

Posted invoices and credit notes in Manu Online carry accounting implications, especially when Xero has already received the data via the native push. We coordinate with the customer during scoping to determine whether posted documents migrate as open items in Dynamics 365, are excluded from migration to avoid double-posting in Xero, or are marked as historical with only the audit trail preserved. The decision depends on whether the customer will continue using Xero, transition to Dynamics 365 Finance, or decommission the accounting integration entirely. We flag any Xero-synced posted documents in the scoping report with a recommended disposition for customer sign-off.

Traceability records (serial numbers and lot numbers linked to stock transactions, works orders, and delivery documents) migrate to Dynamics 365 InventSerial and InventBatch tables. The traceability chain — lot number to supplier, through production, to customer delivery — transfers as fully as the source data permits. If Manu Online records did not capture supplier lot numbers at goods receipt, the inbound traceability leg will be blank. We include a pre-migration data quality report that shows the percentage of lines with complete traceability and the percentage with gaps, so the customer can decide whether to remediate before migration or accept the gap in the destination system.

Manu Online user accounts with login, email, and role-based permissions map to Dynamics 365 Worker records (if using HR integration) and User accounts with security roles. We map active users to the destination system, flagging any users with elevated admin privileges for explicit re-creation in Dynamics 365 security role assignment. Role mapping is configuration-based: Manu Online permission levels map to the nearest Dynamics 365 security role (for example, Manu Online Stock Controller maps to Inventory Manager in Business Central or the equivalent security duty in Supply Chain Management). The customer's admin assigns the final role after reviewing the mapping report.

Manu Online custom fields on Products, Customers, and Orders may not be fully captured in the DataWarehouse export. We inventory all custom field definitions during scoping against the manuonline_ DataWarehouse schema. Any custom field not present in the standard export is flagged as a manual-entry or UI-export candidate. Custom fields that do migrate are created as extension fields in Dynamics 365 using the field group or custom field framework. We note that Dynamics 365 Finance and Supply Chain Management uses extension fields via the Extension SDK or the customize workspace, while Business Central uses custom fields on the page extension model.