Keep a complete private backup
Back up the database, config/accounts.php and private storage/ together. The original encryption keys must remain paired with the data. Store backups outside the web root with restricted access.
Prove the recovery
Restore to a private isolated environment first. Verify balances, documents, attachments and decryption before planning a live cutover. Review mail, payment connections and queued work so the test copy cannot contact customers or providers accidentally.
Change the licensed domain
The listed one-time USD 69 package covers one changeable domain. Prepare the new hostname and HTTPS, use the available licence-transfer process, then update the installation's canonical address in accordance with its release instructions. A transfer does not authorize two live production copies.
Do not upload executable ZIP updates through a legacy browser tool or force a reinstall to change a hostname. Use a reviewed product release and the matching backup procedure. Updates, branding and support terms are confirmed separately with the purchase.
Include the external licence directory
Back up the actual external directory selected by ORBIT_LICENSE_CONFIG, including the preparation kit's identity and signed state. Earlier browser-prepared installations may use the PHP account's .emaila-product-licences/ directory. Retain that original path rather than creating a replacement. Keep the licence directory, config/accounts.php, storage and database together with their restricted ownership and permissions.
Retain the exact release archive and review current terms on the product page. Domain transfer and replacement of a lost installation identity are separate operations. A backup or old setup code does not authorise a second live installation.