Migrate from MONITOR ERP to Microsoft Dynamics 365 Business Central

MONITOR ERP Customer records map to Dynamics 365 Customer records with address, contact, currency, payment terms, and invoice profile preserved. The customer number in Monitor becomes the Customer number in Dynamics 365; if Monitor uses alphanumeric customer codes that conflict with Dynamics 365's numeric default, we apply a prefix or renumbering rule during import. Business Central uses a single Customer table; Finance and Supply Chain Management maintains CustTable with the same field structure.

Supplier records map 1:1 to Dynamics 365 Vendor records, preserving address, contact, currency, payment terms, and all linked Purchase Orders. Vendor number mapping follows the same prefix or renumbering logic applied to Customers to maintain consistency across the account-numbering scheme.

MONITOR ERP Items with Bill of Materials and routing data decompose into three Dynamics 365 entities: Released Product (the base item with costing and inventory dimensions), BOM Version (linking the finished good to its components with quantity-per relationships), and Production Route (work-centre sequence with setup and run times). We preserve the Monitor BOM version effective dates as BOM Version validity periods and map Monitor work-centre codes to Dynamics 365 Operations Resource Groups.

MONITOR ERP Customer Orders map to Microsoft Dynamics 365 Sales Orders with order lines, delivery dates, pricing, and discount structure preserved. We flag open orders versus closed orders during extraction to prevent duplicate processing: open orders require careful sequencing to avoid duplicate entry if the customer continues entering data in Monitor during migration. Sales Order status in Monitor maps to the corresponding Dynamics 365 Document Status and External Item Status values.

Supplier Purchase Orders map to Dynamics 365 Purchase Orders with vendor line items, expected delivery dates, pricing, and status preserved. Open Purchase Orders in Monitor require coordination with the customer's procurement team to confirm receipt handling in Dynamics 365; if goods have been partially received in Monitor, we map the received quantities to the corresponding Dynamics 365 receipt lines.

MONITOR ERP Production Orders carry embedded routing, work-centre assignments, and lot traceability links that do not map 1:1 to any single Dynamics 365 entity. We decompose each Monitor Production Order into a Dynamics 365 Production Order header (with BOM and Route references), and Job lines (in Finance and Supply Chain Management) or Operations lines (in Business Central) representing each routing step with work-centre, start/end times, and status. Lot traceability from Monitor's production-order-linked lot register maps to InventDim lot and serial numbers in Dynamics 365's inventory tracking dimensions.

Open and historical invoices export via Monitor's configured file paths. Invoice headers and lines map to Dynamics 365 invoice journals with header fields (invoice number, date, due date, currency, amount) and line fields (item number, quantity, unit price, discount, tax) translated to the destination field names. We flag any invoice attachments stored against Monitor invoice records as a manual export requirement since document attachment migration is not available via Monitor API.

MONITOR ERP journal entries export in batches via file export without date-range filtering at the export level. We download the full batch, perform in-house date-range filtering and chunking to respect fiscal period boundaries, and load journal lines into Dynamics 365 General Journal with account codes, debit/credit amounts, posting dates, and voucher numbers preserved. Account codes from Monitor are validated against the destination chart of accounts before insert to flag any undefined account references.

MONITOR ERP account codes, descriptions, and account types export via file. We map these to Dynamics 365 Chart of Accounts entries, noting that Monitor's account-numbering conventions may conflict with Dynamics 365's default numeric structure. We work with the customer during scoping to define an account prefix or renumbering scheme that accommodates Monitor's existing account codes while maintaining fiscal year continuity. Posting groups (Account Schedule categories in Business Central) are configured to align Monitor's account types with Dynamics 365's posting profile requirements.

Inventory positions (quantity by Item, Warehouse, Lot/Serial) export as Monitor stock reports. We map these to Dynamics 365 inventory records with InventDim dimension combinations (Site, Warehouse, Location, Lot, Serial) resolved at migration time. Lot and serial number fields from Monitor's production-order traceability links are mapped to InventDim lot and serial number fields. Any inventory transactions that occurred after the snapshot date are reconciled as a delta migration during cutover.

Bank accounts and cash accounts export via Monitor file paths. We map these to Dynamics 365 Bank or Cash Accounts and reconcile opening balances against the latest Monitor trial balance. If Monitor stores bank statement transactions separately, we flag these for manual import or a bank reconciliation reconfiguration step because Dynamics 365's bank reconciliation feature expects a different statement import format.

MONITOR ERP User records (login, name, role assignments, department) map to Dynamics 365 User records linked to Azure Active Directory, with Worker or Employee records created for HR and organizational purposes. Role assignments in Monitor translate to Dynamics 365 Security Roles and duties; we flag any Monitor role with no direct Dynamics 365 equivalent for the customer admin to configure post-migration. Inactive Monitor users are mapped to inactive Dynamics 365 users pending the customer's cleanup decision.

Documents attached to Customer Orders, Items, or Production Orders in MONITOR ERP are stored within the Monitor file store and are not accessible via the standard API query endpoint. File export configuration varies by Monitor installation and per-user manual navigation. We cannot guarantee complete automated document migration. We flag all document attachment locations during scoping and deliver a manual export checklist with folder structure guidance so that the customer's team can export documents before the migration freeze period.