Seven Signals You’ve Outgrown Business Central

If you are wondering whether you have outgrown Business Central for Dynamics 365 Finance, do not start with revenue or employee count. Look at operational complexity instead. Here are seven signals worth taking seriously.

Outgrowing an ERP does not feel like a system failure

Business Central can support sophisticated organizations.

It includes financial management, multiple companies, intercompany transactions, consolidation, manufacturing, supply planning and warehouse management. Microsoft describes Business Central as primarily serving common processes in small and midsize companies while also supporting more complex processes including manufacturing and directed warehouse management.

So growth alone does not mean you have outgrown it.

The problem starts when your operating model repeatedly requires capabilities outside Business Central’s natural design. You can usually solve one gap with an extension. You can solve another with Power BI. Another might justify an ISV.

Eventually, however, the architecture itself becomes the problem. The question is not whether Business Central can technically be made to do something. It is how much work you are doing to keep making it do it.

Signal 1: Entity count and intercompany volume

Having multiple companies in Business Central is not, by itself, a reason to move.

Business Central supports consolidation across companies, including companies with different charts of accounts. It can translate currencies, consolidate dimensions and include partially owned businesses.

So do not accept “you have ten companies, therefore you need Finance” as analysis.

Instead, look at what happens between those companies:

• How many intercompany transactions require intervention?
• How complicated are eliminations?
• Do entities use different charts of accounts?
• Different fiscal structures?
• Different currencies?
• How much reconciliation takes place outside the ERP?

Dynamics 365 Finance provides a deeper legal-entity and consolidation architecture, including scenarios involving multiple charts of accounts, different fiscal calendars, multiple reporting currencies and eliminations.

The signal is not entity count. It is the amount of financial machinery required to manage those entities.

Signal 2: Statutory reporting where the localization is thin

Business Central has broad geographic availability, but the localization model varies by country.

Microsoft directly provides local functionality for countries including Canada, the United States and Mexico. In many other markets, Business Central availability depends on partner-developed localization applications built on the international version.

That does not make a partner localization bad. It does mean you need to inspect what you are relying on.

If your organization operates across several jurisdictions and local finance teams continually require additional extensions, custom reports or manual processes to meet statutory requirements, localization becomes part of the ERP decision.

Finance also provides structures for organizations that need global and local charts of accounts. Microsoft documents models where legal entities maintain local accounting structures while the organization consolidates into a global chart.

If statutory complexity is driving the discussion, assess it country by country.

Signal 3: Transaction volume and concurrent users

This one gets oversimplified constantly.

There is no Microsoft rule saying Business Central stops working at a specific number of users. Do not invent one.

Business Central Online is a cloud service with operational limits covering areas such as client connections, reports, queries, background tasks and web-service requests. For example, Microsoft currently documents web-service limits of 6,000 requests per five-minute sliding window per user and five concurrent requests per user, with additional requests queued.

Those are service limits. They are not recommendations to migrate to Finance.

Measure posting times, job queues, API traffic, peak concurrent usage, report execution, integration throughput and database growth. Then tune it. If performance improves, you had a performance problem. (We cover that diagnosis in more detail in why Business Central reports go slow.)

If the organization keeps introducing workloads that fight Business Central’s architecture despite good design and tuning, then scale becomes part of the product discussion.

Signal 4: Manufacturing or warehouse complexity beyond BC’s model

Business Central Premium includes legitimate manufacturing functionality. Its warehouse functionality includes bins, receipts, shipments, picks, put-aways, movements and more advanced warehouse configurations.

Do not replace it because somebody says Business Central “doesn’t really do manufacturing.” It does. The question is whether it models your manufacturing.

Dynamics 365 Supply Chain Management goes deeper in areas such as advanced warehouse work, location directives, work templates, wave processing, transportation integration and complex manufacturing warehouse processes.

Its planning architecture also supports master plans, multisite planning and Planning Optimization. If you keep adding software because Business Central cannot naturally represent how your plants or distribution centres operate, pay attention.

Signal 5: The number of ISVs holding the solution together

ISVs are not a warning sign by themselves. The Business Central ecosystem is one of its strengths.

A strong vertical solution can be a better decision than moving to a much larger ERP just to obtain one capability. The problem is dependency. Map every extension in your environment. For each one, document what business process it owns, what it integrates with, who supports it and what happens if it stops working. Then look at the whole picture.

If order processing depends on one vendor, warehousing on another, planning on another, consolidation on another and manufacturing execution on another, you no longer have one ERP. You have an integration architecture with Business Central in the middle. That can still be the right architecture.

But it should be a deliberate decision, not something accumulated one extension at a time.

Signal 6: Planning, consolidation and allocations live entirely outside BC

Business Central does not need to perform every analytical process itself. Moving reporting to Power BI or Fabric can be good architecture.

The signal appears when core financial and operational processes have moved outside Business Central because the ERP cannot support the way the organization now operates. Business Central has native consolidation functionality. It also has native manufacturing and supply-planning capabilities.

If finance ignores the consolidation functionality and maintains the real process in a collection of spreadsheets, find out why. The same goes for planning. Sometimes the answer is that Business Central was never configured properly.

Sometimes the business has genuinely moved beyond what it provides.

Signal 7: A customization backlog that never shrinks

Every ERP has a backlog. The warning sign is the type of request entering it.

If the requests are refinements, automation and usability improvements, that is normal. If they repeatedly ask Business Central to imitate capabilities from a different class of system, the backlog is telling you something. Look at the last 12 months.

Categorize requests into configuration, reporting, integration, genuine competitive differentiation and modifications required because standard Business Central cannot model the process. If it keeps growing, stop treating every ticket as an isolated requirement.

You may have a platform-fit problem.

Score it before you shop

Do not score yourself against an arbitrary internet checklist. Build the score from your actual operating model.

For each of the seven signals, document:

• What happens today.
• How many people or entities it affects.
• How frequently it occurs.
• The manual effort involved.
• The software or customization currently compensating for it.
• The cost and business impact when it fails.
• Whether standard Business Central can solve it with better configuration.

You should end up with evidence, not a score of “6/7, therefore buy Finance.”

Then compare three options: fix Business Central, extend Business Central, or change platform. If you are at that stage, our Business Central vs. Dynamics 365 Finance comparison walks through where the two products actually differ.

Five reasons companies move up too early

There are also plenty of bad reasons to move from Business Central.

1. Revenue increased. Revenue is not an ERP requirement.
2. Headcount increased. More employees do not automatically create more ERP complexity.
3. One report is slow. Tune the report.
4. The implementation is messy. A failed Business Central implementation does not prove Business Central was the wrong product.
5. Finance has more features. It does. You will also have to implement and own the additional architecture you choose to use.

A larger ERP does not repair weak master data, unclear processes, bad integrations or poor implementation decisions. It usually makes those problems more expensive.

In conclusion

Do not ask whether your company is “too big for Business Central.” Ask where Business Central is forcing the organization to compensate.

Document the seven signals. Measure the work happening outside the ERP. Map the ISVs and customizations. Benchmark the performance issues. Separate implementation problems from product limitations. Then make the decision.

Qixas Group implements Business Central, Dynamics 365 Finance and Dynamics 365 Supply Chain Management. We also recover projects where companies were sold more software before anyone fixed the underlying problem.

Our recommendation is simple: Stay on Business Central while it fits the operating model. Fix it when the implementation is the problem. Move when the evidence shows the platform itself has become the constraint.