Migrate from Masterplan to Microsoft Dynamics 365 Business Central

Masterplan Customer records map to Dynamics 365 Customer with full billing and shipping addresses, payment terms, credit limit, and currency. We use the customer account number as the dedupe key and create the Customer record before any related transaction import. In Finance and Operations, customer records belong to a specific legal entity; in Business Central, customer numbering is across-company consistent. We confirm the destination legal entity assignment during scoping. Payment terms map from Masterplan's terms code to the Dynamics PaymentTerm reference entity.

Masterplan Vendor records carry W-9 data, 1099 eligibility flags, address, and payment terms. We map these to the Dynamics 365 Vendor entity with the vendor account number as the dedupe key. In Finance and Operations, vendor records are legal-entity-specific and require the same vendor record to be created per operating unit if the customer operates across entities. We flag any cross-entity vendor scenario during scoping for the customer's finance admin to confirm before import.

Masterplan Items span Finished Goods, Raw Materials, Components, and Services with distinct costing methods. Each item type maps to the corresponding Dynamics 365 Product with the costing method preserved—Standard, FIFO, Moving Average, or Lot Cost for manufacturing items. Item number from Masterplan becomes the Dynamics 365 Product number. We flag any user-defined unit of measure conversions that require a UOM schedule setup in the destination before item import.

Masterplan GL account numbers, names, types (Asset, Liability, Equity, Revenue, Expense), and optional department or cost-center rollups map directly to Dynamics 365 Main Account records. Account number is the dedupe key. If Masterplan uses cost center as a separate segment, we discuss whether to map it as a main account dimension (Financial Dimensions in Finance and Operations) or as a department entity before extraction. The full account hierarchy is extracted intact and loaded first, before any journal entries.

Outstanding receivables include invoice number, amount, due date, and aging bucket. We normalize Masterplan aging buckets to standard 30/60/90/120-day buckets, though these vary by customer configuration. We ask the customer to decide during scoping whether to import open invoices as posted transactions (requiring a journal import) or leave them as open sales orders to be invoiced post-migration in Dynamics 365. Any invoice tied to a closed work order or outside the lookback window is flagged as potentially out-of-scope.

Outstanding payables follow the same normalization and scoping approach as AR. We map invoice number, amount, due date, and vendor reference. Any open invoice tied to a closed purchase order is flagged explicitly. In Finance and Operations, AP aging is driven by the invoice and payment terms; we import as invoice journals or open purchase orders depending on whether the customer prefers accrual-posted or PO-receipt-based AP tracking.

Open Sales Orders carry line items, quantities, unit prices, and fulfillment status. We flag partially shipped orders explicitly in the migration manifest so that the customer's operations team handles fulfillment status in Dynamics 365 at cutover. Sales order headers carry the customer account, currency, payment terms, and delivery address. Sales order lines carry the item number, quantity, unit price, and warehouse. We resolve the item number to the Dynamics 365 Product reference during import, and we validate warehouse codes against the destination warehouse setup.

Open Purchase Orders from Masterplan map to Dynamics 365 Purchase Order with vendor, line items, quantities, and receipt status. Partially received orders are flagged for the customer to manage at go-live. In Finance and Operations, PO lines can reference product receipts and invoices separately; we preserve the receipt status as a custom reference field and defer invoicing to the accounts payable team post-cutover. Any PO linked to a closed vendor account is flagged for review.

On-hand quantities per warehouse location and bin in Masterplan map to the Dynamics 365 inventory on-hand entity, with warehouse code mapped to the destination warehouse structure. We flag bin-level inventory that has no matching warehouse in the destination, requiring a warehouse setup review before on-hand import. Lot numbers and serial numbers transfer as available; expiration dates on lot-controlled items require lot number setup in the destination.

Multi-level BOMs with component quantities, scrap factors, phantom assemblies, and routing steps require careful extraction and transformation. We extract the full BOM tree from Masterplan and map each level to a BOM Version in Dynamics 365 Finance and Supply Chain Management or a Production BOM in Business Central. Phantom assemblies are flagged explicitly for the customer's engineering team to decide whether to preserve them as phantom BOM lines or flatten them. BOM routing steps (work centers, labor hours, machine time) map to Operations Resources and Route lines if the destination includes the Production module.

Work orders track status (Released, In Process, Complete, Closed), routing steps, labor hours, and material allocations. We preserve all status history and associate backflush transactions with the corresponding production order. Open and In-Process orders migrate as Active or Scheduled Production Orders; Completed and Closed orders migrate as Completed Production Orders with actuals. The BOM reference on the production order must resolve to a valid BOM Version in Dynamics 365 before import, so BOM migration precedes work order migration.

Masterplan addresses carry multiple roles per customer (invoice, delivery, primary). Finance and Operations supports address roles but marks only one as primary per usage type. We extract all addresses and consolidate multiple primary-invoice or primary-delivery addresses into a ranked list, importing the first as primary and flagging overflow addresses for manual assignment post-migration. Business Central supports multiple addresses per customer with roles. We confirm the address strategy with the customer during scoping.

Masterplan item pricing including list prices, volume-based breaks, and customer-specific pricing agreements map to Dynamics 365 Price Groups, Customer Price Groups, and Trade Agreements. We extract all active price lines and import them as trade agreements with the appropriate validity dates. Future-dated price agreements are imported with their effective-from and expires-after dates to maintain continuity at cutover.

Masterplan user accounts and owner assignments on records map to the corresponding Dynamics 365 User record. We extract distinct owner IDs from Customers, Vendors, Sales Orders, Purchase Orders, and Work Orders and match by name or email to the destination User table. Any Masterplan Owner without a matching Dynamics User goes to a reconciliation queue for the customer's admin to provision before record import. Active/inactive status on users maps directly.