Business Central
Business Central integrates through published REST APIs, OData, Power Automate, Dataverse and AppSource extensions.
Reviewed 2026-08-24 by the Machina IT engineering team.
Business Central integrates through published REST APIs, OData, Power Automate, Dataverse and AppSource extensions. The integrations that pay off fastest for manufacturers are shipping and rate quoting, EDI, barcode and shop floor data capture, CAD or PLM item and BOM sync, and Power BI reporting. Direct database writes are not an option in the cloud, which removes the most common source of legacy ERP fragility.
Define one system of record per data element. When both ERP and a satellite system can change an item's cost or a customer's credit limit, reconciliation becomes permanent manual work.
Make every integration observable: log every message, alert on failures rather than on silence, and build a documented replay path for a missed batch.
Microsoft ships major updates twice a year plus monthly service updates. Extensions and custom APIs must be validated in a sandbox against the preview release, not discovered broken in production.
That validation cycle belongs to someone by name, on a calendar, as part of managed IT rather than as an occasional project.
Common mistakes
Common questions
No. Cloud Business Central is API-only, which is a durability improvement — extensions and APIs are version-tested, while direct table writes never were.
Service-to-service connections authenticate differently than people do. Confirm the licensing treatment per integration during design so the model has no surprises.
Either an AppSource EDI extension or a managed EDI provider mapped to Business Central APIs. The deciding factor is how many trading partners and how customer-specific their maps are.
We review your network, security posture, cloud tenant and recovery plan, then hand you a plain-language report of what we found and what it means for the business.
