The cloud-native BizTalk successor. Built by Microsoft V-TSP consultants.
iQBus carries your BizTalk flows, maps, and routing into Azure-native runtime - without rewriting them. The Windows fleet, Visual Studio toolchain, and per-message licensing stay behind.
- Built by Microsoft V-TSP consultants
- Microsoft Solutions Partner · Azure-native ESB
Where your team operates today - and where they operate after.
Hover any row to see its paired equivalent. These five shifts show up in every BizTalk-to-iQBus migration we run.
Where your integration team operates now
- BizTalk Server 2020 - the final version, no successor planned
- Dedicated Windows fleet to patch, scale, and audit
- Visual Studio + compiled releases for any change
- HAT and BAM for tracking, plus custom dashboards on top
- Scarce, expensive talent pool that’s actively retiring
Where your team operates after
- Configuration-driven integrations, hot-swapped at runtime - no version lock
- Serverless on Azure App Service - nothing to patch
- Web console only - no Visual Studio, no compiled releases
- End-to-end transaction tracking out of the box
- Azure-native talent pool, broad and supplied by the market
A migration, not a rewrite.
Two decades of BizTalk work isn’t thrown away. The patterns translate; only the runtime changes.
Maps and transformation intent
BizTalk maps become iQBus XSLT 3.0 transforms - functoid logic preserved, complex maps converted through a guided path and validated against both engines in pilot.
Integration patterns
Receive-validate-transform-route-deliver pipelines map directly to iQBus itineraries. Port groups, exception flows, retries, and dead-letter handling all have first-class equivalents.
Adapters
SAP, Oracle, mainframe, HL7, EDI, and AS2 all have iQBus equivalents. Partner agreements and adapter configs transfer through a structured import path.
Four phases. Parallel run from week one. Cutover when you decide.
A wave model: BizTalk keeps running production until each integration is validated, parallel-run, and signed off. No big-bang cutover, no outage windows.
- Artifact inventory: orchestrations, pipelines, schemas, maps
- Custom component & .NET adapter audit
- Risk & complexity scoring per integration
- Translate artifacts to iQBus itineraries & XSLT 3.0 maps
- Custom-component re-implementation plan
- Migration wave plan with priority order
- 2–3 representative integrations on iQBus
- Parallel run alongside BizTalk - both take production traffic
- Audit & compliance verification
- Migrate remaining integrations in waves - you set the order
- BizTalk retirement, wave by wave
- Knowledge transfer & support handover
Total elapsed time depends on scope. The Discover phase produces the exact estimate before the rest of the work begins.
What our migrations look like in practice.
How iQBus de-risks the move off BizTalk. The Discover phase produces specific numbers for your environment.
iQBus’s AI converts your BizTalk maps, schemas, and orchestration logic into iQBus itineraries and XSLT 3.0 transforms. Your architects review and refine - not rewrite from scratch.
BizTalk keeps serving production while each integration runs in parallel on iQBus. Cut over wave by wave, in the order you choose - no big-bang switch, no outage window.
Tell us about your organization’s BizTalk experience.
A written modernization roadmap, tailored to your environment.
An iQBus senior architect reviews your BizTalk inventory and returns a written assessment: complexity score per integration, recommended migration wave order, indicative timeline, and infrastructure-cost comparison. No sales call required to receive the document.
- Written assessment within 5 business days of intake
- Reviewed by a Microsoft V-TSP consultant - not a generalist
- No cost. No purchase obligation. NDA on file before any inventory review.
- Result is yours to keep - share it with internal stakeholders freely
Prefer a fully delivered migration? Cerebrum City’s BizTalk Migration Services — assessment, parallel run, and wave cutover executed end-to-end by the same V-TSP–recognized team.
What integration teams ask.
Microsoft says Logic Apps is the BizTalk successor. What does iQBus give me?
iQBus gives you the governance, end-to-end transaction tracking, exception-routing, and operational rigor that ESB workloads demand - on the same Azure foundation as Logic Apps. Logic Apps is excellent for new cloud-first workflows, but it was never designed to absorb that discipline. Neither path is “outside Microsoft” - the difference is whether the platform you adopt matches the workload you’re moving, and whether your BizTalk maps, flows, and patterns carry forward instead of being rewritten.
How much of my custom pipeline components translate to iQBus?
Most of it. Custom adapters and pipeline components are inventoried during the Discover phase. The majority translate to iQBus custom function packages (deployable as .NET assemblies); a small minority require re-implementation. The Build phase produces an exact list of which components fall into which category before any work starts. For a construct-by-construct view, see how iQBus maps to every core BizTalk capability.
Can we run BizTalk and iQBus in parallel during the migration?
Yes - parallel run is built into the methodology. From Phase 03 onward, iQBus receives production traffic alongside BizTalk for a defined window per integration (typically 2–4 weeks). Both produce output, both are observed, and cutover happens only after your team signs off. BizTalk continues running until its last integration moves.
How long does deploying a new iQBus server take?
About an hour. A new iQBus environment provisions into your Azure subscription from Azure Marketplace as a managed, Azure-native runtime - no Windows servers to build, no cumulative-update projects. Migrating your existing BizTalk integrations onto it is a separate, scoped effort that follows the four-phase approach above; the Discover phase produces a concrete estimate before that work is committed to.
Does iQBus support multi-region deployments?
Yes. iQBus deploys across multiple Azure regions for high availability and data residency. A single multi-region deployment can consolidate several regional BizTalk hosts, with routing and failover handled at the Azure-native layer - the resources still run entirely inside your subscription.
What does the assessment cost?
Nothing. The Migration Assessment is free, no obligation, and the written deliverable is yours to keep regardless of whether you proceed with iQBus. We have found that the assessment itself often surfaces value the integration team can act on independently - gaps in trading-partner agreements, redundant orchestrations, audit-coverage holes.
How often does iQBus release patches and enhancements?
Continuously. iQBus ships security patches and feature enhancements on a regular release cadence, delivered as managed updates to your Azure-native runtime - no Windows fleet to patch, no cumulative-update projects to schedule. Security fixes are prioritized and applied without downtime. Because the platform runs inside your subscription, your data and IP never leave your tenant.
Customer success story
Retiring BizTalk with zero downtime and 50–70% code reuse.
Cerebrum City migrated Novelty, Inc.'s retail-partner EDI off end-of-life Microsoft BizTalk to iQBus on Azure — reusing 50–70% of existing artifacts, with zero downtime.
Greenfield, Indiana · ~140 employees
EDI on iQBus + Microsoft Azure
Try the Starter Plan in your Azure subscription, free.
Install the free Starter Plan from Azure Marketplace - free license - and run a non-production integration through it before scoping the real migration. No sales call required.
Note: Azure consumption still applies - minimum infrastructure cost about $100/month.