AI-powered BizTalk migration to Azure Integration Services (AIS)
Webinar recording from June 3, 2026
Microsoft BizTalk Server support is coming to an end. For SMEs and large enterprises, this is much more than a mandatory task—it is a strategic turning point.
Historically grown, business-critical integration landscapes must now be future-proofed. The logical step leads to Azure Integration Services (AIS). However, such migration projects are often considered budget-draining: they are lengthy, error-prone, and tie up valuable IT resources. Furthermore, the question arises: should old workarounds be carried into the future? Are the existing workflows still valid in the new cloud world? Now is the moment to put existing processes and workflows to the test and plan the migration process.
This webinar focused on the technical part of the migration. We demonstrated in a practical way how you can efficiently master the transition from BizTalk to AIS and save up to 50% of project days during your BizTalk migration. Learn how to automate the transformation of BizTalk components to AIS using the AI-powered NSYNC BizTalk:Migrator tool (also known as NSYNC AIS:Generator), thereby minimizing manual effort, reducing migration risks, and transferring your interfaces in a standardized and compliant manner.
Would you like to see the entire technical migration process and the monitoring dashboard in action? Start the video recording of the webinar directly.
Three migration paths in strategic & technical comparison
Moderated by NSYNC's co-founder Tommy Bauhammer—a profound expert in the Microsoft integration world for over 25 years (from BizTalk 2000 to AIS)—the webinar analyzed three essential cloud strategies:
Quantitative benchmark (Scenario: Enterprise infrastructure with 100 interfaces)
| Metric / Criterion | Classic Redevelopment | Microsoft BTS Migrator | NSYNC BizTalk:Migrator |
| Automation Level | 🔴 5 % | 🟡 30–50 % | 🟢 80–95 % |
| Analysis effort | 🔴 Very high | 🟡 Medium | 🟢 Low |
| Development effort | 🔴 Very high | 🟡 Medium | 🟢 Very low |
| Pattern-based runtime design | 🔴 No (manual) | 🟡 Fragmented | 🟢 Yes (native Pub/Sub) |
| Integrated process monitoring | 🔴 No | 🔴 No | 🟢 Yes (NSYNC SYMON DPM) |
| Technical implementation effort | 🔴 500–800 PD | 🟡 400–600 PD | 🟢 200–300 PD |
| FTE requirements (project team)* | 🔴 10 | 🟡 8 | 🟢 4 |
*Note for the PMO: The required overhead for project management and business stakeholders for end-to-end validation is already fully included in the FTE requirements.
- Classic redevelopment (Greenfield)
- The native Microsoft approach (tool by Harold Campos)
- The automated approach via NSYNC BizTalk:Migrator
The traditional approach involves a complete manual analysis and documentation of the existing BizTalk landscape, followed by a full reprogramming in AIS.
-
For the CEO:
- High dependency on rare specialists.
- Unpredictable project timelines.
- High operational risk during the transition.
-
For the technician:
- Full control over every target component.
- Extremely repetitive, error-prone greenfield development effort.
Microsoft recommends a semi-automated migration path using conversion tools. The tool reads isolated artifacts (mappings, ports, pipelines, orchestrations) and generates Azure components from them.
-
For the CEO:
- Accelerated analysis phase.
- Unclear follow-up costs, as no turn-key end-to-end processes are created.
-
For the technician:
- The tool only delivers fragmented individual components (predominantly Logic Apps Standard).
- These must subsequently be manually assembled in Azure into a logical sequence and a functional data flow.
- Many artifacts still require manual recreation.
The NSYNC BizTalk:Migrator bridges the gap left by the Microsoft approach through a holistic, AI-based concept.
- For the CEO:
- High level of automation, ranging from 80% to 95%.
-
Greatly shortened time-to-market.
-
Up to 50% savings in technical project days.
-
For the technician:
-
Generation of clean, native cloud code (optionally Azure Logic Apps or Azure Function Apps).
- Automated implementation of process monitoring for operations.
-
Interfaces based on established AIS enterprise architecture patterns.
-
Instead of loose fragments, the tool creates fully functional, end-to-end interfaces based on standardized design patterns and integrates them directly with process monitoring.
The tool architecture: How the AI enables a qualitative leap
For integration architects and tech leads, the NSYNC BizTalk:Generator engine is divided into three transparent phases:
1. Input: Flexible source import
To capture a BizTalk application fully automatically, the engine only requires the existing sources.
- The exported MSI file of the application.
- The associated bindings (ports & mappings).
-
The actual source code (Visual Studio solution including pipelines, maps & schemas).
No preliminary code cleanup is necessary. Unnecessary processes can be excluded within the NSYNC BizTalk:Migrator.
Additional feature for hybrid landscapes: Via Excel specifications or an integrated graphical interface designer, new cloud interfaces can be designed in parallel that exist completely independently of legacy systems.
2. Engine: Cloud architecture based on the on-premises model (Pub/Sub)
Classic BizTalk architectures decouple systems via a central MessageBox using the publish/subscribe principle. Messages find their own way through the platform via filters and subscriptions instead of being hard-wired.
The NSYNC BizTalk:Migrator (AIS:Generator) mirrors this proven enterprise pattern one-to-one in the cloud. Through an innovative AIS Runtime Design Pattern, a pub/sub architecture is built based on Azure Service Bus Topics and Azure Blob Storage. Receiving, processing, and sending components act completely decoupled. This guarantees maximum stability and ensures that the logic of the original environment is maintained exactly.
3. Output: Clean Code & DevOps-Readiness
From the imported structures, the NSYNC BizTalk:Generator (AIS:Generator) generates Azure-native code within seconds, regardless of the number of interfaces.
Architects have the choice between graphical workflows for Azure Logic Apps or high-performance C# code for Azure Function Apps.
Environment-dependent parameters (App Settings for Dev, Test, Prod) are cleanly separated to securely integrate them via Azure DevOps/GitHub Pipelines using Azure Key Vault.
Technical live demo: End-to-end migration of a "Sales Order Entry" application
The core of the webinar consisted of a live demonstration by Andreas Conrad (Architect Product Development) and Dr. Plamen Petrow (Head of Development).
The demo scenario
A functional enterprise application with the following topology was migrated:
- Receive Port (RP_Inbound): Processes two parallel inputs
- System A delivers via file adapter (File).
- System B delivers via HTTP interface.
- Both converge via BizTalk's standard XML receive pipeline.
- Send Port 1 (Archive): Filters by receive port name.
- Intercepts every incoming message.
- Archives them unchanged in the file system.
- Send Port 2 (System C): Uses an HTTP adapter and contains an outbound map.
- The message is transformed according to the specifications of target system C before leaving the integration platform.
The migration process in a nutshell
-
Packaging: MSI, bindings, and source code are uploaded to the generator as a ZIP file.
-
Parsing & Extraction: The engine converts the data asynchronously into a standardized format. Within seconds, the system reports the successful extraction of 4 interface connections, 2 maps, 4 schemas, and 2 pipelines.
-
Topology Selection in the Interface Designer: The developer sees the exact data flow prepared graphically. Here, the logical assignment of FunctionApps and/or LogicApps (e.g., sorted by entities or systems) is determined flexibly.
-
Code Generation & Deployment: With one click, the complete Visual Studio .NET solution, including all C# classes and the integration of process monitoring, is generated and deployed directly into the Azure runtime environment.
The result: Full operational transparency in SYMON DPM
After deployment, the Azure Functions send telemetry data in real time to the integrated process monitoring tool N:SYNC SYMON DPM. In the operations team's dashboard, the entire process chain is immediately visible: From successful receipt and the correct execution of the mapping (including full before-and-after insight into the XML payloads) to archiving and final delivery.
Should an error occur during live operation, the dashboard allows for quick error qualification as well as direct, error-free reprocessing (restart) with a single click.
Further resources
Would you like to see the entire migration process and the monitoring dashboard in action? Start the video recording of the webinar directly.
We would be happy to provide you with our whitepaper "BizTalk Migration to AIS" upon request.
This whitepaper offers a complete overview of all necessary tasks that must take place before and after the technical migration.
Are you planning to replace your on-premises integration platform or would you like to experience the NSYNC BizTalk:Migrator (AIS:Generator) in a live demo?
Our team is happy to advise you on strategic, architectural, and technical matters.
Get in touch
Your contact person:
Tommy Bauhammer | Tommy.Bauhammer@nsync.ch | +41 76 564 61 18 | Contact form