Make an inventory before moving
- Website files, databases and application environment values.
- PHP or Node.js version, extensions, scheduled tasks and background workers.
- Domains, subdomains, redirects and the complete DNS zone.
- Mailboxes, aliases, forwarders and email-client settings.
- External services such as payment gateways, CDNs, webhooks and transactional email.
Prepare the destination
- Create the website and required databases in Enhance.
- Match the application runtime closely enough to test before upgrading it.
- Import files and databases or upload a compatible Enhance backup.
- Create email addresses before uploading an Enhance email backup so addresses can be recreated.
- Use a preview or temporary hostname to test the destination before changing public DNS.
Move traffic with minimal disruption
- Lower DNS TTL in advance when you control the current zone.
- Choose a low-activity time and pause content or order changes when the application cannot synchronize them.
- Take a final source backup and import the final database or changed files.
- Change DNS to the new service and verify root, www, email and important subdomains.
- Keep the old hosting intact until the new site, SSL, forms, cron jobs and email are confirmed.
Important
An Enhance backup import does not map the primary domain automatically. Add and point the domain as a separate migration step.
Official references
Platforms and tools change over time. Use these official references for the current product documentation.