Migration for BizTalk Server with Azure Logic Apps Migration Agent

When you're ready to migrate BizTalk Server solutions to Azure Logic Apps Standard, modernize your enterprise integrations as Standard logic app solutions by using the Migration Agent extension for Visual Studio Code. The agent is an open-source extension that provides an AI-assisted workflow by using GitHub Copilot and the Visual Studio Code Language Model API to guide you from discovery through deployment.

Migration isn't a lift-and-shift process. Preserve the required business behavior, but refactor the implementation to use appropriate Azure Logic Apps workflows, connectors, custom code, identity, messaging, monitoring, and deployment practices. Start with Azure Logic Apps Standard as the target application, use the native workflow capabilities, built-in connectors, transformations, and local functions where appropriate, and add other Azure services only when a specific architectural requirement justifies them. For reasons to modernize and a capability summary, see Why migrate from BizTalk Server to Azure Logic Apps Standard?

For an introduction and demonstration, see Modernize any integration platform to Azure Logic Apps Standard with the Azure Logic Apps Migration Agent. To inspect the implementation, report issues, or contribute, see the Logic Apps Migration Agent repository.

Supported migration scope

The following table describes the BizTalk Server source and Azure Logic Apps target support in Azure Logic Apps Migration Agent version 1.12.1. Check the Migration Agent releases for changes before you start a migration.

Parser support means that the extension can discover and represent the listed source artifacts. Missing dependencies, unsupported constructs, and application-specific code still require investigation and might require manual implementation. Generated analysis, plans, workflows, connections, configuration, and code require review and validation.

The Migration Agent architecture is extensible to other integration platforms through contributed parsers and platform-specific skills, but the extension doesn't provide complete migration support for every platform by default. For current platform status and extensibility guidance, see Azure Logic Apps Migration Agent overview and Extend Azure Logic Apps Migration Agent to other platforms.

How the Migration Agent works

The extension organizes migration into five stages. Complete and review each applicable stage before proceeding to the next one. Deployment is optional and requires separate approval.

Custom code in a BizTalk solution doesn't automatically require a separate Azure Functions resource. The Conversion stage can generate .NET local functions for workflow-scoped logic so that workflows and code build, deploy, scale, and operate together in the same Azure Logic Apps Standard application. Use a separate Azure Functions resource when code must be shared across applications or requires independent scaling, versioning, deployment, security, or ownership. For more information, see the custom code guidance for BizTalk migration.

Three specialized Copilot agents support the workflow:

• @migration-analyser groups and analyzes discovered artifacts.
• @migration-planner creates migration plans and source-to-target mappings.
• @migration-converter generates workflows, connections, and supporting code from approved plans.

The extension stores stage outputs so you can inspect and correct the generated inventory, architecture, plans, and implementation artifacts. Treat these checkpoints as required engineering reviews rather than automatic approvals.

The BizTalk capability mapping provides a high-level view of common modernization paths. During Planning, the Migration Agent produces operation-level mappings for each flow, identifies components without direct equivalents, and recommends resolutions.

Prepare your migration

Before you start Discovery, collect the source implementation and the evidence needed to verify its behavior:

• BizTalk solution and project files
• Bindings and environment-specific configuration
• Orchestrations, schemas, maps, pipelines, and pipeline components
• Business rules, assemblies, and other custom code
• HIDX files
• Endpoint and adapter information
• Certificates or certificate references without exposing private keys or secrets
• Existing architecture and operational documentation
• Representative input messages and expected outputs
• Unit, integration, regression, and black-box tests
• Throughput, latency, ordering, message-size, recovery, and availability requirements

Keep related files and dependencies in a clear directory structure. Discovery quality depends on the completeness of the source material. Resolve missing dependencies and incorrect flow groupings before authorizing Planning or Conversion.

Modernize incrementally

For most BizTalk estates, migrate in waves rather than using a single big-bang release. Use the Discovery results to group related artifacts into end-to-end integration flows, then prioritize flows based on business value, risk, complexity, expected operating cost, support timelines, and dependencies.

For each wave:

1. Select one or more representative flow groups.
2. Complete and review the applicable Migration Agent stages. Run the optional Deployment stage only when you want the agent to deploy to Workflow Service Plan.
3. Validate behavior and nonfunctional requirements in a representative environment.
4. Plan coexistence, partner coordination, cutover, rollback, and backlog reconciliation.
5. Release the migrated flows and confirm production monitoring and support ownership.
6. Capture reusable mappings, architecture patterns, tests, deployment assets, and lessons for later waves.

Start with a flow that is meaningful enough to validate the target architecture but contained enough to expose gaps without putting a critical migration path at unnecessary risk.

Estimate each wave by starting with the Azure Logic Apps Standard application and adding supporting Azure services only when the approved architecture requires them. Each service is provisioned and billed independently. Include Standard hosting, managed connector calls, storage, networking, monitoring, supporting services, and temporary BizTalk coexistence in the estimate. For more information, see Build a cost-effective target architecture.

What your team still owns

The Migration Agent automates repeatable work. Your team remains responsible for the decisions and evidence required for a production integration solution.

Apply mission-critical design guidance only to workloads whose business impact and availability requirements warrant that classification.

Next step

Install the extension, prepare a complete source folder, and begin with Discovery. Keep source projects unchanged and write generated output to a separate destination so you can compare implementations and repeat the migration safely.