Migrate from Grade to Microsoft Dynamics 365 Business Central

Grade Customers map to D365 Customer with party ID, name, address, and contact information preserved. D365 requires a Customer party record (DirParty) before any Sales Order or Invoice can reference it. We extract the customer name, primary email, billing and shipping addresses, and any credit limit or payment terms, then insert the party and customer records in dependency order. Grade customer-specific custom fields map to D365 Extension fields (FieldValue) on the customer entity. If Grade supports customer types (e.g., consumer vs. B2B), we map those to the CustomerGroupId in Business Central or the CustGroup in Finance and Supply Chain.

Grade Vendors map to D365 Vendor with party ID, name, address, and W-9 or tax registration fields preserved. D365 enforces a Vendor account number as the primary key. We extract the vendor name, primary contact, payment terms, and bank account details, then insert the party and vendor records before any Purchase Order or Invoice import. Grade vendor custom fields migrate to Extension fields. Tax exemption status from Grade maps to the Tax1099 field and vendor Tax1099Type in D365 Finance.

Grade Products or Items map to D365 released products. We extract the product name, item number (Grade SKU maps to ItemNumber), product type (item vs. service), unit of measure, and any costing method (standard, average, FIFO). D365 requires a product record before an inventory transaction can reference it. For items with costing, we set the cost price as the initial inventory cost and, if Grade holds opening stock quantities, we create an inventory opening transaction in D365 rather than a standard receipt.

Grade Sales Orders map to D365 Sales Order with order number, order date, customer reference, and line-level item/qty/price preserved. We resolve the D365 Customer account number from the Grade Customer mapping, and the D365 Item number from the Grade Product mapping, at migration time. Order status (open vs. closed) maps to the SalesStatus field. If Grade holds partially shipped orders, the D365 order carries the shipped quantity as a negative line and the open quantity as the positive line.

Grade Purchase Orders map to D365 Purchase Order with order number, order date, vendor reference, and line-level item/qty/price preserved. We resolve the D365 Vendor account number from the Grade Vendor mapping. If Grade tracks approval status on POs, we set the PurchStatus to Pending or Approval required on open orders and skip closed or received orders, which migrate as posted receipts. Multi-line Grade POs with multiple delivery dates map to separate D365 purchase order lines.

Grade Sales Invoices map to D365 Customer Invoice with invoice number, invoice date, due date, customer reference, and line-level totals preserved. D365 enforces that an invoice references an open or posted Sales Order, or creates a free-text invoice if no order linkage is needed. We prefer order-linked invoices where Grade provides the linkage. Closed/cancelled invoices in Grade are not re-posted; we record the original posted amounts as a note and flag them for opening-entry creation in D365.

Grade vendor invoices and bills map to D365 Vendor Invoice with invoice number, vendor reference, invoice date, and line-level amounts preserved. We resolve the D365 Vendor account from the Grade Vendor mapping. If Grade holds invoice approval workflows, open invoices migrate as pending approval and cancelled invoices are excluded. Invoice totals, tax amounts, and payment terms transfer to the D365 vendor invoice entity.

Grade customer receipts and vendor payments map to D365 Payment Journal lines. We extract the payment date, amount, customer or vendor reference, payment method, and bank account. D365 requires a resolved Customer or Vendor account and a valid bank account for each payment line. We do not re-open or reverse original Grade transactions; we create new D365 payment records that clear the aged receivables or payables as of the migration date.

Grade GL accounts map to D365 MainAccount in Finance and Supply Chain, or G_L Account in Business Central. This is a configuration step rather than a data migration because D365 requires the account structure to be defined before any transactional data can post. We extract the Grade account number, name, type (asset, liability, equity, revenue, expense), and posting definition, then configure the D365 COA with the equivalent MainAccount structure. If Grade holds account groups or categories, we map these to D365 Account Categories for financial statement grouping.

Grade closed-period GL entries are not re-posted. Instead, we capture period-end account balances from Grade and create D365 opening period journal entries (a balance carryforward) for each account in the configured COA. This approach avoids duplicate posting while preserving the financial position as of the migration cutoff date. The opening entry debit or credit amount matches the Grade trial balance. We exclude Year 1 through Year N detail lines and only carry forward the ending balance per account.

Grade warehouse or location records map to D365 InventLocation with warehouse ID, name, address, and site reference. D365 requires the warehouse to be defined before inventory transactions (receipts, shipments, or transfers) can reference it. If Grade tracks bin or location hierarchy within a warehouse, we map that to D365 WMS location or configure InventLocation with the appropriate InventoryDimension field.

Grade on-hand inventory quantities map to D365 inventory on-hand records using InventDim (the combination of Site, Warehouse, Location, and Batch) and InventSum. We set the Item number from the Grade Product mapping, the dimension combination from the Grade location mapping, and the quantity from Grade. This is a configuration and opening-entry step rather than a transactional receipt, establishing the starting on-hand position without re-posting historical receipts.

Grade currency codes and historical exchange rates map to D365 Currency and ExchangeRate tables. We extract the ISO currency code, currency symbol, and any stored exchange rates from Grade. D365 maintains its own exchange rate table; we populate historical rates if Grade holds them, enabling accurate revaluation of open foreign-currency transactions during migration. Single-currency Grade instances (most likely) map trivially to the D365 base currency with no conversion needed.

Grade tax groups or tax codes map to D365 Tax Group with the applicable TaxGroupLine entries. We extract the tax group name, rate, and applicability (sales vs. purchase) from Grade and configure the equivalent D365 Tax Group and Tax Code. If Grade holds tax exemption certificates by customer or vendor, we record these as notes on the Customer or Vendor entity and set the appropriate exemption flag in D365.

Grade payment term definitions (e.g., Net 30, 2/10 Net 30) map to D365 PaymTerm with due date calculation logic (number of days, discount percentage, discount days). We extract the term name, due days, and early payment discount from Grade and configure the equivalent D365 payment term before customer or vendor invoice import.

Grade bank account records map to D365 BankAccount with account number, bank name, SWIFT/BIC, and IBAN where available. D365 requires a bank account for payment journal lines and reconciliation. We extract the bank account details from Grade and configure the D365 bank account as a configuration step before any payment or receipt import.