Your IBM BAW migration,
mapped.
IBM Business Automation Workflow is actively developed, so there's no platform-wide shutdown here. What does age out on a fixed schedule is each individual version. If your team has decided to move off BAW, this guide covers the version reality, the destination options, and what the project involves.
No platform-wide deadline
IBM continues to develop and support BAW. Individual versions age out on a published schedule, most recently 23.0.x on April 30, 2026.
Not a platform shutdownIBM continues to develop BAW on a Continuous Delivery model: one product line with frequent updates, not a fixed end-of-life date for the platform itself. IBM
But versions do expireBAW 23.0.x reached end of support on April 30, 2026. Since then it can no longer be purchased and IBM no longer supports it without a paid extension. IBM
Newer releases get 3 yearsThe initial delivery of BAW 24.0.x carries proactive security fixes for a 3-year base support period from release, under IBM's standard lifecycle policy. IBM
12 months' notice if withdrawnIf IBM ever withdraws the BAW offering entirely, its policy is to announce end of support at least 12 months in advance, with an optional paid extension. IBM
Often a cost decision, not a forced oneIndependent comparisons report BAW's licensing and implementation costs as high relative to alternatives, which is what drives most migration decisions, not a shutdown clock.
The Complete IBM BAW
Exit Playbook
The version-by-version reality, destination options (Power Automate, Appian, Pega, Camunda, ProcessMaker), a process-inventory method, and what the rebuild actually involves. Written for teams running the whole migration, not just reading about it.
Get the playbook
Enter your work email and it opens immediately, no waiting on a follow-up.
By submitting, you agree to be contacted about this. See our Legal & Disclaimers.
No spam. Unsubscribe anytime.
What's actually changing, and what isn't
IBM Business Automation Workflow is not being retired as a product. What has a real, published date is each specific version. This guide treats the move as a modernisation or cost decision, not a race against a platform shutdown.
BAW as a product
BAW ships on a Single Stream Continuous Delivery model: one current version, updated frequently, rather than the old major-release cadence. Staying current is a valid path; there's no platform-wide cut-off forcing a move.
BAW 23.0.x
This specific version line was withdrawn from support on April 30, 2026: it can no longer be purchased, and runs unsupported without a paid extension.
BAW 24.0.x
The 24.0.x line carries proactive security fixes for a 3-year base support period from its release, under IBM's standard support lifecycle policy.
IBM's withdrawal policy
Should IBM ever withdraw BAW as an offering, its stated policy is at least 12 months' advance notice, with an optional paid support extension, not an abrupt cut-off.
Which version are you actually running?
This is not a platform-wide deadline check. Tick your version, then generate a summary of your real support status.
…
Get this as a PDF
A short summary of your version's support status, sent to your inbox.
By submitting, you agree to be contacted about this. See our Legal & Disclaimers.
The dates that actually apply
There is no single platform deadline. What matters is which version you're running, and when that specific version ages out.
IBM's support lifecycle policy
Cases can be opened for any update within the last two years, or a supported Long-Term Service Release. Staying within that window is what keeps you supported. IBM
BAW 23.0.x withdrawn from support
This version line can no longer be purchased and is no longer supported without a paid extension after this date. IBM
BAW 24.0.x base support window
The current release carries proactive fixes and security corrections for three years from its release date, under IBM's standard policy. IBM
What's driving BAW migrations
You've made the decision to migrate. This section covers the context behind that decision and the factors worth carrying into your planning, each attributed to its source.
Licensing cost adds up
BAW doesn't publish list pricing; costs are quoted per deployment. Independent comparison sites report ranges from roughly $500/month for a single-user small deployment to $30,000+/month at 100 seats, with implementation, customisation and training as separate line items.
Reported as pricier than some alternatives
Third-party comparisons describe BAW's initial cost as high relative to platforms such as Nintex Process Platform or Camunda, which are noted for lower setup cost. Treat this as a reported comparison, not a fixed fact.
Complexity for simpler processes
Reviewers describe BAW's cloud migration path as lagging more cloud-native BPM tools in agility, and as more machinery than many simpler processes actually need.
Version currency is an ongoing cost
Because support tracks the specific version you run, staying supported means budgeting for periodic upgrades, not a one-time decision. Some teams migrate instead of carrying that recurring cost indefinitely.
Where BAW workloads go next
The right destination depends on how M365-committed you are and how complex your processes are. None of these is a like-for-like swap.
Power Automate
The default pick if your organisation already runs Microsoft 365. Deep platform integration, though long-running or highly complex case-management processes need a state-machine design to work within its run limits.
Appian
Positioned for rapid deployment and case management at enterprise scale, often evaluated by teams wanting to move fast without a long implementation cycle.
Pega Systems
Known for AI-powered BPM and decisioning; typically evaluated by larger enterprises already invested in Pega's broader platform.
Camunda
A process-orchestration engine aimed at coordinating people, systems and AI workflows with less platform overhead; often chosen by engineering-led teams.
ProcessMaker
Positioned as a more affordable option for small and mid-sized deployments that don't need Pega- or Appian-scale infrastructure.
How to choose your destination
Start from your process requirements, not from a vendor name. Score every candidate, including staying on a current BAW version, against the same questions.
- →Is your organisation already committed to Microsoft 365, or is the field genuinely open?
- →How long do your longest-running cases and approvals need to stay open?
- →Is your process complexity closer to simple approvals or heavy case management?
- →What's your real budget: licensing plus implementation, customisation and training?
- →Who will build and maintain this: professional developers, or a mixed citizen/pro team?
- →What's your exit cost if this platform's terms or pricing change later?
What a BAW migration involves
Case-management and BPM migrations are rebuilds, not conversions. A structured pass keeps scope honest and avoids migrating processes nobody uses.
Inventory your processes
Catalogue every active process, case type and integration running on BAW, with owners and real usage, not assumed usage.
Triage
Retire processes that are duplicated, unused or better replaced by a simpler tool before you rebuild them on anything.
Score complexity
Separate simple, linear approvals from heavy case-management processes with parallel branches, SLAs or complex data models.
Map to a target
Assign each surviving process to a destination based on runtime needs, integration complexity and who will maintain it.
Migrate data and case history
Move case data, documents and audit history with dedicated tooling; this is a data move, not a logic move.
Rebuild process logic
Recreate rules, routing and forms on the target platform, optimised for its model rather than copied verbatim from BAW.
Test, train and cut over
Run parallel validation on live case types, train process owners, and cut over in planned waves rather than all at once.
“We have been through the whole process from BAW on prem to CP4BA (SAAS), and adding BAW Case and BAI functionality as well.”
Playbooks, guides and templates
Everything you need to plan and run the migration, in one place.
The IBM BAW Exit and Migration Playbook
The version reality, destination options, and a seven-phase method.
View the PDFarrow_forwardThe Step-by-Step Migration Guide
The sequence in order, with the trap to avoid at each step.
View the PDFarrow_forwardMigration Cost & Effort Estimator
Size both sides: what you pay to stay, and what it costs to rebuild elsewhere.
View the PDFarrow_forwardProcess Inventory & Readiness Template
Inventory, score, and triage every process and case type before you migrate.
View the PDFarrow_forwardThe Version Exposure Report
Which version you run, its support window, and recommended next steps.
View the PDFarrow_forwardQuestions teams ask
Drawn from IBM's own lifecycle documentation and independent comparison sites, answered plainly.
Is IBM Business Automation Workflow being discontinued?expand_more
No. IBM continues to develop and support BAW on a Continuous Delivery model. What has fixed dates is each specific version, not the platform as a whole.
What actually happens on April 30, 2026?expand_more
That's the end-of-support date for the BAW 23.0.x version line specifically. It can no longer be purchased, and runs without standard IBM support after that date. IBM does offer paid extended support through April 30, 2030, but only for the 23.0.2 delivery, and only critical defects and high-severity security fixes in the first 12 months of that extension.
If we're on a current version, are we affected?expand_more
Not by that date directly. But you inherit the same pattern: your version will eventually age out on IBM's schedule, so staying supported means planning for periodic upgrades.
Why do teams migrate off BAW if it isn't being killed?expand_more
Mostly cost and complexity. Independent comparisons report BAW's licensing and implementation costs as high relative to alternatives, and its architecture as more than many simpler processes need.
Is there a straightforward converter to another platform?expand_more
No. Like other enterprise BPM platforms, moving off BAW means rebuilding process logic, forms and integrations on the target platform; content and case data migrate separately from the logic.
What's the realistic alternative if we're already on Microsoft 365?expand_more
Power Automate is the most commonly evaluated option for M365-committed organisations, with the caveat that long-running cases need a state-machine design to work within its run limits.
How long does a BAW migration take?expand_more
It depends primarily on how many processes are genuinely active and how complex they are, which is why inventory and triage come before any rebuild work begins.
Every source we pulled from
Grouped by who published it. Lifecycle dates are IBM's own; cost and comparison figures come from independent review sites and should be treated as reported ranges.