Moving a portfolio of client websites requires more care than moving one personal site. Each account may have different software, email, DNS, storage, ownership, and business priorities. A written migration plan reduces surprises and gives clients a clearer idea of what will happen.
HTech Solutions reseller plans include a stated number of free eligible cPanel migrations. The following process will help you prepare the accounts, communicate with clients, and verify the result.
1. Build a complete account inventory
Begin with facts, not assumptions. Create one record for every cPanel account and list all domains connected to it. Record:
- Primary domain and additional domains.
- Current hosting provider and server details.
- Whether working cPanel and WHM access is available.
- Storage use, database sizes, and major files.
- Website software and required PHP version.
- Email accounts, forwarders, mailing lists, and filters.
- DNS provider, nameservers, and important DNS records.
- Third-party services for email, forms, payments, or verification.
- Business owner, technical contact, and preferred migration window.
This inventory also reveals accounts that should be separated or cleaned up before the move.
2. Confirm compatibility and migration scope
cPanel-to-cPanel transfers are usually the most direct because the source and destination share a familiar account structure. Even then, access restrictions, unusually large accounts, old software, custom server modules, or damaged backups can require additional work.
Send the inventory to HTech Solutions through a secure support request. Confirm which accounts are eligible, how many migrations your plan includes, what credentials are required, and which items need manual attention.
Do not send server credentials through ordinary email
Use the secure method provided for the migration request. Share only the access needed for the work, and change temporary or transferred credentials when the migration is complete.
3. Protect the source before copying anything
A migration is not a substitute for a backup. Confirm that current recoverable copies exist before changes begin. Avoid major website updates, mailbox moves, or account restructuring during the migration window unless they are part of the plan.
For active sites, decide how late-arriving orders, form submissions, comments, and email will be handled while data is copied and DNS changes propagate.
4. Plan DNS and email carefully
DNS determines when visitors and mail systems begin using the new destination. Before changing nameservers or records:
- Export or record the complete existing DNS zone.
- Identify third-party email records such as MX, SPF, DKIM, and verification entries.
- Confirm external services, subdomains, and API endpoints.
- Lower relevant TTL values ahead of the move when appropriate and permitted.
- Decide whether the domain will change nameservers or only selected DNS records.
Email deserves its own checklist. Determine whether mailboxes are hosted in cPanel or through a third party such as Microsoft 365 or Google Workspace. A website migration should not overwrite working external email records.
5. Transfer in controlled groups
Do not begin with every high-priority customer at once. Start with a representative lower-risk group that exercises the workflow: a standard website, a site with a database, and an account with cPanel-hosted email if that service is in scope.
Once those accounts are verified, schedule the remaining groups by business priority and complexity. Keep a status column in the inventory so the team can see which accounts are pending, copied, tested, switched, and completed.
6. Test before changing production DNS
A copied account is not automatically a completed migration. Test the destination wherever possible before directing normal traffic to it. Review:
- Home pages, internal pages, images, and downloads.
- Database connections and dynamic content.
- Administrative logins and password-protected areas.
- Forms, notifications, scheduled tasks, and integrations.
- SSL readiness and redirect behavior.
- Email accounts and routing when email is part of the move.
- Error logs and unexpected PHP warnings.
Involve the person who knows the website best. A technically successful transfer can still miss a business-specific workflow.
7. Switch DNS and monitor both environments
Make the approved DNS change, record the time, and continue checking the website from more than one network. DNS caches update at different times, so requests may reach both servers during the transition.
Keep the source account available until the destination has been verified and the agreed transition period has passed. Deleting the source immediately removes a valuable recovery option.
8. Complete the post-migration review
After traffic has moved, review SSL, forms, email, analytics, scheduled tasks, backups, and account access again. Update internal documentation with the new server details, nameservers, support path, and responsible contacts. Remove temporary access and rotate credentials where appropriate.
Finally, notify the client that the move is complete and explain any action they must take. A concise completion message builds confidence and provides a written record.
Prepare your move with HTech Solutions
Choose a plan based on separate cPanel account capacity, storage, bandwidth, and migration allowance. Then open a support request with the account inventory so eligibility and timing can be reviewed before changes begin.
Compare HTech Solutions reseller plans or contact support about an existing reseller portfolio.