+1 480 485 7373
Microsoft Teams
Should an Intacct company move at all?
Be honest about the reason before starting. Intacct is a strong financial system. If your pain is purely reporting, cleaning up the dimension design often gains more than changing ledgers. The companies that gain most from Business Central have grown into physical operations. Think of stock in several warehouses, or assembly and production. Think of buying that needs receiving and landed cost, or field and project work tied to stock. Intacct usually handles those with bolt-on products. The joins between them are where the cost and the errors live.
The other common driver is Microsoft 365. Teams, Outlook and Excel integration, Power BI, Power Automate and Copilot sit natively beside Business Central. So a company that already runs on Microsoft tools often wants finance in the same family. If none of those apply, we will say so on the first call.
Intacct objects against their Business Central counterparts
Entities, shared customers and consolidation
By default, Intacct entities share one customer and vendor list and one chart of accounts. The top level can also post across them. Business Central treats each company as its own set of tables. That gives a cleaner audit trail per legal entity, but you must keep shared masters in step. Business Central has a master data management feature. It can sync customers, vendors, items and the chart of accounts from a source company to the others. We decide field by field what they share and what each entity owns. Payment terms and tax areas are typical examples.
Consolidation runs as its own company that imports balances from each business unit. It translates foreign subsidiaries at the rates you set. The difference posts to the accounts you choose. Eliminations post as journals in the consolidation company. In the first month after a Sage Intacct to Business Central migration, we run the consolidation beside the final Intacct statements. That way we explain any difference before the board sees Business Central numbers.
Intacct features that need a planned replacement
- ✓Interactive Custom Report Writer reports, rebuilt as financial reports or Power BI pages
- ✓Dashboards and performance cards, replaced by role centers and Power BI dashboards
- ✓Smart events that send emails, rebuilt as Power Automate flows or Business Central workflows
- ✓Approval rules on bills, purchase requisitions and journals, rebuilt as approval workflows
- ✓Time and expense entry, moved to time sheets or an expense app that posts into Business Central
- ✓Scheduled report emails to managers, replaced by scheduled Power BI subscriptions or job queue reports
Getting the data out of a hosted system
- 1
Agree the export scope early
Sage hosts Intacct, so the data leaves through its CSV exports, report exports and web services API. Decide what you need before your subscription end date, not after.
- 2
Map dimension to dimension
List every Intacct dimension, its values and the entities that use it. Then agree the Business Central dimension and code for each.
- 3
Load masters per company
Customers, vendors, items, projects and the chart of accounts load into the source company through configuration packages. From there they sync outward.
- 4
Bring open items and balances
Open AR and AP documents come across per entity with their dimensions. Next, each entity's trial balance posts by account and dimension.
- 5
Archive the rest
Export detailed history, attachments and audit trails to storage you control, since read access ends with the subscription.
Before you leave Sage Intacct
Will our Intacct dimension reporting survive the move?
Yes, as long as we map the dimensions deliberately rather than copy them blindly. Business Central posts dimension values on every ledger entry, so departmental and location reporting carries straight over. Customer, vendor and item dimensions disappear because the ledger records those natively. You do have to rebuild report layouts, since Business Central cannot import Intacct report definitions.
Do we need one Business Central company per Intacct entity?
Usually yes, one company per legal entity is the cleanest design. It keeps each entity's tax, banking and audit trail apart. It also matches how Business Central handles consolidation and intercompany work. Some entities are just divisions of one legal company. For those, one company with a division dimension is simpler. We decide this entity by entity in the design workshop.
How do we handle revenue recognition that Intacct automates?
It depends on how complex your contracts are. Business Central deferral templates cover simple straight-line recognition over a service term. Multi-element contracts with ASC 606 allocation usually need an AppSource subscription billing or revenue app. We test your real contract examples in it before we recommend it. We load open deferral balances at cutover with their remaining schedules.
More Sage Intacct to Business Central migration questions
Can we keep read access to Intacct after go-live?
Only while the subscription runs, which is why the archive matters. Many companies keep a reduced subscription for a period to cover the first audit. Others export everything and rely on the archive. Either way, we list the reports and detail your auditors will ask for. Then we export those in a readable format before access ends. That decision belongs in the plan from the start.
Is there a Microsoft tool that migrates Intacct straight into Business Central?
We do not plan around one; we move Intacct data with configuration packages, the Business Central APIs and scripts. In a Sage Intacct to Business Central migration, the real design work sits in mapping entities, dimensions and inter-entity accounts. No generic tool makes those decisions for you. Scripted loads also let us rehearse the migration in a sandbox as many times as needed.
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.