Skip to main content
CRM and Fees guidance marked legacy on this page applies only to an existing legacy release. Midaz v4 deploys the unified Ledger and serves CRM and Fees on /v2.
Version numbers in this section refer to Helm chart major versions, not Midaz application versions. The chart v5 line introduced the Ledger workload. Midaz application v4 now uses the unified Ledger regardless of that historical chart numbering.
The Helm repository retains a crm.enabled workload and the plugin-fees-helm chart for older application releases. These are legacy compatibility surfaces, not the Midaz v4 deployment model. 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 chart line has moved on. The hops beyond v5 carry their own breaking changes, most notably:
  • v7.0.0 removed the onboarding and transaction services, the Console, and NGINX. Onboarding and Transaction run in ledger. CRM and Tracer remain separate optional workloads.
  • v8.4.0 no longer installs the otel-collector-lerian subchart, and its schema now rejects legacy keys.
No page here covers those hops yet. Read the chart’s own upgrade notes at charts/midaz/docs/ (UPGRADE-7.0.md, UPGRADE-8.x.md) before going past v5.x. 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.