Back up a complete installation
Save the database, config/app.php, private storage/, installation-specific uploaded assets and the matching release information. Preserve the original application encryption key. Include the external private licence directory created for this installation under the PHP account's .emaila-product-licences/ directory, or the approved external directory used by your host.
Do not put private configuration, database exports, identity keys or customer files into Git or a public web directory. Use restricted storage and a suitable retention schedule. Arrange a consistent database/file snapshot using your host's supported backup tools.
Test recovery privately
Restore to an isolated, restricted environment before a production cutover. Review cron jobs, SMTP, payment connections and other external services so the copy cannot contact real users or providers. Do not use a backup to operate a second licensed production installation.
Verify owner and limited-user sign-in, business and template access, an existing project/case, attachments, private-field decryption and archived work. Preserve the original keys; a fresh key cannot decrypt data encrypted by the old installation.
Restore without reinstalling
The empty-database installer is not a restoration tool. Restore matching configuration, database and files according to the release's recovery instructions. Keep the external licence path and its Unix ownership valid. If you cannot retain the installation identity, use the issuer's replacement process rather than generating a new identity and expecting an old activation code to work.
For hostname changes, follow the domain move guide.