Migrate from Microsoft Dynamics 365 Business Central to Acumatica

G/L Account numbers map 1:1 to Acumatica Account IDs. Business Central's Account Category (Income, Expense, Asset, Liability, Equity) maps to Acumatica Account Type. Posting Groups from Business Central must be translated into Acumatica Account Rules that govern which Subaccount combinations are valid per transaction type.

Business Central's two Global Dimensions (e.g., Department and Project) translate to Acumatica Subaccount segments. The first global dimension maps to the first subaccount segment; the second maps to the second. Shortcut Dimensions 1–8 translate to additional subaccount segments if your Acumatica configuration uses multi-segment subaccounts.

Direct map with attention to Customer Posting Groups. Business Central assigns Payment Terms, Invoice Discount, and General Business Posting Group per customer. Acumatica's Customer record holds Payment Term ID and AR Account lookup; the General Business Posting Group becomes an attribute or custom field unless your Acumatica chart uses separate AR accounts per segment.

Vendor mapping mirrors Customer mapping. Business Central's Vendor Posting Group controls how purchases flow to the general ledger. In Acumatica, Vendor records reference a Payment Term and an AP Account; posting groups are resolved via Acumatica's VendorClass entity. Remit-to addresses migrate as separate Vendor locations.

Item records map 1:1 with costing method preservation. Business Central's Inventory Posting Group controls the inventory account; in Acumatica, each warehouse/site can override the costing method. Lot/serial number setup and shelf life tracking flags carry over. Stock items vs. non-stock items map to Acumatica Item Type: Stock, Non-Stock, or Service.

Business Central service items with resource links map to Acumatica Non-Stock items. If the service also has labor routing or project time tracking, consider creating an Acumatica Non-Stock item paired with a corresponding Labor Code for project billing and cost tracking purposes. Service items that bill at fixed rates map directly while those using time-and-materials require the labor code linkage.

Open Sales Orders migrate with current line status, quantities remaining, scheduled ship dates, and owner assigned. Closed lines are not migrated unless historical reporting requires them. Sales Lines carry the original Item No., quantity ordered, unit price, and discount amounts. Custom fields on Sales Headers and Lines migrate as attributes on the corresponding Acumatica documents.

Open Purchase Orders migrate with quantities remaining to receive, promised delivery dates, and buyer assignment. Drop-ship and special order flags are preserved. If Business Central PO statuses use release status (Open/Released/Finished), Acumatica's Hold flag on PO lines provides equivalent control.

Blanket Purchase and Sales Orders map to Acumatica Blanket Orders. The remaining quantity, expiration date, and pricing terms carry over. Release quantities create regular Purchase/Sales Orders in Acumatica after migration; the blanket relationship is preserved at the header level. Any partial releases completed in Business Central before cutover are reflected as released quantities in Acumatica.

Manufacturing BOMs with version control map to Acumatica BOMs. Single-level and multi-level BOM structures are preserved. If Business Central uses the Production BOM type, Acumatica's Material Kit or Production BOM type is selected based on the manufacturing edition. BOM unit of measure conversions carry over.

Open and scheduled Production Orders migrate with status, quantity, and remaining output. If Business Central production orders use warehouse/location tracking, Acumatica's Site ID on production order lines preserves the location assignment. Released vs. firm status maps to Acumatica's Production Order status (Scheduled, In Process, Completed).

Employee records migrate including name, address, employment type, and cost rate for project accounting. If Business Central uses Employees for time and resource management, Acumatica's Employee record and associated Labor Code carry the same billing and cost rates. Employee address and contact fields map directly.

Currency codes and historical exchange rates with effective-from dates migrate to Acumatica's Currency Rate table. If Business Central uses a service to pull live rates, the migrated rates serve as baseline; Acumatica's rate provider can be configured post-migration for ongoing updates.

Business Central Locations map to Acumatica Sites. Address, default bins, and transit warehouse flags carry over. If Business Central uses zone or bin configurations, Acumatica's warehouse structure (Sites > Buildings > Aisles > Shelves > Bins) can accommodate the same hierarchy.

Historical posted documents (invoices, credit memos, payments) are not migrated as live documents in Acumatica because they have already affected the general ledger. If fiscal periods are still open for adjustment, individual GL entries can be migrated as journal batches. Typically these are archived as reports and the migration focuses on open documents only.