Migrate from MRPeasy to Microsoft Dynamics 365 Business Central

MRPeasy Vendors map directly to Dynamics 365 Business Central Vendor records. We extract vendor name, contact details, address, payment terms, and currency from the MRPeasy vendor table and load into the Vendor table. Vendors are imported first because Item purchase terms reference vendor codes — this dependency order must be preserved to avoid orphaned purchase item links during import.

MRPeasy Items map to Dynamics 365 Item records with the Type field set to Inventory Item or Non-Inventory Item based on the MRPeasy tracking flag. Part number becomes Item No.; description, unit of measure, and cost (standard cost on creation) migrate directly. Items are created before BOMs and before inventory levels so that the BOM component lookup is satisfied at import time. The MRPeasy 3000-line CSV cap applies to Items; we chunk large catalogs into sequential import batches and track completion to avoid duplication.

MRPeasy BOMs map to Dynamics 365 Manufacturing Bill of Materials. Each BOM version in MRPeasy becomes a BOM with a version code and status (Draft, Certified). Component lines map with the component Item No., quantity per, and unit of measure. Multi-level BOMs are resolved as nested BOM structures in Dynamics 365. Co-product BOMs and disassembly BOMs require additional mapping to the Byproduct Lines table. BOMs import after all component Items exist.

MRPeasy Routings map to Dynamics 365 Work Centers and Routing records. Each MRPeasy workstation group becomes a Work Center; each operation step in the Routing becomes a Routing Line with Sequence, Work Center No., Run Time, and Setup Time. Overlap and parallel execution flags from MRPeasy map to the Dynamics 365 Concurrent Capacity field. Routings import after Work Centers are created.

MRPeasy Manufacturing Orders map to Dynamics 365 Production Orders. The source Item No. links to the destination Item; the BOM and Routing references are resolved at migration time using the BOM and Work Center mapping. MRPeasy dynamic rescheduling may shift active/open MO dates — we flag these during scoping and advise the customer to close or freeze active MOs before import where possible, then document any post-import date delta for the production planner.

MRPeasy Customers map to Dynamics 365 Customer records. Customer code, name, contact information, address (street, city, state/province, postal code, country), tax registration number, and currency code migrate directly. We create Customer Posting Groups and General Business Posting Groups during configuration so that the customer record is valid on insert. Price Lists attached to customers map to the destination's Sales Prices and Line Discounts tables.

MRPeasy inventory levels per storage location map to Dynamics 365 Item Ledger Entries of type Positive Adjustment. The MRPeasy 3000-line CSV cap applies; a 10,000-item single-site warehouse requires at least four import passes. We chunk large inventory datasets and track which batches have been loaded to avoid duplication. Storage Locations must exist in Dynamics 365 before inventory can be assigned to them — we create these manually or via a pre-migration UI configuration pass before inventory import begins.

MRPeasy Stock Lots with batch numbers, expiry dates, and quantities map to Dynamics 365 Lot No. Information records linked to Item Tracking Codes on the Items. Lot traceability metadata (received status, storage location) migrates as Lot-specific ledger entries. Serial number tracking similarly maps to Serial No. Information records. Items must have an Item Tracking Code configured before lot or serial records can be assigned — we configure tracking codes during the Item phase.

MRPeasy Price Lists hold customer-specific and product-specific pricing. These lines split into Microsoft Dynamics 365 Sales Price records (one per Item-Customer combination with unit price and currency) and Sales Line Discount records (discount percent or amount per Item-Customer group). We preserve the currency, minimum quantity, and effective date range on each price line. Price Lists import after Items and Customers exist.

MRPeasy Transfer Orders migrate to Dynamics 365 Transfer Orders with status preserved (New, Released, Received). MRPeasy Transfer Orders require manual status completion to 'Received' — in-transit orders will land in 'Shipped' status in Dynamics 365 and require manual receipt posting. Transportation costs and waybill information map to the Transfer Line and In-Transit Entry tables. We document pending receipts in the cutover checklist.

MRPeasy Custom Fields (Professional and above) require schema replication in Dynamics 365 as extension fields on the relevant table. MRPeasy field types (free text, number, date, choice) map to the nearest Dynamics 365 field type (Text, Decimal, Date, Option). We capture every custom field definition during discovery and pre-create the extension fields before data migration begins so that values are not silently dropped on import.

MRPeasy user records (name, email, role, active status) map to Dynamics 365 User records. We resolve by email match against the destination Azure Active Directory tenant. MRPeasy role assignments map to Dynamics 365 Permission Sets or Security Groups. Users without a matching AAD account go to a reconciliation queue for the customer's IT admin to provision before record migration resumes.

MRPeasy's general ledger Chart of Accounts maps to Dynamics 365 G/L Account entries. Account type (Income, Expense, Asset, Liability, Equity) maps to the G/L Account Gen. Posting Type and Balance account type fields. Non-standard account codes or custom account types require manual reconciliation against the destination's accounting configuration. We flag any accounts with balances that do not map cleanly to a standard Dynamics 365 account type for the customer's finance team to resolve.

MRPeasy explicitly states that Workstation Groups and Workstations cannot be set up via CSV import — they must be created manually in Settings. This impacts the Routing migration because MRPeasy operations reference workstations by name. We flag these as requiring manual configuration in Dynamics 365 before Manufacturing Orders can be posted to the production floor. We provide a written checklist of all required Work Centers with their capacity, crew size, and efficiency values extracted from the MRPeasy workstation data.