Migrate from Accolent ERP to Microsoft Dynamics 365 Business Central

Accolent Customer records carry billing/shipping addresses, contact details, account type flags, and payment terms. In Dynamics 365, the customer model splits into Vendor and Customer entities under Finance and Supply Chain Management, or Customer and Contact under Business Central. We extract all address roles (billing, shipping, primary) and map them to the destination's customer address structure. D365 Finance and Operations requires each address to have a single primary purpose — we combine Accolent's separate primary-invoice and primary-delivery flags into a single primary address per role and flag any loss of dual-purpose address data during scoping review.

Vendor master data in Accolent includes address, payment terms, PO defaults, and 1099 settings. We map these directly to Dynamics 365 Vendor records. Vendor lookup in D365 Finance is the VendorId/VendTable entity; in Business Central it is the Vendor card. PO defaults map to Vendor posting groups and purchase policies that we configure before loading.

Items are the core inventory object in Accolent, supporting multiple warehouse locations, cost layers (FIFO, Average, Standard), and reorder points. We map item records including pricing tiers and BOM links to D365 Product (Business Central) or Released Product (Finance and Supply Chain). Costing method, inventory dimensions (Site, Warehouse, Location, Color, Size), and unit-of-measure conversions are preserved through the costing version configuration step before items are released to legal entities.

Open and historical sales orders in Accolent carry header fields (customer reference, order date, terms, shipping method) and line items (item number, quantity, price, warehouse). We extract all order headers and lines, flagging fulfilled versus open status so the destination sets the appropriate document status. For D365 Finance and Operations, we resolve the CustAccount, InventTransId, and InventDimId references before inserting. For Business Central, we resolve Sell-to Customer No. and Location Code before posting.

PO records in Accolent include vendor reference, line items, receipt status, and amendment history. We extract PO headers and lines, mapping receipt-stage flags to the destination's Receipt status or Posting status. D365 F&SCM uses PurchTable/PurchLine with InventDim for inventory dimensions; Business Central uses Purchase Header/Purchase Line. We preserve receipt-stage status so partially-received POs are not inadvertently re-opened in the destination.

Accolent uses a structured GL chart with account numbers, names, types (Asset, Liability, Expense, Revenue), and optional cost-center assignments. We extract the full chart and map account codes to D365 MainAccount (F&SCM) or G/L Account (Business Central), preserving account type, posting definitions, and any intercompany flags. Cost-center assignments map to D365 Financial Dimensions if the customer uses dimensional accounting, which we confirm during scoping.

Outstanding invoices and credit memos represent live payables and receivables that cannot be re-invoiced — they must land as existing open balances in D365. Accolent does not expose a dedicated AP/AR aging export. We extract invoice and credit-memo headers with outstanding amounts and map them to D365's open-balance or beginning-balance mechanism (Vendor Invoice Journal for AP, Customer Invoice Journal for AR in Business Central; open transaction records in F&SCM). Any record with an original invoice date more than 90 days in the past is flagged for customer review before committing. Exchange rates on historical foreign-currency invoices are preserved from the original transaction date.

Accolent stores multi-level BOMs with parent-component relationships, quantity-per, routing steps, work-center assignments, and phantom BOM flags. We extract the full BOM tree and flatten it for the destination. D365 Finance and Supply Chain uses a MtBOM/SKB/MFB type model with separate BOM and Route entities; Business Central uses a simpler BOM with lines and an optional routing. We flag any BOM with more than three levels for manual review to prevent circular-reference errors in the destination MRP system. Phantom BOM flags in Accolent map to the Phantom BOM type in D365 F&SCM.

Accolent supports multiple warehouse sites with bin/shelf location tracking. We extract warehouse definitions and location codes and map them to D365 InventLocation (warehouse) and InventDim (location) entities. Location status, zone assignments, and picking priorities are preserved where Accolent exposes these fields. For customers using D365 WMS module, we configure warehouse configuration including receiving and shipping locations before item migration.

Historical GL transactions in Accolent include date, account, debit/credit amounts, and source references. We extract posted journal entries and map them to D365 LedgerJournalTrans. Original posting dates and voucher numbers are preserved. For year-end migrations, we close the Accolent fiscal year in the GL before extraction to ensure the destination opens with correct beginning balances. Currency and exchange rate information is carried forward for foreign-currency transactions.

Fixed-asset records in Accolent include acquisition cost, acquisition date, depreciation method (straight-line, declining balance, units-of-production), accumulated depreciation, salvage value, and asset class. We extract asset records and map them to D365 Fixed Assets. In F&SCM, assets use AssetBook with separate book definitions for tax and GAAP depreciation; in Business Central, Fixed Asset cards carry the primary depreciation setup. We preserve the accumulated depreciation balance and the net book value as of the migration effective date.

Accolent user accounts, roles, and access-control assignments are stored in the database. We extract user records and role definitions and map them to D365 User Management and Security Roles. Because D365 security is role-based rather than permission-matrix-based, we deliver a written mapping of each Accolent role to the nearest D365 security role (for example, Accolent Order Entry role maps to D365 Sales Order Processor or a custom role with specific duties). The customer's admin provisions D365 users and assigns roles after reviewing the mapping.

Accolent tax codes define rates and applicability rules for sales and purchasing transactions. We extract the tax-code master and map them to D365 Sales Tax codes (F&SCM) or Tax Groups and Tax Business Groups (Business Central). Jurisdiction-specific tax codes are mapped to D365 Tax Codes with the appropriate sales-tax or VAT configuration. We flag any Accolent tax code with a jurisdiction not supported in D365's standard tax configuration for manual setup review.