// DEEP DIVE | LEGACY INTEGRATION
Microsoft Dynamics Integration: From Navision to 365
Microsoft Dynamics integration is rarely the bottleneck itself in the Microsoft stack. The bottleneck sits in the gaps between versions: an older NAV in the basement, Business Central in the cloud, Dynamics 365 Sales for CRM. Standard connectors like Power Automate cover trivial flows but hit their limits as soon as complex AI logic, custom fields, or on-premise data sources enter the picture. We build the custom bridge that works exactly in those gaps.
THE PROBLEM
67 percent of integration projects fail on legacy systems
In the Microsoft ecosystem, several worlds meet. A NAV 2018 that has been running in production for years. A Business Central just migrated to the cloud. An AX/F&O for enterprise operations. On top of that, Dynamics 365 Sales as CRM and Power Platform flows running somewhere in between. As long as standard processes get mapped, this works. As soon as AI logic enters the picture, the chain breaks at its weakest link.
Microsoft recommends Power Automate and Copilot for everything that is standard. That covers a good share of cases but stays generic. Anyone needing specific AI logic (deduplication, dark processing, cross-system validation) quickly runs into low-code limits. Or the existing system is not cloud-capable at all and Power Automate never even sees it.
We solve this with real code: Python.NET, AL. Not because code is always better, but because it goes exactly where low-code tools give up. Existing Power Automate flows we do not tear down, we extend them with custom connectors. Where Power Automate finishes, we continue.
How we speak Dynamics
Depending on the Dynamics variant we take the right path. For NAV we use SOAP and REST web services, optionally direct SQL access in read-only mode for reporting. For Business Central and Dynamics 365 we go through OData v4 and the official REST APIs. For AX and Finance & Operations we work with data entities for mass import and export. For Dynamics 365 CE/Sales (CRM) we go through Dataverse and the Web API. In-system code (AL for BC, X++ for F&O) we only touch where it is indispensable for performance or specific logic.
Four use cases we automate in production
/ OUR APPROACH
01
Step 01
BC/NAV - Order entry from email
PDF order comes in by email, Xanevo OCR reads the content, a custom connector checks the customer number in Business Central or NAV and creates the sales order directly. Custom fields that the standard Power Automate connector does not even know about are handled. Document number flows back to the sender, the whole process runs unattended.
02
Step 02
AX/F&O - Procurement with demand forecast
The AI forecasts demand for the upcoming weeks based on historical data. Through data entities we create purchase requisitions in AX or F&O, pre-filled with quantities, suppliers, and proposed delivery dates. Purchasing reviews and approves instead of calculating demand themselves.
03
Step 03
Dynamics 365 CRM - Lead enrichment and deduplication
New leads in the CRM are pulled through Dataverse. The AI enriches them with company data (address, industry, headcount) and checks against existing accounts for duplicates. Real duplicates get merged, possible duplicates go to the CRM manager for review. The data stays clean without sales losing time.
04
Step 04
Custom connector and licensing
For the integration, we typically do not need an additional named-user license. We work with an integration user or a web service key. Permissions are set granularly so the connector can only do what the defined use cases require. Every action is logged with user ID and timestamp.
Extend Power Automate, don't replace it
If you already run Power Automate in production, that is a strong starting point. We do not build a competing platform. We extend existing flows with custom connectors. Your Power Automate flow calls our custom connector exactly where the standard action falls short. The connector brings the AI logic with it, writes the result back, and the flow keeps running. You keep your Power Platform investment and gain depth precisely where standard ends.
67 %
of integration projects fail on rigid legacy systems
Industry benchmark: the majority of integration projects between cloud applications and existing systems do not hit their defined goal in the planned timeframe because standard connectors are overwhelmed by individual requirements. With a custom connector approach the risk profile changes: defined scope, concrete outcome, documented paths.
When does Power Automate suffice, when do you need custom?
Requirement
Power Automate (standard)
Xanevo custom connector
Trivial flows (email → Excel)
Fully covered
Not needed
Custom fields in BC
Limited support
Fully covered
AI logic (OCR, classification)
Only limited via AI Builder
Maximum flexibility (Python.NET)
NAV on-premise (not BC)
Not possible without gateway
Fully covered via SOAP/SQL
Cross-system validation
Cumbersome across multiple flows
In one pipeline
Three questions Microsoft owners ask
In most cases, an integration user or a web service key suffices. For Business Central and Dynamics 365 there are dedicated API and application license models that are cheaper than a full named user. For NAV and AX we use service accounts. Which variant applies to you, we clarify in the Dynamics check.
Yes. We use secure gateways or hybrid connections to integrate closed NAV installations. For industries with strict data protection requirements (finance, healthcare, defense), this is often the only viable path. Cloud, hybrid, or pure on-premise are all valid deployment models.
Yes, that is our standard approach. We build custom connectors that get called as an action inside your existing flows. You keep your Power Platform investment and gain AI logic exactly where standard ends. No rip-and-replace, just extend-and-enhance.
Related deep dives
SAP Integration
Side-by-side connection to SAP R/3 and S/4HANA via BAPI, IDoc, and OData. The sister solution for SAP estates.
AS/400 and Mainframe
Modernization for IBM i systems via terminal emulation and validated write paths, where even NAV still feels modern.
// DYNAMICS INTEGRATION
Let's review your Dynamics landscape.
Which versions are in use, which modules do you run, which processes still go manual today? We review your version (NAV, BC, AX, F&O, 365 CE), look at existing Power Automate flows, and give you a clear answer on where standard suffices and where custom begins. One hour, no sales pitch.