Why Most Business Central Integrations Fail Before They Even Launch
Every Business Central project eventually runs into the same question: how does this connect to everything else? Almost no organisation runs Business Central in isolation. There is a CRM somewhere, an ecommerce platform, a warehouse system, a reporting tool the finance team will not give up.
The pitch is always the same: connect everything, and the data flows cleanly between systems forever. The reality is messier. Most integration problems are not technical. They are decisions that never got made properly in the first place, and they show up months after go-live, usually at the worst possible time.
Why Integration Gets Treated as an Afterthought
Integration tends to get discussed late in a Business Central project, often after the core configuration is already locked in. That ordering is backwards.
By the time someone asks how this will talk to the CRM, the data structures, the field mappings, and the business logic have often already been built around the assumption that Business Central is the only system that matters. It is not. It is one node in a network of systems that all need to agree on what a customer record means, what a paid invoice means, and what happens when two systems disagree about either.
The Three Integration Patterns Nobody Explains Clearly
Most integration conversations skip straight to tooling, Power Automate versus a custom API versus a third-party connector, without first deciding which pattern actually fits the problem. There are really only three patterns worth knowing.
Real-time sync
Keeps two systems constantly aligned. Useful when a delay of even a few minutes causes real business problems, such as inventory levels feeding an ecommerce storefront. Expensive to build well and expensive to maintain.
Scheduled batch sync
Moves data on a timer, every fifteen minutes, every hour, overnight. Good enough for most reporting and most CRM use cases. Far cheaper to build and far easier to troubleshoot when something breaks.
Event-triggered sync
Fires when something specific happens, an order is placed, an invoice is approved, and pushes that one event downstream. The best fit for workflows that depend on a specific business moment rather than a constant state of agreement.
Most failed integrations picked real-time sync by default, because it sounds more impressive in a sales conversation, when scheduled batch sync would have done the job for a fraction of the cost and a fraction of the ongoing maintenance burden.
Where the Real Cost Hides
The sticker price of an integration project rarely tells the whole story.
Build cost
The number everyone sees upfront, and usually the smallest one over a three-year horizon.
Maintenance cost
What happens every time Business Central updates, the other system updates, or someone adds a field the integration did not expect. These breaks tend to be quiet, not loud. Nobody notices until the numbers in two systems stop matching and nobody can say when that started.
Reconciliation cost
The time spent every month manually checking the data still matches across systems, because nobody fully trusts the integration to have caught every edge case. This cost is almost never budgeted for, and it is almost always there anyway.
A genuinely good integration is the one with the lowest combined cost across all three, not the one with the most impressive demo.
The Question That Actually Predicts Integration Success
Before any tooling decision, there is one question worth asking that does more predictive work than almost anything else: what should happen when the two systems disagree?
Every integration eventually hits a moment where Business Central says one thing and the connected system says another. A customer was updated in both places at once. An order was cancelled in one system after it had already synced to the other. A field was left blank somewhere it should not have been.
If nobody has decided in advance which system wins, that decision gets made accidentally, inconsistently, by whichever piece of code happens to run last. That is how data quality problems start, quietly, six months after everyone stopped paying attention to the integration because it seemed to be working.
Organisations that get integration right tend to have an explicit answer to the conflict-resolution question, in writing, before a single line of integration code gets built. Ask any partner proposing an integration to show you that answer before the build starts, not after it breaks.
Frequently Asked Questions
Why do Business Central integrations fail after go-live rather than during the build?
Most integration problems are not technical. They are decisions that never got made properly during the build, such as which system wins when two systems disagree about a record. Those gaps surface quietly months later, often when data in two systems stops matching and nobody can say when that started.
What are the three main integration patterns for Business Central?
Real-time sync keeps two systems constantly aligned and is expensive to build and maintain. Scheduled batch sync moves data on a timer and is cheaper to build and easier to troubleshoot. Event-triggered sync fires when a specific business event happens and pushes that one event downstream. Most integrations default to real-time sync when a cheaper pattern would have done the job.
What does a Business Central integration actually cost over time?
Three costs matter: the build cost, which is usually the smallest over a three-year horizon; the maintenance cost, which appears every time either connected system updates; and the reconciliation cost, the ongoing manual effort to confirm the data still matches across systems. The cheapest integration to build is not always the cheapest to own.
What question should be answered before any Business Central integration is built?
What should happen when the two systems disagree? Every integration eventually hits a moment where Business Central and the connected system hold conflicting information. Deciding in advance which system wins, in writing, before any code is built, is one of the strongest predictors of long-term integration reliability.
Scoping a Business Central Integration?
TEKenable holds Advanced Specialisations across Microsoft Dynamics 365, Power Platform, and Azure, and has built Business Central integrations across CRM, ecommerce, reporting, and warehouse systems for organisations in the UK and Ireland. If you want a second opinion on an integration approach before committing to a build, our team is happy to talk it through.
Call us on +44 (0) 207 183 8996 or visit www.tekenable.co.uk. No commitment required.