elDoc versions overview:

• v5.9.2
• v5.9.1
• v5.9.0
• v5.8.9
• v5.8.8
• v5.8.7
• v5.8.6
• v5.8.5
• v5.8.4
• v5.8.3
• v5.8.2
• v5.8.1
• v5.8.0
• v5.7.4
• v5.7.3
• v5.7.2
• v5.7.1
• v5.7.0
• v5.6.1
• v5.6.0
• v5.5.3
• v5.5.2
• v5.5.1
• v5.5.0
• v5.4.6
• v5.4.5
• v5.4.4
• v5.4.3
• v5.4.2
• v5.4.1
• v5.4.0
• v5.3.8
• v5.3.7
• v5.3.6
• v5.3.5
• v5.3.4
• v5.3.3
• v5.3.2
• v5.3.1
• v5.3.0
• v5.2.0
• v5.1.2
• v5.1.1
• v5.1.0
• v5.0.12
• v5.0.11
• v5.0.10
• v5.0.9
• v5.0.8
• v5.0.7
• v5.0.6
• v5.0.5
• v5.0.3
• v5.0.2
• v5.0.1
• v5.0.0

Breaking changes

As a general rule, we strive to keep backwards compatibility between minor versions (e.g. 5.x to 5.y) so you can upgrade without any configuration file changes or IDP or BPM re-configuration needs.

But in case any backwards compatibility changes come even with minor version upgrade (e.g. 5.0 to 5.1) - we always mention that in Release Notes, so during upgrade - please make sure you have checked Release Notes for any breaking changes.

There are breaking changes between major versions (e.g. 3.x to 5.y), please review all Release Notes for the intermediate version when you upgrade from the older version of the elDoc system to the latest.

General rule: make sure you have a valid backup of the database before performing any upgrade.

elDoc Product Lifecycle and End of Life Policy

elDoc provided with at least 5-year software lifecycle with support and maintenance. As a general rule we provide new releases with backward compatibility and automatic upgrades, what ensures smooth upgrades from any version of the elDoc system to the latest release of the same major version.

* not early than Q2 2025