Learn how Business Central integrates with Microsoft 365, Power Platform, Shopify, HubSpot and Salesforce, plus APIs, setup steps and mistakes to avoid.
Contact Us
Most Business Central projects I have reviewed did not fall short because the ERP lacked features. They fell short because the ERP sat on an island. Orders were rekeyed from the webstore, sales reps quoted from stale price lists, and finance closed the month by reconciling three spreadsheets that never agreed.
Integration is what turns Business Central from a good accounting system into the operational backbone of the company. This guide covers how the platform connects to Microsoft tools and outside apps, which integration methods hold up over time, and the mistakes I see teams make most often.
Microsoft Dynamics 365 Business Central is a cloud ERP for small and midsize businesses. It grew out of Dynamics NAV (originally Navision), so it carries decades of proven accounting logic, but it now runs as a SaaS application on Azure with two major updates a year.
It is also available on premises, though most new features, including Copilot and agents, are only delivered to the online version. If you are choosing today, online should be your default unless a regulatory or hosting constraint forces otherwise.
Business Central covers the processes a growing company runs every day, in one database:
The real strength is not any single module. It is that every transaction posts to the same ledger, so a shipment, an invoice and a cost adjustment are always reconciled by design.
Business Central fits companies that have outgrown entry level accounting tools like QuickBooks or Xero but do not need the complexity of an enterprise ERP. In practice, that usually means:
That last point matters more than most buyers realize. When your team already lives in Outlook, Excel and Teams, Business Central feels like an extension of tools they know rather than a new system to learn.
An ERP is only as accurate as the data that reaches it. When orders, customer records and payments live in separate systems, someone has to move that data by hand, and every manual step adds delay and error.
Integration removes that handoff. It lets Business Central receive transactions the moment they happen and push financial truth back to the teams that need it.
Well planned integrations pay back in ways that show up on both the P&L and the team's calendar:
Silos rarely start as a strategy. They grow one app at a time: a CRM for sales, a storefront for eCommerce, a shipping tool for the warehouse. Each works fine alone, but none of them agree on what a customer owes or how much stock is on hand.
Integration gives each system a clear role. A practical rule I use with clients:
Once ownership is clear, data flows in one direction per field and conflicts disappear.
A controller looking at yesterday's numbers makes yesterday's decisions. When Business Central receives orders, receipts and shipments as they happen, finance can see cash, margin and inventory exposure on the same day.
The supply chain benefits too. Purchasing sees true demand from every sales channel, not just the orders someone remembered to enter, so reorder points and planning worksheets actually reflect reality.
Rekeyed orders, stale price lists and spreadsheet reconciliations are signs your integrations need attention. Our experts can map your systems and fix the gaps.
Get an Integration ReviewThis is where Business Central has a genuine edge over competing SMB ERPs. Many Microsoft integrations are built in, share the same Microsoft Entra ID sign in, and need little more than switching on.
The Microsoft 365 connection is the first thing I enable on every project, because it changes daily habits fastest:
The Power Platform is how most companies extend Business Central without writing AL code:
My advice: use Power Automate for lightweight, user facing workflows. For high volume transactional sync, such as thousands of orders a day, use the APIs or a proper integration platform instead.
Business Central online runs on Azure, so you inherit its security, backups and geographic data residency without managing servers. For custom needs, Azure Functions, Logic Apps and Service Bus are common building blocks for integrations that need queuing or heavy processing.
Copilot is now part of everyday use. Microsoft states that every Business Central license includes Copilot at no extra cost. Useful features today include bank reconciliation suggestions, marketing text for items, sales line suggestions, and chat that answers questions about your data.
The newer layer is agents, such as the Sales Order Agent, which can read incoming customer emails and prepare sales quotes for review. These agents are billed separately through Copilot Credits, so budget for them as a usage cost rather than assuming they are free.
Microsoft raised Business Central list prices on November 1, 2025, the first increase in over five years. Current US list prices on an annual commitment are:
| License | Price (USD per user per month) | Best for |
|---|---|---|
| Essentials | $80 | Finance, sales, purchasing, inventory, projects |
| Premium | $110 | Everything in Essentials plus manufacturing and service management |
| Team Members | $8 | Light users who view data, approve and make limited edits |
A few licensing points that affect integration planning:
There is no single right way to connect Business Central. The best method depends on data volume, how real time the sync must be, and who will maintain it after go live.
Native connectors are built and maintained by Microsoft. The Shopify connector, the Dynamics 365 Sales integration through Dataverse, and the Microsoft 365 add-ins are good examples. They are updated with every release, cost nothing extra and are the safest long term choice when they cover your process.
Third party integrations fill the gaps. They are built by ISVs or the other application's vendor and usually offer deeper features for a specific platform. The tradeoff is dependency on that vendor's roadmap and support quality.
| Factor | Native connector | Third party integration |
|---|---|---|
| Cost | Included | Subscription or one time fee |
| Upgrade safety | Maintained by Microsoft | Depends on the vendor |
| Flexibility | Fixed scope | Often more configurable |
| Support | Microsoft and your partner | The ISV |
Microsoft AppSource is the marketplace for Business Central apps. Thousands of extensions cover CRM sync, eCommerce, EDI, shipping, payments, tax and AP automation.
Before installing any extension, I check four things:
When no connector fits, or when you need to connect several systems at once, an integration platform as a service (iPaaS) is often the right middle ground. Common choices include Azure Logic Apps, Celigo, Boomi, MuleSoft, Make and Zapier.
iPaaS tools handle mapping, retries, logging and error alerts, which are the parts that quietly break hand coded integrations. Zapier and Make suit low volume, simple flows. Celigo, Boomi and Logic Apps handle higher volumes and more complex logic.
Every serious integration eventually touches the Business Central APIs, even if a connector hides them from you. Knowing the basics helps you judge the quality of any connector or partner proposal.
Business Central offers standard API v2.0 endpoints that follow REST and OData v4 conventions. They cover core entities such as customers, vendors, items, sales orders, sales invoices, purchase invoices, journals and general ledger entries. When the standard APIs miss a field, developers build custom API pages and queries in AL.
One change every company needs to know about: Microsoft is retiring the old habit of exposing UI pages as web services.
If an older integration still calls page based OData or SOAP endpoints, plan its migration now rather than discovering the problem the week of an upgrade.
Business Central also supports webhooks, which notify a subscriber when records such as customers, items or sales orders change. Webhooks cut down on constant polling, but subscriptions expire after three days unless renewed, so the integration must handle renewal.
Basic authentication with web service access keys is no longer supported in Business Central online. All integrations must use OAuth 2.0 through Microsoft Entra ID. The practices I insist on:
The technical connection is usually the easy part. The work that decides success happens before anyone opens a mapping screen.
Start with the business problem, not the app. "Connect Shopify" is not a goal. "Post every web order to Business Central within 15 minutes with correct tax and payment" is.
For each integration, document:
A simple data flow diagram on one page saves weeks of rework later.
Match the method to the requirement, not to what the last consultant liked:
Also weigh total cost over three years, including subscriptions, support and the effort of each Business Central update.
Clean your data before you connect anything. Duplicate customers and inconsistent item numbers will sync just as faithfully as good data.
Then work through the details in a sandbox:
I always run a short parallel period after go live, where the team spot checks synced transactions daily.
Integrations are living processes, not one time projects. Plan for their care from day one:
These five cover the integrations I am asked about most: CRM, eCommerce and customer communication. Each one solves a different problem, so the right mix depends on where your revenue and customer conversations happen.
HubSpot is a popular CRM for SMBs that want marketing, sales and service in one easy to use platform. Paired with Business Central, it gives the front office a modern CRM while finance keeps full control of the ledger.
There are three common routes:
The native data sync is a good starting point for contacts and companies. Most companies that want true quote to cash automation end up adding a deal to order flow on top.
Shopify has the strongest native story of any eCommerce platform. Microsoft built and maintains the Shopify Connector, and it comes preinstalled in new Business Central environments.
The connector supports:
My recommendation is to start with the native connector. Only look at third party Shopify apps if you hit a specific gap, such as complex B2B pricing or bundles.
Adobe Commerce, formerly Magento, suits merchants with complex catalogs, multiple storefronts or heavy B2B requirements. Unlike Shopify, there is no Microsoft built connector, so integration runs through AppSource apps from specialist vendors, an iPaaS, or a custom API build.
What a good Adobe Commerce integration should handle:
Because Adobe Commerce stores are often heavily customized, budget for more mapping and testing time than you would with Shopify.
Salesforce is common in midsize companies with larger sales teams or complex sales processes. Microsoft does not offer a native Salesforce connector, but there are well established options:
The most valuable flows are account and contact sync, opportunity to sales order, and invoice and payment status back to Salesforce. One honest note: if you are choosing a CRM from scratch, Dynamics 365 Sales has a native integration through Dataverse. If Salesforce is already embedded in your sales team, a solid connector works well.
Twilio adds SMS, WhatsApp, voice and email to Business Central processes. It is less about syncing records and more about triggering timely messages from ERP events.
Practical uses I have seen work well:
The easiest route is Power Automate, which has a Twilio connector and can react to Business Central events. For higher volumes, a small Azure Function or AL extension calling the Twilio API gives more control. Always respect opt in rules and local messaging regulations.
The value of integration looks different in each industry. Manufacturing is where I see the biggest gap between companies that integrate well and those that do not.
Manufacturers on Business Central Premium already have production orders, routings and MRP in the ERP. Integration extends that core to the shop floor and the supply chain:
The result is a planning engine fed with accurate data, which is the only way MRP suggestions become something planners trust.
Many companies come to Business Central integration as part of a migration from older Microsoft ERPs. The pressure is real:
Migration is the perfect moment to rethink integrations rather than copy them. Old NAV and GP integrations often rely on direct SQL access, SOAP or file drops, none of which carry over to Business Central online. Rebuild them on API v2.0 and OAuth, and retire any integration that only existed to work around old system limits.
The right integration is the one your team can run confidently for years, not the one with the longest feature list.
These are the mistakes I see repeatedly, and each one is avoidable:
Business Central is a strong ERP on its own, but its real value appears when it sits at the center of a connected business. Start with the Microsoft integrations you already pay for, such as Outlook, Excel, Teams, Power BI and Copilot. Then connect the systems where revenue and customer conversations happen, whether that is HubSpot, Salesforce, Shopify, Adobe Commerce or Twilio.
Keep the approach simple: define who owns each piece of data, choose native connectors where they fit, build on supported APIs, and monitor every integration like the business process it is. Companies that follow these principles close faster, sell with better information and scale without adding people to move data around.
From HubSpot and Salesforce to Shopify and custom API builds, our team can design integrations that are secure, supportable and built to scale.
Talk to Expert
Yes. Business Central integrates natively with Microsoft 365, and both use the same Microsoft Entra ID sign in. Users can work with Business Central data in Outlook and Excel, and store documents in OneDrive, without separate connectors or extra Business Central licensing.
It depends on the method. Native connectors like Shopify and the Microsoft 365 add-ins cost nothing beyond your Business Central licenses, which start at $80 per user per month for Essentials. AppSource apps usually run from a small monthly fee to a few hundred dollars a month. Custom or iPaaS integrations typically range from a few thousand dollars for a simple flow to tens of thousands for complex, multi system projects, plus ongoing support.
Yes, all three. In Teams, Business Central links shared in a chat expand into live cards, and users can look up contacts without leaving Teams. Power BI connects natively, offers ready made reporting apps, and lets you embed reports in Business Central role centers. Viewing shared Power BI reports requires the appropriate Power BI license.
Yes. Shopify has a native connector built by Microsoft. Salesforce, HubSpot, Adobe Commerce and Twilio connect through AppSource apps, iPaaS platforms or custom integrations using the Business Central REST APIs.
A native connector like Shopify can be running in days, with one to three weeks for proper mapping and testing. A standard AppSource connector usually takes two to four weeks. Custom or multi system integrations often take six to twelve weeks, depending on data quality, the number of entities and how much testing finance requires.
Not always. Microsoft 365 integrations, the Shopify connector and many AppSource apps can be configured by a functional consultant or a capable admin. You will need a developer for custom API pages, AL extensions, complex iPaaS logic or high volume integrations. Even with a no code tool, involve someone who understands Business Central posting setup, since mapping mistakes show up in the ledger.
It can be, if the integration follows current standards. Business Central online requires OAuth 2.0 through Microsoft Entra ID, and data travels over encrypted HTTPS. Give each integration its own app registration with only the permissions it needs, store secrets securely, and review vendors for security certifications and data residency before you install their apps.
Tell us about your problems and one of our Customer Success Managers will get back to you the same day. No spam. No pressure.
No spam. No pressure.Prefer direct contact? Call or email us anytime.
© 2026 All Rights Reserved By TechImplement
© 2025 All Rights Reserved By TechImplement
