Inventory the components to move
| Component | Information to record |
|---|---|
| Website | Domain, document root, IIS bindings and redirects |
| Application | Runtime, dependencies, environment and process owner |
| Data | Databases, uploads, models and working files |
| Domains, mailboxes, messages and outbound route | |
| Operations | Tasks, backup destinations, monitoring and recovery point |
Verify the migration tools’ coverage
AdaPanel has site migration, validation and Plesk/cPanel source discovery endpoints. Connecting to a source does not establish that every application or server setting transfers automatically. Inspect discovered resources and operation warnings.
For backup-based migration, compare selected components with the manifest. A file archive does not inherently represent mail messages, databases or custom Windows tasks. Prepare a separate controlled transfer for components outside the supported workflow.
Rehearse before changing DNS
- Back up source files, databases and the required mail scope.
- Prepare compatible Windows/IIS components and runtimes on the destination.
- Transfer files and data while preserving production .env values and user uploads.
- Securely re-enter secrets and account permissions that do not transfer between machines.
- Use a controlled mapping of the real hostname to the target IP to test HTTPS and application flows.
- Ensure the test copy’s workers, payments and emails cannot perform production operations twice.
Final synchronization and DNS cutover
New data can be created on production after the first copy. Plan a brief write pause or application-appropriate synchronization. Changing DNS before the final data transfer can leave users writing to different servers.
Plan TTL values in advance and change only the required records. Preserve mail and verification records on the same domain. Keep the previous system until real traffic, error rates and background jobs are verified on the new server.
Planning a rollback
Rollback is more than pointing DNS at the old IP. Orders, uploads or messages created on the new server may require reconciliation. Agree on acceptance criteria and a rollback decision before migration. Retain the previous server and backups until verification is complete.
Frequently asked questions
Will copying .env make every secret work?
Not necessarily. Machine-bound protection, local paths and destination database accounts may require separate changes.
Can I test before changing public DNS?
Yes. Controlled name resolution or an appropriate test connection can preserve the real hostname while targeting the new server. Prevent production side effects separately.