Backup the data from the old system using the Admin Web App, or see the instructions at Section C.4.6, “db-export and db-export-to” for the command-line variant.

Copy the backup zip file created in the backup step onto the new server.

Stop the SavaPage Server by running the stop script. See Section C.5, “Stopping and Starting the Server”.

Restore the data from the old system into SavaPage on the new server by following the Database Import instructions. The import commands need to be run as the savapage user.

Migrate the database Encryption Keys by copying the encryption.properties file at location /opt/savapage/server/data/ from the old server to the same location on the new server. Overwrite the existing file on the new server. Make sure this file is owned by savapage , and restrict access by executing:

sudo chown savapage:savapage encryption.properties
sudo chmod 600 encryption.properties

If present, migrate the User Name Aliases and Internal Groups by copying the username-aliases.txt and internal-groups.txt files at location /opt/savapage/server/data/conf/ from the old server to the same location on the new server. If the alias file depends on users from a User Source on the local Unix system, be sure that these users also exist on the new server.

If present, migrate any messages in the email outbox by copying the files at location /opt/savapage/server/data/email-outbox/ from the old server to the same location on the new server.

If present migrate the Document Store from the old server to the same location on the new server.

Migrate all customization files to the new server. See Chapter 20, Customization and Appendix K, PPD Extensions.

Start the SavaPage Server by running the start script. See Section C.5, “Stopping and Starting the Server”.

Check that all data has been migrated correctly and the system works as expected by comparing Users and Documents data in the old and new Admin Web App.