Skip to main content

Moving to Another Server

Move the database, files, and domain configuration as one consistent deployment. Do not run the old and new copies simultaneously with the same installation identity.

Migration order​

  1. Schedule a maintenance window and enable maintenance mode for the site and cabinet.
  2. Create a verified database and file backup.
  3. Transfer the application, src/config.php, data, and internal_data.
  4. Import the database and update local connection settings if required.
  5. Configure Nginx/Apache, HTTPS, ownership, and permissions.
  6. Test through a local hosts entry before changing DNS.
  7. Test connection, login, settings upload, and update checks.
  8. Switch DNS and monitor logs until the old TTL expires.

If the protected identity was lost, revoke the old installation in the project card and enroll the new server. This does not require reinstalling the client database.

After switching, verify registration and login, email delivery, payment callback URLs, uploads, cookie domain, and cache clearing. Keep the old server closed until verification is complete, then remove its working secrets and user data.