Skip to main content
This section covers migrating between major versions of the Midaz Helm chart, including breaking changes, migration steps, and configuration mapping.

​
Migration paths

These paths stop at v5.x. The current chart line is v8.x, and the hops beyond v5 carry their own breaking changes — most notably v7.0.0 (the onboarding and transaction services were removed; everything runs in ledger) and v8.4.0 (the otel-collector-lerian subchart is no longer installed and its schema now rejects legacy keys). Those hops are not yet covered by a page here; read the chart’s own upgrade notes at charts/midaz/docs/ (UPGRADE-7.0.md, UPGRADE-8.x.md) before going past v5.x, and see Upgrade guide for the current upgrade procedure.

​
Which path should I choose?

  • v4.x → v5.x: Most common. Introduces the unified Ledger service and CRM integration.
  • v3.x → v4.x: RabbitMQ dependency change (Bitnami → Groundhog2k) and BitnamiSecure images.
  • v3.x → v5.x: Direct jump that addresses both v4.x and v5.x breaking changes in a single upgrade.
For routine upgrades within the same major version, see Upgrading Midaz Helm.