Skip to main content

    REIGN OPS · FLUXNOVA MIGRATION

    Move the engine. Keep the processes.

    Camunda 7 to Fluxnova, or Fluxnova 2.x to 3.0. We do the infrastructure half: engine, database, environments, identity, CI/CD, cutover, rollback, and performance validation. Your BPMN and DMN models come with you unchanged.

    Model changes

    None. Backward compatible

    Scope

    Fixed fee, sized to your estate

    Environments

    Dev, test, production, DR

    Rollback

    Planned before cutover, not after

    Scope your migration

    Delivered as a single-tenant dedicated instance, in our environment or in your own cloud account on AWS or Azure. Air-gapped and sovereign are in development.

    WHICH MOVE ARE YOU MAKING

    Two paths, different urgency.

    Camunda 7 to Fluxnova

    Community Edition is past end of life. Fluxnova is the compatible, openly governed path forward. No re-platform, no model rewrite, no per-core license. Timeline is yours to set.

    Fluxnova 2.x to 3.0

    Spring Boot 4, fourteen library upgrades, Cockpit retirement, and end of support for JBoss and WildFly. If you are on either app server this is not optional and it has a clock on it.

    SCOPE

    What we do, and what we do not.

    Migration is two jobs. Confusing them is how these projects go wrong. We are explicit about the boundary, and we bring Summit58 in for the functional half rather than pretending it is ours.

    iTmethods · infrastructure

    • Engine deployment and topology
    • Database migration and schema
    • Environment build across dev, test, production
    • Identity, secrets, CI/CD integration
    • Cutover planning, rollback, performance validation

    Summit58 · functional

    • BPMN and DMN process definitions
    • Business logic and rules
    • Forms and task interfaces
    • Process semantics and behavior
    • Business validation and UAT
    • Training your process modellers

    Migrating running process instances sits across both. We name an owner for it per engagement rather than leaving it to a general rule.

    Migration Readiness Guide

    Estate inventory template, compatibility checklist, environment and cutover sequencing, rollback criteria, and the questions to settle before anyone touches a database. Available shortly. Ask for it on your scoping call in the meantime.