There are two steps to upgrading a LedgerSMB 1.4.x - 1.10.x to 1.11:
The last step must be executed for each company database that's set up.
This page contains the comprehensive version with the installation instructions for LedgerSMB 1.7 targetting a production installation from release tarballs and deals with these steps:
If you already have all of the above, please proceed to the "Preparing for first use" guide.
Company database upgrades are supported all the way back from 1.4 directly to 1.9, using the 1.9 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.9 structure, while upgrades adjust the existing structure for 1.9.
This page contains the comprehensive version with the installation instructions for LedgerSMB 1.9 targetting a production installation from release tarballs and deals with these steps:
There are two steps to upgrading a LedgerSMB 1.8.x installation to 1.8.y (x smaller than y):
The second step has to be executed for each company database that's set up.
The steps to upgrade the software differ between Docker or tarball (from source) installations.
In case the installation was created using the docker-compose infrastructure provided by the project, the upgrade should be as simple as running
This page contains the comprehensive version with the installation instructions for LedgerSMB 1.8 targetting a production installation from release tarballs and deals with these steps:
If you already have all of the above, please proceed to the "Preparing for first use" guide.
Company database upgrades are supported all the way back from 1.4 directly to 1.8, using the 1.8 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.8 structure, while upgrades adjust the existing structure for 1.8.
By far the fastest procedure for installing LedgerSMB is by using the published Docker images: Being an ERP, there are many dependencies to be installed and all of them are included in the images, with the exception of the required PostgreSQL database. There are two ways to provide the PostgreSQL functionality: by setting up a separate PostgreSQL server or by using a PostgreSQL-providing Docker container.
This page contains the comprehensive version with the installation instructions for LedgerSMB 1.7 targetting a production installation from release tarballs and deals with these steps:
If you already have all of the above, please proceed to the "Preparing for first use" guide.
There are two steps to upgrading a LedgerSMB 1.5.x/1.6.x to 1.7:
The last step must be executed for each company database that's set up.