Everything BizTalk does.
Cloud-native on Azure.
Full capability parity — schemas, maps, orchestrations, pipelines, adapters — with live, built-in tracking. Migrated by an AI tool, built by the original BizTalk architects.
Free assessment · Senior architects · Runs in your Azure tenant
BizTalk stopped at 2020.
The clock is running.
BizTalk Server 2020 is the final major version — with no successor on the roadmap. Migrating on your timeline beats a forced cutover later.
A replacement — not a rewrite.
Every core BizTalk construct maps across, then modernizes: no build cycles, no server farms, no proprietary IDE.
| Capability | Microsoft BizTalk | iQBus |
|---|---|---|
| Message schemas | ✓ XSD Visual Studio project | ✓ XSD Web console — no IDE |
| Transformation / mapping | ✓ Maps (BTM) Functoids | ✓ iQBus Maps XSLT 3.0 + custom functions |
| Message pipelines | ✓ Receive / send pipelines | ✓ Custom pipelines Deterministic flow |
| Adapters / connectivity | ✓ Adapter pack | ✓ Ports & adapters + Azure-native connectors |
| EDI / HL7 / FHIR | ✓ EDI & HL7 | ✓ EDI, HL7 & FHIR |
| Tracking & monitoring | ✕ Not native Separate BAM / HAT add-ons | ✓ Built-in tracking UI OpenTelemetry, bottleneck detection |
| Hosting model | ✕ On-prem server farm SQL Server, host instances | ✓ Serverless on Azure Scales to zero, your tenant |
| Deployment | ✕ Build & redeploy Restart host instances | ✓ Configuration, live No builds, no restarts |
| Product roadmap | ✕ Ends Apr 2030 No successor version | ✓ Actively developed Continuously shipped |
Your artifacts, converted automatically.
Point the AI at your BizTalk solution. It reads every schema, map, pipeline, and orchestration — then generates the iQBus equivalent, reviewed by our architects before anything ships.
BizTalk source
AI
iQBus output
Connect estate
Upload your solution or point at your repo. The AI inventories every artifact.
AI conversion
Maps become XSLT 3.0, orchestrations become itineraries — automatically.
Architect review
Original BizTalk architects validate output. Nothing ships unreviewed.
Deploy in tenant
Approved config deploys serverless into your Azure tenant. No downtime.
We didn't just learn the rules
of enterprise integration.
We helped write them.
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
See your estate, mapped to iQBus.
Send us your integration landscape. We'll return a tailored roadmap — artifact inventory, AI-conversion coverage, and a phased plan — at no cost.
You'll speak with a senior integration architect, not an SDR. Response within one business day.
BizTalk migration, answered.
Is iQBus a genuine BizTalk replacement?
Yes. iQBus provides capability parity with every core BizTalk construct — schemas, maps, orchestrations, pipelines, and adapters — while running serverless on Microsoft Azure. It's built by the original Microsoft BizTalk Server architects at Cerebrum City as the cloud-native evolution of the platform.
How does the AI migration tool work?
The iQBus Migration AI inventories your BizTalk solution, then converts each artifact to its iQBus equivalent: XSD schemas migrate as-is, BizTalk Maps become XSLT 3.0 iQBus Maps, orchestrations become declarative itineraries, and pipelines are rebuilt on the deterministic iQBus pipeline. Every conversion is reviewed by a senior architect before it ships.
When does BizTalk Server support actually end?
BizTalk Server 2020 is the final major version. Mainstream support ends in April 2028, and paid extended support runs until April 2030 — after which it is fully unsupported. There is no announced successor, which is why planning your migration now avoids a forced, rushed cutover later.
Do we have to migrate everything at once?
No. Migrations are phased, and many customers run BizTalk and iQBus side by side during transition. Cerebrum City can also support and extend an existing BizTalk estate — including end-of-life versions — until you're ready to move. See our full BizTalk migration approach for how a phased cutover is scoped and sequenced.
Where does iQBus run — and who can see our data?
iQBus deploys inside your own Azure tenant with Entra ID integration, encryption, and audit controls. Your messages and data never leave your environment.