Do we have to move to Axon 5 at all?

Not necessarily right now. The assessment answers exactly that question, including the option to stay on 4.x deliberately and plan the move instead of forcing it.

What if we want to move away from Axon instead?

We assess that too. We work technology-agnostically: Axon, EventSourcingDB or an existing relational solution — the domain decides, not the product.

Can we ship features in the meantime?

Yes. The migration runs incrementally in parallel operation so daily business does not stop.

Assessment at a fixed price of €7,500, migration from €35,000 depending on scope. The assessment is credited when you continue.

Offers

A migration path to Axon 5 with numbers instead of gut feeling

After three weeks you know what migrating to Axon 5 costs, in which order it runs and where the real risks are.

MigrationAxonAxoniq

“We are on Axon 4, the migration is due and nobody on the team has time for this”

Duration: Assessment 3 weeks, migration in iterations
Who it is for: Teams running Axon Framework in production that need or want to move to version 5
Price frame: Assessment €7,500 fixed price, migration from €35,000
Technology partner: Axoniq

Typical symptoms

The Axon version in use is ageing and dependencies can no longer be updated cleanly.
The team knows Axon from daily work, but nobody has led a major upgrade.
Sagas and projections have grown over years and nobody knows all the side effects.
A migration attempt was started and rolled back.
The decision between Axon 5 and an alternative has been postponed for months.

Outcome

Inventory: Axon usage, event store, sagas, projections, upcasters
Migration path in steps with parallel operation instead of a cut-off date
Assessment of breaking points: changed APIs, configuration, test setup, operational picture
Event store and schema evolution strategy including a fallback path
Delivery of the first slices together with your team, the rest handed over documented

How we work

01
Week 1 — inventory
We read code, configuration and the operational picture: which Axon building blocks are actually used, what the event store looks like and where custom extensions sit.
02
Week 2 — migration path
Sequence, parallel operation, test coverage and fallback path — with effort ranges per step instead of one number without basis.
03
Week 3 — risk validation
We validate the riskiest breaking point with a small spike: could the first building block migrate in parallel operation? The result sharpens the effort estimate and the fallback path.
04
First slices in production
We migrate the first areas together with your team, including tests and observability. Operations keep running.
05
Handover
The pattern is established, the remaining steps are documented. Your team finishes the migration itself — we stay only as long as it helps.

Frequently asked

Do we have to move to Axon 5 at all?: Not necessarily right now. The assessment answers exactly that question, including the option to stay on 4.x deliberately and plan the move instead of forcing it.
What if we want to move away from Axon instead?: We assess that too. We work technology-agnostically: Axon, EventSourcingDB or an existing relational solution — the domain decides, not the product.
Can we ship features in the meantime?: Yes. The migration runs incrementally in parallel operation so daily business does not stop.
What does it cost?: Assessment at a fixed price of €7,500, migration from €35,000 depending on scope. The assessment is credited when you continue.

Often combined with

First conversation on Axon migration 4.x → 5

30 minutes, no slide deck. Afterwards you know whether and how we start.