We need to integrate Business Central with some proprietary legacy systems. What API options are available for integration? Are there any good integrators someone can recommend?

Business Central/NAV
1

We need to integrate the D365 business central solution with some proprietary legacy systems. What API options are available for integration? Are there any good integrators someone can recommend?

1 Like
2

I’ve found that the API Pages can handle most of the work. Anything else can be done in the Business Central Web Services.

These are just OData. And really easy to set up via a PTE Extension.

Using Service to Service Authentication - Business Central | Microsoft Learn

I highly recommend you understand all the API limits and per-tenant limits on your integrations. This has been an issue for me and could easily make or break a process in large user environments.

BCCL is another tool in my back pocket. It’s made by Erik Hougaard you can utilize it to move data in/out of BC in bulk.

3

Hi Sandey,

That is a critical and common integration question. You have excellent API options to connect your proprietary legacy systems to Business Central (BC).

Primary API Options

For deep, reliable integration, you will use these two BC endpoints:

  1. Standard Web Services (OData/SOAP): The default, most stable option. Exposes core BC entities (Customers, Items, Orders) as API endpoints. This is best for standard data creation and updates (CRUD).

  2. Custom API Pages (AL Language): If standard APIs don’t expose the complex data or logic you need, developers can build custom endpoints. This gives you maximum control to consolidate data from multiple tables into a single call.

Finding the Right Integrator

Look for a partner who is skilled in both parts of the connection:

  1. BC Development (AL): They must understand the BC data structure and be able to build Custom API Pages to ensure data integrity.

  2. Azure/Middleware: Experience with tools like Azure Logic Apps or Power Automate is essential. These act as the reliable “translator” between your proprietary system and the BC API, handling logging and retries.

Focus on certified partners who prioritize a stable, well-designed data flow over quick fixes. Good luck!

If you need some direct help, Email me hardik.gupta@allgrowtech.com

4

For integrating legacy systems with D365 Business Central you basically have three main API options:

  • Standard REST APIs (v2.0 API pages) for most master and transactional data.​

  • OData v4 web services, which expose pages and queries and are still widely used for reporting and integrations.​

  • Custom API pages / codeunits when you need domain-specific payloads, validation, or performance tuning beyond the standard entities.​

If your legacy systems are more SQL‑centric, one option you might consider is using a dedicated connector that syncs Business Central data into SQL and then integrating locally from there. For example, BC2SQL Sync (bctosql.com) is a specialized integration service that:

  • Synchronizes Business Central SaaS companies to SQL Server, PostgreSQL or MySQL on‑prem or in the cloud, so legacy apps can keep working against a relational database.​

  • Supports scheduled and incremental synchronization, with resilient retry logic and logging for audit/compliance scenarios.​

  • Handles multi‑tenant / multi‑company scenarios and multiple database targets, which is useful if you have several BC companies or environments to integrate.​

  • Is designed to sit between Business Central and other systems (BI, reporting, custom line‑of‑business apps), so you can decouple the legacy side and keep the integration surface stable.​

Depending on your architecture, you could either integrate directly with the BC APIs, or use something like BC2SQL as an intermediate layer that keeps a clean SQL model in sync with BC and lets your legacy systems talk “their native language” to that database.

5

Hi @sandey_sharma

Is the issue resolved? Or is there something we can help get it sorted?