+1 480 485 7373
Microsoft Teams
How Acumatica structures its data, and where Business Central differs
Acumatica pairs every G/L account with a subaccount. The subaccount is a segmented key, often department, location or product line. Over time, many firms build up hundreds of account and subaccount pairs. Business Central keeps the chart of accounts lean and carries that analysis in dimensions instead. Two global dimensions sit on every entry. Up to eight shortcut dimensions show on entry screens. Dimension sets hold more beyond that.
In Acumatica, customers and vendors share one business account. So one company can play both roles on a single record. In Business Central, a customer and a vendor are separate cards. You can tie both to one contact when you want the link visible. Acumatica's customer, vendor and item classes carry defaults such as terms and posting accounts. In Business Central, posting groups plus customer, vendor and item templates do that job.
Branches are the call that needs the most thought. A branch may become a location, a dimension value or a separate company. It depends on whether the branch keeps its own balance sheet. Stock and non-stock items map to inventory, non-inventory or service items. Warehouses and their locations become locations and bins. Lot and serial classes become item tracking codes.
Acumatica screens and entities against Business Central
Balances, open items and history get three different treatments
Trial balance at cutover
General ledger balances arrive as one opening journal at a period end. Each line carries the account and the dimension values that replace your subaccounts.
- ✓Prior-year monthly net changes if you want comparative financial reports
- ✓Bank balances matched to the last reconciled statement
- ✓Inventory value tied back to the quantities loaded
Documents still in play
Unpaid AR invoices, open AP bills, unapplied payments and credit memos load one by one. As a result, aging and payment application work from day one.
- ✓Open sales and purchase orders with remaining quantities
- ✓Customer prepayments carried as their own entries
- ✓Stock by location, bin, lot and serial number through item journals
What you look back at
Posted Acumatica transactions rarely justify line-level replay. Most companies keep summarized G/L history in Business Central and read older detail from a structured export.
- ✓Customer and item sales summarized by month
- ✓Closed purchase orders exported to a searchable archive
- ✓Audit trail detail kept outside the new ledger
Rebuild these in Business Central instead of migrating them
Customization projects
Acumatica customization projects and custom screens are platform code. Each one gets a fit check. The answer is a standard feature, an AppSource app, or a per-tenant AL extension written for the new system.
Generic inquiries
Generic inquiries have no importable equivalent. Common ones become saved list views with filters. The heavier ones become Power BI reports or analysis mode views.
Approval and assignment maps
Approval maps become approval workflows. Notification rules move to workflow responses or Power Automate flows.
Payroll
Business Central has no US payroll module. If you run Acumatica payroll, you choose a payroll provider. Its journals then post into Business Central through an import or connector.
Replacing generic inquiries, dashboards and ARM reports
Acumatica users lean heavily on generic inquiries and the Analytical Report Manager. Before cutover in an Acumatica to Business Central migration, we list every inquiry and report someone actually opens. We note each one's owner, then sort each into one of four homes. One is a list view or analysis mode. Another is a financial report, the feature Microsoft once called account schedules. A third is a Power BI report on the Business Central connector. The last is retirement, because nobody reads it.
Statements built in ARM usually rebuild well as financial reports. Row definitions work by account range, and column definitions by period and dimension. Day-to-day dashboards tend to land in Power BI. There, Microsoft's own reports for finance, sales, buying and stock give you a starting point to adjust.
Cutover from Acumatica, one controlled stage at a time
- 1
Freeze the structures
Agree the dimension design, posting groups and number series, and stop creating new subaccounts in Acumatica.
- 2
Extract with scenarios, inquiries or the API
Master data and open items come out through export scenarios, generic inquiries in Excel, or the REST API. We then reshape them into Business Central configuration packages.
- 3
Trial loads in a sandbox
Each load runs in a sandbox. Finance then checks customer, vendor and stock totals against Acumatica.
- 4
Close the last Acumatica period
Post the final transactions and close the financial period. Then run the trial balance, AR aging, AP aging and inventory valuation that the opening loads must match.
- 5
Load, prove, go live
Load production and tie each subledger to its G/L control account. Then sign off and open Business Central for posting.
Acumatica to Business Central questions
Is Business Central a step down from Acumatica?
Not for most mid-sized companies, but it is a different shape. Both cover finance, distribution, stock, manufacturing and projects at a similar depth. The strongest reasons to move are the tie to Microsoft 365 and the size of the partner and app ecosystem. Fit with other Microsoft systems you already run also counts. If Acumatica fits and the team is happy, we will say so.
Can we keep our subaccounts exactly as they are?
Yes in substance, though not in form. Each subaccount segment becomes a dimension, and each segment value becomes a dimension value. So reporting by department or location still works. What changes is that you no longer keep an account and subaccount pair for every mix. Default dimensions and dimension combination rules control what users may post.
What happens to customers who are also vendors?
They become two records in Business Central: a customer card and a vendor card. Both can link to one contact, so sales and purchasing both see the link. If you offset receivables against payables today, the usual approach is a general journal entry. It clears one balance against the other, and we set that routine up with your controller.
More Acumatica to Business Central migration questions
Do we lose our Acumatica history?
No, but you decide where it lives. Summarized G/L history can load into Business Central so year-over-year reports work from the start. We usually export the detail to a structured archive before the subscription ends. Replaying every line adds cost and risk for records people rarely open.
How do we extract data if we are on Acumatica cloud?
Through the tools Acumatica gives every tenant. Export scenarios, generic inquiries exported to Excel and the REST API cover master data and open items. We script the extraction rather than rely on one manual export. So trial loads repeat with fresh data right up to the final cutover.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.