Camunda 8 migration and adoption – safely from Camunda 7 to Camunda 8
Whether you start a new project directly on Camunda 8 or plan the Camunda 8 migration of existing process applications: with 15 certified consultants for Camunda 7 and 8, we support you from the initial assessment and migration strategy to the reality check in live operation.
Camunda consultants for Camunda 7 and 8
end of support for Camunda 7 Enterprise (standard / extended)
assessment, strategy, reality check
Camunda partner and Recognized Migration Partner
Why now is the right time
Camunda 8 is already running successfully in numerous projects. Anyone familiar with Camunda 7 quickly sees that architecture, operating models and deployment scenarios have changed significantly – which may require adjustments to your processes and systems.
Now is a good time to plan: many projects prove the reliability of Camunda 8, and there is still enough time for an orderly move before Camunda 7 reaches end of support. We help you with all key questions – whether you migrate an existing process application or start a new project with Camunda 8.
The timeline at a glance
- Camunda 7 Enterprise: end of support in 2030, extended support until 2032
- Camunda 7 Community Edition: discontinued, no further security updates – immediate action required
- Our recommendation: implement new projects directly on Camunda 8 and gain experience for the migration
What the new platform brings you
Cloud-native & scalable
Camunda 8 is a cloud-native platform based on the Zeebe engine – highly scalable, as SaaS or self-managed.
Out-of-the-box connectors
Ready-made connectors integrate widely used systems such as SAP, Kafka or Microsoft Office quickly.
Low-code meets pro-code
Low-code and pro-code in one process model: with connectors and FEEL, business users can automate without programming skills.
Agentic orchestration & IDP
Agentic orchestration and intelligent document processing open up new use cases – with clear guardrails.
Integrated Web Modeler
Forms and DMN directly from the BPMN model, plus simulation, deployment and Git integration in the Web Modeler.
One integrated platform
Modeler, Operate and Optimize work seamlessly together – with a consistent look and feel for business and IT.
Two paths to Camunda 8 – each in three phases
First, we clarify the architectural differences in a workshop and assess the maturity of your architecture and processes. Then we develop your strategy and roadmap – and prove feasibility in the reality check.
Start a new project directly on Camunda 8
For many companies, running Camunda 7 and 8 in parallel is the safest way to get to know the benefits of Camunda 8: without legacy constraints, with Web Modeler, Operate and Optimize – and with IT and business working on a shared model. Sub-processes can often be implemented directly in Camunda 8, ideal for trying out agentic orchestration without risk.
1 · Assessment
Workshop (1–2 days), differences from Camunda 7, use case selection, process review and maturity based on checklists.
2 · Planning
Define requirements and interfaces, create the data model for the process – and set the happy path for the MVP.
3 · Reality check
Build the MVP, develop job workers and connectors with your developers, establish low-code good practices and define the operating strategy.
Camunda 8 migration: moving existing processes from Camunda 7
In a Camunda 8 migration, the details matter: how tightly are your components coupled to the process engine? Which external task handlers can be reused? Based on reviews of your processes and source code, we recommend the right strategy – and test it before things get serious.
1 · Assessment
Workshop (1–2 days), checklists, differences from Camunda 7, architecture and migration scenarios. Goal: a shared understanding of the requirements.
2 · Migration strategy
Code and process review, risk analysis, strategy recommendation and a concrete roadmap. Goal: a migration plan you can start with.
3 · Reality check
Proof of concept of the migration, migration of process tests, operating strategy and process optimisation. Goal: the first steps successfully implemented.
Two migration strategies compared
Big bang
A process is deployed to Camunda 8 on a fixed cut-over date and runs there from then on.
Drain-out
The process runs in parallel on Camunda 7 and 8 until all new instances start on Camunda 8 and all old ones on Camunda 7 are completed.
The right operating strategy
- Self-hosted in your own data centre
- Self-hosted in the cloud, e.g. GCP, AWS or Azure
- Camunda SaaS
We advise you on the choice and, if required, take over operation with our managed services.
GEMA: 580+ processes orchestrated with Camunda
How business-critical processes scale on Camunda 7 and move to the cloud – the starting point for many companies before the step to Camunda 8.
Process Automation Starter Kit
Planning your first steps in process automation with Camunda 8? With our starter kit, we build a proof of concept on your technology stack.
FAQ on Camunda 8 migration and adoption
Not immediately. Support for Camunda 7 Enterprise ends in 2030, extended support in 2032. We recommend implementing new projects on Camunda 8 already and using the next optimisation of your automated processes as the trigger for migration. If you use the Community Edition, however, you should act quickly, as it no longer receives security updates.
Camunda 8 is cloud-native and highly scalable, comes with ready-made connectors for systems such as SAP or Kafka and combines low-code and pro-code in one model. On top of that, there is a more tightly integrated Web Modeler with forms, DMN, simulation and Git, plus new AI capabilities such as agentic orchestration and intelligent document processing.
Camunda 8 is a platform made up of several components, optimised for scalability, cloud operation and low-code. Its focus is the orchestration of business processes and systems via connectors and job workers. Camunda 7, by contrast, could be embedded directly into your own software as a Java library; the external task pattern was already a step towards microservice orchestration that Camunda 8 consistently continues.
With a big bang, a process switches to Camunda 8 on a cut-over date. With drain-out, Camunda 7 and 8 run in parallel until all old instances are completed. Which strategy fits depends, among other things, on the runtime of your process instances and how tightly your components are coupled – we clarify this in phase 2.
That depends on your licence. The SaaS option also has its own licensing model. We are happy to clarify this together with you and Camunda.
No. The Camunda 7 Community Edition has been discontinued and no longer receives security updates. For secure operation, we recommend moving to Camunda 8.
Your path to Camunda 8 starts with a conversation
We discuss your project in an initial call and show you how to adopt Camunda 8 smoothly.
Your contact at cimt
Board Member, cimt Group
Note: This text was created with AI assistance.