Migration
Plan your move to EzePanel with confidence.
Understand what should be reviewed, transferred and verified when moving websites and hosting workloads to an EzePanel-managed server.
Keep the source available
while you validate the destination.
Migration paths
Start with your current environment.
Planning guides are available today. Data transfers and configuration are operator-led; the expanded migration platform is planned.
cPanelEzePanel
Explore the path Planning GuideDirectAdminEzePanel
Explore the path Planning GuidePleskEzePanel
Explore the path Planning GuideManual serverEzePanel
Explore the pathAutomated cross-panel importing is not currently offered here. See the planned migration platform.
What moves
Move the workload. Rebuild the right configuration.
Treat content, service settings and access separately. A successful file copy is only one part of a working hosting environment.
Websites & files
Transfer application files and uploads; preserve ownership and review document roots.
Databases
Export and import the application data, recreate users/grants and update application connections.
Domains & DNS
Recreate required records and hosting mappings; plan TTLs, nameservers and the traffic switch.
SSL
Reissue or deliberately transfer certificates through an appropriate secure process; test HTTPS.
Plan mailbox data, credentials, client settings, routing and delivery checks separately.
Cron & scheduled work
Recreate schedules and paths. Avoid running duplicate jobs during the transition.
FTP & account configuration
Recreate access, package/resource settings and permissions for the target account.
The migration workflow
A staged path to your new server.
Prepare and verify the destination before directing customers to it.
Assess source
Inventory websites, dependencies, data and service settings.
Prepare EzePanel
Install on a clean target and create the account structure.
Transfer data
Move files and database exports using authorized access.
Rebuild configuration
Match PHP, mail, DNS, permissions and scheduled work.
Verify websites
Test application behavior, database access, HTTPS and mail.
Switch traffic
Coordinate the final data sync and DNS or traffic change.
Confirm
Monitor the destination and retain a rollback path.
A carefully staged migration can reduce interruption, but actual downtime depends on DNS, application and service conditions.
Prepare your move
Make the cutover a deliberate decision.
Protect the source
- Source inventory
- Readable backup
- Current application dependencies
- Rollback plan
Prepare the target
- Server capacity
- PHP version & extensions
- Database compatibility
- Mail, DNS & SSL
Confirm the switch
- Functional testing
- Final data synchronization
- Cutover window & owner
- Post-move monitoring
Shared cutover guidance
Verify the destination. Preserve the recovery path.
Before changing traffic
Test websites, database connections, PHP behavior, scheduled work, mail sending and receiving, and HTTPS coverage. Compare DNS records and public addresses. Define final synchronization and a write-freeze or another consistency approach suitable for the application.
A page loading once does not validate orders, uploads, logins or mail history.
After changing traffic
Change authoritative DNS or routing only after accepting the target. Monitor customer outcomes during propagation and retain the source for the agreed verification window.
Before returning traffic to the old system, assess new data written after cutover. DNS rollback alone does not reconcile divergent databases or mailboxes. Retire the source only after confirming preservation and recovery needs.
Moving a production hosting environment?
Tell us about your source platform, workloads and intended destination.