How do you actually justify a bpm migration to finance when you're paying for eight separate ai subscriptions on top?

I’m building a business case for migrating from Camunda to an open-source BPM setup, and finance is rightfully skeptical. We’re not just replacing one line item with another—Camunda licensing is a known cost, but open-source migration has ancillary costs. We need new infrastructure, integration work, team training.

What’s making the case harder is that we also have eight separate AI subscriptions scattered across the org. We’re paying for OpenAI, Claude access, Anthropic, a couple others. Each one has a different cost structure and justification. When I try to show finance that consolidating those into a single unified AI subscription reduces our total cost of ownership for the migration, the conversation gets muddled because those AI costs aren’t currently in the same bucket as BPM licensing.

Finance sees them as distinct budget lines. We’re asking them to potentially change how they allocate budget, not just to accept a lower total spend.

I’ve built ROI models that show the migration pays for itself in saved licensing, but none of them account for the friction of actually consolidating our AI tooling at the same time. That’s a real saving, but it’s also a real complication during migration.

When you’re presenting a BPM migration business case that includes subscription consolidation, how do you actually structure the conversation with finance? Do you separate the BPM and AI consolidation arguments, or do you try to tie them together? Has anyone actually gotten finance to buy in when you’re essentially asking them to rearrange multiple internal budget lines at the same time?

seperate them. finance loves simple comparisons. BPM migration case stands alone. AI consolidation is a bonus if it happens, not a requirement for ROI. mixing them confuses the conversation.

frame it as risk reduction too. fewer subscriptions = less vendor lock-in. that usually resonates with CFOs more than pure cost savings.

Show current Camunda cost vs open source + support. Separate AI subscription consolidation as operational improvement, not migration driver.

We structured our case by isolating the open-source migration ROI first—Camunda licensing savings, infrastructure costs, implementation timeline. That’s the core case finance evaluates. Then, separately, we quantified what consolidating AI subscriptions would save quarterly, and presented that as an optional upside if we managed integration properly. Finance approved the core migration, and the AI consolidation happened gradually as we onboarded workflows into the new platform. We realized about 60 percent of projected AI savings in year one because we staggered implementation. The key was not making AI consolidation a prerequisite for BPM migration approval.

The harder conversation was with IT procurement about managing two simultaneous platform transitions. Finance approved the business case, but IT had concerns about supporting both systems in parallel during migration and managing the consolidation complexity. We had to commit to a specific cutover timeline with clear milestones to get buy-in. The business case finance approved looked good on paper, but implementation complexity was the actual constraint.