Your ERP holds the answers. Your reports don't.
Many Business Central 365 environments contain valuable business data, but standard reports only show a fraction. Closing the gap starts with the right architecture.
Excel as a workaround
Standard reports fall short. Excel exports and manual consolidation have become the norm.
Combining data is manual work
Merging data from Business Central 365, WMS, webshop and financial systems takes hours every week.
Cloud costs without results
Your Azure bill keeps rising, but reporting capabilities don't improve.
No data ownership, just dependency
Your data layer is embedded in vendor solutions. You depend on external parties for every change.
Discovery
45 minutes about your Business Central 365 environment, current integrations and reporting needs. Together we map out what exists and what is missing.
Architecture proposal
API-first design, platform choice (BigQuery, Fabric or other) and a realistic cost estimate. No thick reports, just a clear plan.
Delivery & operations
Build, validate, hand over. You own the result. We remain available for operations and further development.
Fabric Mirroring: how we removed Synapse from our Business Central 365 pipeline
From complex Synapse pipelines to near-realtime data with Fabric Open Mirroring.
Read moreWhy your Azure costs explode with realtime reporting
How near-realtime reporting can blow up your cloud costs, and what you can do about it.
Read moreAzure API Management as integration hub: one gateway, multiple systems
When five systems each have their own authentication mechanism, you have an architecture problem.
Read moreFrom FTP to API: how to modernize a legacy data connection
The step-by-step path from CSV files via FTP to event-driven integration.
Read moreThe hidden costs of outsourced integrations
Why owning your data layer matters. Do you always know what you are giving up?
Read moreThe large consulting firms provide advice and depart. Boutique firms build, but often lack architectural depth. We do both. And we stay.
"Advice without execution is an opinion. Execution without architecture is a time bomb."
What you get
- Conversation with Herman and/or Maurits personally
- Independent advice, no license sales
- Custom architecture proposal
- Ownership of the result
Direct Access
ERP Data Integration in practice
- What is ERP Data Integration?
- ERP Data Integration means making your ERP data available outside the ERP system itself, in a form you can report on, analyze and combine with other sources. For Business Central 365 that means: extracting data via APIs or direct queries from BC365, transforming it into a reportable format, and loading it into a data platform such as BigQuery, Microsoft Fabric or a similar environment. From there any BI tool works: Power BI, Looker, Tableau. You own the data and are no longer dependent on the standard reporting module.
- Does this only work with Business Central 365?
- We specialize in Business Central 365 because that is the most common request, but the approach works for the entire Microsoft Dynamics family: BC365, NAV, AX and Finance & Operations. For other ERP systems (Exact, Unit4, AFAS, SAP, custom solutions) we build similar connectors. During the introductory call we ask which version you use and how your environment is set up. Based on that we create the architecture proposal.
- Which data from BC365 can be extracted?
- In principle, all tables that BC365 grants access to. Sales and purchase data, inventory, finance, projects, manufacturing, service, customer and supplier records. Standard and custom fields. History and real-time. We work via the official BC365 APIs and additional endpoints where needed. Which data is actually extracted depends on your reporting needs: we usually start narrow with the data that solves the biggest reporting bottleneck, and expand as the need grows.
- How do you combine BC365 with other sources?
- In the data platform we bring BC365 data together with data from other sources: webshop, WMS, CRM, PIM, external APIs, financial systems. We model the data so they relate to each other at customer, product or order level. The result is an integrated view in which you can see, for example, how a marketing action translates into actual order data, or how inventory movements relate to lead times. This is exactly what loose Excel exports cannot deliver.
- Where does the data platform run?
- We work with Google Cloud (BigQuery) and Azure (Microsoft Fabric, Synapse, Cosmos DB). The choice depends on your existing IT environment, preferences and budget. Microsoft-centric organizations often choose Fabric because it fits what they already have. Organizations seeking maximum scalability and low entry costs more often choose BigQuery. We advise independently: we run both platforms in production and have no preference detached from your situation.
- What if we already have a data warehouse?
- Then we connect to it. There is no need to replace your existing environment to integrate BC365 data well. We assess what is in place, what works well and where the gaps are. Then we build the connector so the BC365 data lands in your existing data warehouse, in a usable model. That way we strengthen what already exists instead of building something next to it. Sometimes it turns out the existing data warehouse no longer fits where you are now: we will discuss that openly.
- How long until we are operational?
- A first working integration with the most important data flows is usually in place within four to six weeks. With that you can already report on the core figures. A fully rolled out data platform with multiple sources, dbt transformations and dashboards typically takes three to six months, depending on scope. We work in short sprints with intermediate deliveries, so you see value quickly and do not have to wait for one big final delivery.
Last updated: 11 April 2026