Business Central Integration: Connecting Your Systems

"BC integrates with everything" is a true statement at the architecture level and a misleading one at the project level. Business Central exposes a modern REST API and connects natively with the Microsoft ecosystem. Outside the Microsoft ecosystem, most integrations require design, configuration, and in many cases bespoke development. The difference between a native integration and a configured or custom integration is measured in weeks, cost, and ongoing maintenance commitment.

This article explains the three layers of BC integration, where each common system falls, and what integration actually involves for an Irish or UK SMB. If you have been told that a specific integration "just works," this is the article to read before you sign the statement of work.

The Three Layers of BC Integration

Not all integrations are equal. Understanding which layer a given system falls into is what separates a realistic budget from a mid-project surprise.

Layer 1: Native Microsoft ecosystem integration. For organisations already using Microsoft 365, this layer is genuinely plug-and-play. Outlook, Excel, Teams, OneDrive, SharePoint, and Word all integrate natively with Business Central, configured during implementation, with no additional licensing or development required.

The Outlook add-in lets users create quotes, view customer records, and post purchase invoices directly from their inbox. The Excel "Edit in Excel" feature provides a two-way sync: users edit records in a familiar spreadsheet interface and publish changes back to BC via an OData web service endpoint (Microsoft Learn, Business Central and Excel Integration). Teams integration surfaces BC records and data within Teams channels and conversations without requiring a full BC licence for every viewer (Microsoft Learn, Teams Integration). Power BI connects to BC data for dashboards and reporting with no middleware required.

For businesses already running on Microsoft 365, this native integration layer is one of the most practical reasons to choose BC. Users work in the tools they already use. ERP data does not require a separate login or a parallel window.

Layer 2: Pre-built AppSource connectors. Microsoft maintains an AppSource marketplace of certified connectors and extensions. The most significant for Irish and UK SMBs is the native Shopify connector, included in all new BC cloud environments at no additional licensing cost (Microsoft Learn, Shopify Connector). Power Automate provides a low-code workflow automation layer that connects BC to hundreds of external services for notifications, approvals, and simple data sync. A range of payroll connectors (Sage Payroll, Moorepay, Bright Pay for Irish businesses) are available through AppSource and certified third-party partners.

Pre-built connectors are not the same as native integrations. They handle defined scenarios well. When the business scenario falls outside what the connector was designed for, a pre-built connector either fails silently or requires workarounds that introduce their own maintenance overhead.

Layer 3: Bespoke API and middleware integration. For systems outside the Microsoft ecosystem that do not have a pre-built connector that fits the business requirements, integration requires custom API development against BC's REST (OData v4) endpoints, a middleware or iPaaS platform such as Azure Logic Apps, Celigo, or Patchworks, or a file-based data exchange using BC's Data Exchange Framework for systems without a modern API.

Most CRM systems, legacy payroll platforms, industry-specific tools, and proprietary databases fall into this layer. Bespoke integration is not inherently more fragile than a pre-built connector, but it requires design, development, testing, and an ongoing maintenance commitment. When BC releases its twice-yearly feature updates, custom integrations need to be tested and potentially updated.

Zoosh Digital designs and builds bespoke integrations in-house, using our Application Language (AL) development capability alongside standard BC implementation. For businesses where the integration workstream includes custom API development, having the implementation partner and the development team under one roof eliminates the coordination gap and accountability ambiguity that arises when integration work is subcontracted.

The Shopify Connector: What It Does and Where It Stops

The native Shopify connector is the most commonly requested integration for Irish and UK SMBs evaluating BC. It is included in every new BC cloud environment and handles the standard e-commerce-to-ERP flow well: product synchronisation, order import, inventory updates, customer creation, and payment and fulfilment handling.

What the native connector does reliably:

• Bidirectional product and inventory sync between Shopify and BC
• Automatic import of Shopify orders as BC sales orders
• Customer record creation in BC from Shopify customer data
• Payment and fulfilment status updates
• Support for multiple Shopify stores with independent per-store configuration

Where the native connector shows its limits:

Multi-store complexity: while the connector supports multiple Shopify stores, advanced management across stores with different pricing rules, product catalogues, or inventory sources may require additional configuration or middleware. In Zoosh Digital's experience, multi-store Shopify setups are one of the most common scenarios where businesses discover the native connector's limits mid-project. The connector was designed with single-store simplicity as the primary use case, and growing businesses with multiple brands, regions, or B2B and D2C channels often outgrow it as they scale.

Multi-currency: orders imported into Business Central use the store's base currency rather than the actual transaction currency, and only one price list is available per selected currency. For businesses selling internationally across multiple currencies, this is a significant limitation that requires a middleware solution or bespoke handling.

Shopify POS: the connector synchronises Shopify online store orders only. If you operate physical retail locations with Shopify POS, those sales do not automatically import into BC.

Complex product variants: businesses with extensive product catalogues and multiple variant combinations (colour, size, material) may find the variant mapping in the native connector time-consuming and prone to gaps.

Microsoft intentionally limits extensibility in the Shopify connector in order to maintain compatibility with frequent changes on Shopify's side. This makes the connector reliable but less flexible. As Microsoft's own documentation notes, the connector is designed for BC Online only and is not supported for on-premise BC deployments (Microsoft Learn, Shopify Connector). The honest test before committing to the native connector as the integration approach: ask your BC partner to demonstrate the connector against a sample of your actual Shopify orders, including any edge cases. An hour of testing before the statement of work is signed is worth considerably more than discovering the limitation at month three.

CRM Integration: HubSpot, Salesforce, and Dynamics 365 Sales

This is the area where "BC integrates with everything" causes the most expectation misalignment. HubSpot, Salesforce, and most non-Microsoft CRM systems do not have a native Microsoft-managed connector to Business Central. Integration requires middleware, third-party connectors, or bespoke API development.

Microsoft Dynamics 365 Sales is the exception. It connects natively to Business Central through a standard Microsoft integration that synchronises accounts, contacts, items, and opportunities between the two systems. For businesses already using or evaluating Dynamics 365 Sales, this native connection is a genuine advantage.

HubSpot does not have a native Microsoft-managed BC connector. Integration is typically delivered through a middleware platform (Azure Logic Apps, Celigo, Patchworks) or a certified third-party HubSpot-BC connector available on AppSource. Before scoping a HubSpot-BC integration, the data mapping exercise needs to be completed: how does a HubSpot Deal become a BC Sales Order? At what lifecycle stage does a HubSpot Contact become a BC Customer? What happens when a deal is closed-lost, and does that affect the BC record? These are business process questions as much as technical ones, and they take time to answer correctly.

Salesforce follows the same pattern as HubSpot: no native Microsoft-managed connector, middleware or third-party connector required, and a data mapping exercise that is more complex than it appears at the start.

The honest answer for any CRM outside the Microsoft ecosystem: budget this as a bespoke integration workstream with its own design, development, and testing scope. Do not assume a pre-built connector will handle your specific data model and workflow requirements without validation.

Payroll Integration

Business Central does not include payroll natively. For Irish and UK businesses, payroll integration is a standard part of the BC implementation scope.

For UK businesses, several payroll systems have AppSource connectors or certified integrations: Sage Payroll, Moorepay, and Bright Pay (now Thesaurus Payroll Manager in Ireland) are the most common. These connectors typically handle the posting of payroll journals from the payroll system into BC's general ledger, with varying levels of employee master data synchronisation.

For Irish businesses, the Revenue PAYE Modernisation requirements add a compliance layer that the payroll connector needs to handle correctly. Business Central's native Irish payroll support covers the general ledger side, but the PAYE real-time reporting obligation is handled by the payroll system itself, not by BC.

Businesses running payroll in-house on a system without a pre-built BC connector will need either a middleware solution or a file-based export and import process. This is a functional integration that is straightforward to design but needs to be in the implementation scope and budget from the start.

Integration Costs and What to Budget

Integration is not a line item in the core BC implementation. It is a workstream with its own design, development, testing, and ongoing maintenance costs. The most common budget surprise in BC projects is discovering at month four that a required integration needs custom API development that was not in the original statement of work.

Indicative cost ranges, based on Zoosh Digital's project experience with Irish and UK SMBs:

These are indicative ranges. The actual cost depends on data complexity, the number of objects being synchronised, the frequency of sync, and the volume of transactions. Real-time bidirectional sync is more expensive to build and maintain than a daily batch.

Ongoing maintenance is the hidden cost. Every bespoke integration creates an obligation: when BC updates twice per year, custom integrations need to be tested and potentially updated. Budget for annual integration maintenance as a percentage of the original development cost, typically 15 to 20% per year.

The Integration Discovery Checklist

These are the questions to answer in the discovery phase, before the statement of work is signed. As covered in the Business Central implementation guide in this series, integration scope belongs in the discovery phase alongside process mapping and data assessment: discovering integration complexity mid-project is one of the most consistent causes of timeline and budget overruns.

List every system currently in use. For each one: what data needs to flow to or from BC? Is the sync one-way or two-way? How frequently does it need to sync? What happens if the sync fails?

Categorise each integration explicitly. Microsoft native (no additional cost or development), AppSource connector (configuration cost, ongoing connector licence), or bespoke (design, development, testing, maintenance). Insist on this as a written deliverable from the discovery phase.

For Shopify specifically. Ask the partner to demonstrate the native connector against a sample of your actual orders, including any edge cases: discounts, multi-currency, gift cards, subscription products. This takes an hour and is worth doing before you commit.

For CRM specifically. Define the data mapping before scoping the integration. How does a deal become an order? When does a contact become a customer? What happens to open opportunities if the customer record changes in BC?

Ask directly: who builds the bespoke integrations? Does the partner do this in-house, or do they subcontract it? Subcontracted integration development creates a cost overhead, a coordination gap, and an accountability question when something breaks six months after go-live.

FAQ

Does Business Central integrate with Shopify?

Yes. Microsoft provides a native Shopify connector included in all new Business Central cloud environments at no additional licensing cost. The connector handles product synchronisation, order import, inventory updates, customer creation, and fulfilment status. It works well for standard single-store setups. Businesses with multiple Shopify stores, complex product variants, multi-currency requirements, or Shopify POS operations may find the native connector insufficient and will need middleware or bespoke development. Always test the connector against your actual store configuration before committing to it as the integration approach.

Does Business Central integrate with HubSpot?

Not natively through a Microsoft-managed connector. HubSpot integration with Business Central requires a third-party connector from AppSource or a middleware platform such as Azure Logic Apps, Celigo, or Patchworks. The integration must be scoped and budgeted as a separate development workstream, including a data mapping exercise that defines how HubSpot objects (contacts, deals, companies) map to BC objects (customers, sales orders, vendors). Do not assume a pre-built connector will handle your specific data model without validation.

Does Business Central integrate with Microsoft 365?

Yes, natively. Outlook, Excel, Teams, OneDrive, SharePoint, and Power BI all integrate with Business Central out of the box, configured during implementation with no additional licensing required. The Outlook add-in allows users to create quotes and post invoices from their inbox. Excel provides two-way sync for editing and publishing BC records. Teams surfaces BC data within channels and conversations. For businesses already using Microsoft 365, this integration is one of the most practical advantages of choosing Business Central over a non-Microsoft ERP.

Does Business Central include payroll?

No. Business Central does not include payroll natively. For UK and Irish businesses, payroll integration is a standard part of the implementation scope. Several payroll systems have AppSource connectors or certified integrations (Sage Payroll, Moorepay, Bright Pay, Thesaurus Payroll Manager). These typically handle the posting of payroll journals into BC's general ledger. Businesses running payroll on a system without a pre-built connector need a file-based or API-based integration designed as part of the implementation.

What does a bespoke BC integration actually involve?

A bespoke BC integration requires a design phase (defining the data objects, mapping, sync frequency, and error handling), a development phase (building the connection against BC's REST OData v4 API endpoints), a testing phase (validating the sync against real data including edge cases), and a go-live phase. Post-go-live, the integration requires ongoing maintenance: BC's twice-yearly feature updates need to be tested against the custom integration, and any API changes on either side need to be reflected in the integration logic. Budget for this maintenance cost from the start.

Can Power Automate replace a bespoke BC integration?

For some use cases, yes. Power Automate provides a low-code automation layer that connects BC to hundreds of external services without custom development. It is well-suited for notifications, approval workflows, and simple one-way data sync. For complex bidirectional integrations with high transaction volumes, specific error handling requirements, or custom business logic, Power Automate is typically insufficient and a proper middleware or bespoke integration is required. The distinction between Power Automate being sufficient and not sufficient is a question worth asking your partner explicitly during the discovery phase.

Closing Thought

The integration question is where realistic project budgets are built or lost. A business that maps every integration in the discovery phase, categorises each one correctly, and budgets the bespoke development work upfront will deliver a complete BC implementation on time and on budget. A business that discovers mid-project that the HubSpot integration requires custom API development that was not in the original scope will face a cost conversation at the worst possible moment.

The question to ask any BC partner before you sign is simple: who builds the bespoke integrations, in-house or subcontracted? The answer tells you something important about how accountability will work when something breaks after go-live.

Zoosh Digital builds both the BC implementation and the bespoke integration layer in-house. If you are scoping a BC project that includes integration requirements beyond the Microsoft native stack, contact Zoosh Digital for an honest assessment of what each integration actually involves.

Referenced Sources

• Microsoft Learn. Business Central and Excel Integration. learn.microsoft.com/en-us/dynamics365/business-central/admin-deploy-excel-addin.
• Microsoft Learn. Business Central Teams Integration. learn.microsoft.com/en-us/dynamics365/business-central/across-teams-overview.
• Microsoft Learn. Shopify Connector for Business Central. learn.microsoft.com/en-us/dynamics365/business-central/shopify/get-started.
• Microsoft Learn. Dynamics 365 Business Central 2025 Release Wave 1 Overview. learn.microsoft.com.
• Microsoft. Dynamics 365 Business Central pricing and licensing. microsoft.com/en-ie/dynamics-365/products/business-central.