List the domains you need, website technology, file sizes and databases.
If you use email too, count the mailboxes and their stored message volumes. Before migrating, check access to the current provider and the available backup options.
1. List your requirements
| Area | What details to provide |
|---|---|
| Website | A business website, WordPress site, online shop or custom application. |
| Domains | The number of managed domains and subdomains. |
| Files | Current size and expected growth. |
| Database | Count, size, type and version. |
| The number of mailboxes and volume of existing messages. |
2. Check during handover
- The delivered service and limits match the order.
- The control panel address, file access and destination folder are available.
- SSL, backup and restore procedures are defined.
- You verified operation with a test upload and test email.
3. Run a short, repeatable acceptance test
- Open the final domain over HTTP and HTTPS. Check the intended redirect and certificate.
- Sign in to the application and create test content that can be removed afterwards. A real save operation is needed to meaningfully verify the database connection.
- Send to your own external test mailbox, then reply from it. Test the website form's email sending separately.
- Check the scheduled task's result, not just that a schedule exists.
- Download or locate a recent backup and agree on the test restore procedure.
4. What makes a handover incomplete?
If file access is missing, backup contents are unknown or a form reports success without delivering the email, handover is not yet verified. Record the gap, test time and expected result. Request access through a secure channel; never put passwords in a public support ticket.
