Migrate from Adaptive to Microsoft Dynamics 365 Business Central

Adaptive Customer records map to D365 Finance and Supply Chain CustCustomerV3 or Business Central Customer table. The mapping preserves customer name, address, contact details, and tax registration number. Multi-address structures in Adaptive (billing address, shipping address) map to LogisticsPostalAddress with AddressRelationship types set during import. Customer payment terms and credit limits transfer to D365's Customer posting profile configuration.

Adaptive Supplier records map to D365 VendVendorEntityV2 in Finance and Supply Chain or Vendor in Business Central. Payment terms, bank account details, and W-9 or tax ID fields transfer to the vendor posting profile. We flag any supplier records with incomplete bank detail fields during the data audit phase because D365 enforces stricter required-field requirements on vendor banks for payment processing.

Adaptive account codes and account type flags map to D365 Main Account records. We transfer the full account structure (account number, name, account type, posting type, dimension defaults) and note that D365 requires explicit account type mapping (Assets, Liabilities, Equity, Revenue, Expense) and Financial Dimension framework setup before the chart of accounts is functional. Account structure definitions in D365 (segments, account formats) must be configured before import because the COA import validates against the defined format.

Adaptive open AP and AR invoices map to D365 CustTrans and VendTrans via the Free text invoice, Customer invoice journal, and Vendor invoice journal entities. The invoice status field (Open, Partial, Closed) maps to the D365 TransactionStatus field, and outstanding balance amounts are validated against D365 currency and decimal precision settings. We sequence AP and AR import to run after the Chart of Accounts and before any payment journal import to satisfy the financial dimension requirements on journal lines.

Adaptive purchase orders with header and line structure map to D365 PurchTable and PurchLine. PO status (Draft, Submitted, Confirmed, Received, Invoiced) maps to the D365PurchStatus enum. Header-level charges (freight, handling) transfer to PurchLine with a line property or InventTransId reference. Lines referencing Adaptive Stock Items must import after the Item master is established to satisfy the InventDim dimension constraints on purchase order lines.

Adaptive sales orders map to D365 SalesTable and SalesLine with status mapping (Quotation, Confirmed, Delivered, Invoiced). Sales agreement references transfer as a related agreement or blanket order if the customer's D365 configuration includes the Sales agreement module. Line-level discounting, charges, and tax groups migrate with the line record and are validated against D365's tax group configuration during the sandbox reconciliation phase.

Adaptive Stock Items (SKU, description, unit cost, current quantity) map to D365 EcoResProduct and InventTable. BOM structures, routing, and warehouse-specific quantities are flagged for manual configuration post-migration because D365 manages warehouse dimensions (Site, Warehouse, Location, Pallet) as separate dimension entities that require site and warehouse setup before inventory can be allocated. Unit of measure conversions transfer from Adaptive's UOM definitions to D365's UOM class and unit sequence configuration.

Past journal entries from Adaptive carry fiscal period and journal entry date metadata that requires period validation against D365's fiscal calendar. We flag any journal entries with posting dates falling into closed or permanently closed D365 fiscal periods and surface these in a pre-migration reconciliation report for the customer to resolve (either open the period in D365 or re-date the entry). Voucher numbers and entry descriptions preserve for audit trail continuity. Entries spanning D365 fiscal year boundaries require re-dating to align with the D365 fiscal calendar structure.

Adaptive multi-currency customer and vendor balances require D365 currency configuration and exchange rate table population before invoice import. We extract the currency code list and balance amounts from Adaptive, configure the corresponding currencies in D365 General ledger, and populate the exchange rate table with the rates applicable at the balance sheet date. Any balance denominated in a currency not configured in D365 is flagged before the currency setup phase so that the customer can add it to the currency list before invoice import begins.

Adaptive document attachments (invoices, purchase orders, statements stored as file references or blobs) migrate alongside their parent record. Files exceeding D365's typical size threshold for document handling are flagged in the data audit. We recommend enabling SharePoint document management in D365 before migration if Adaptive stores a high volume of attachments, so that the document storage location is correctly provisioned at migration time.

Adaptive user accounts (name, email, role assignments) map to D365 User records. Role assignments transfer as SecurityRole assignments in D365, but we flag them for reconciliation because Adaptive's internal role model does not map directly to D365's granular role and duty privilege structure. Users without an email match in D365 go to a reconciliation queue for the customer's admin to provision before the main migration phase begins.

Adaptive's fiscal period definitions map to D365's Fiscal calendar and Period status (Open, Closed, Permanently Closed). We extract Adaptive's fiscal year start date, period length, and period end dates and configure the corresponding accounting calendar in D365 before any journal or transaction import. Period status is set to Open for all receiving periods; permanently closed periods are flagged for manual resolution before any entry is posted to them.