Services
Server Migration
Moving accounts, sites and mail between servers or panels with a short, planned cutover window agreed with you in advance.
What’s included
- cPanel → cPanel, DirectAdmin → DirectAdmin and cross-panel migrations
- DNS cut-over planned to keep the interruption short, inside the agreed window, with mail synced again after the switch
- PHP, MariaDB and LiteSpeed versions matched or upgraded deliberately
- Post-move checks: mail deliverability, SSL, cron jobs, permissions
- Old server kept as a fallback until you say it’s safe to retire
- A written handover report: what moved, what was checked and what is still on the old server
Why every migration is verified
Migration tools can report success while something is missing. Admins on the cPanel community describe the Transfer Tool finishing without errors while databases and mailboxes were missing, two domains skipped without a warning, and Google MX records broken after the move. We saw the same pattern ourselves: in our FreePBX restore test a backup exited with code 0 while the extensions and trunks were not in it. So a migration here is finished when the checks below pass on the new server, not when the tool says it is done.
What we check before you sign off
| Item | How it is checked | Passes when |
|---|---|---|
| Domains and subdomains | Lists from the old and new server compared | Every domain, subdomain, alias and parked domain is present |
| Mailboxes | Count and size per mailbox, old against new, plus a test login | Counts and sizes match, or the difference is explained |
| Forwarders, autoresponders and filters | Exported and compared | Nothing missing |
| Databases | Number of databases and tables, row counts per table | Counts match and each site connects to its database |
| DNS zones | Record-by-record comparison, including MX, SPF, DKIM, DMARC and custom records such as Google or Microsoft 365 MX | Every record is present with the right value |
| Websites | Each domain loaded on the new server before DNS changes (hosts file or a temporary address) | Pages load without errors, with the right PHP version |
| SSL certificates | Certificate checked for every hostname after the switch | Valid, trusted certificate on each name |
| Mail flow | Test messages sent and received, headers read | Delivery works both ways with SPF, DKIM and DMARC passing |
| Cron jobs, permissions and custom settings | Compared with the inventory from step 1 | Present and working |
You get the results in the handover report. Anything that does not pass is fixed before you are asked to sign off, and the old server stays untouched until then.
Email during the switch
- Passwords and settings: in cPanel-to-cPanel and DirectAdmin-to-DirectAdmin moves, mailboxes keep their passwords, forwarders and filters. On cross-panel moves we test one mailbox first and tell you before the switch if anyone has to set a new password.
- Mail apps: if Outlook, phones and other apps connect to a name such as mail.yourdomain.com, users normally need no new settings once DNS points to the new server; some apps may ask once to accept the new certificate or re-enter the password. If they use the old server’s own hostname or IP address, they need new settings, and you get the exact list before the switch.
- Mail that arrives during the change: until every sender sees the new DNS records, some mail can still reach the old server. It is copied across in the final sync, synced again 24 hours after the switch and once more before the old server is switched off. Keep the old server for at least 7 days after the switch; we tell you when it is safe to cancel it.
- Contact forms and apps that send mail: SMTP settings in WordPress, invoicing tools and other scripts are listed and tested, because a form that silently stops sending is easy to miss.
Pricing
A fixed quote, agreed before anything moves and before you share any access. It is a one-time payment for the migration, not a subscription. The quote depends on:
- the number of accounts, domains and mailboxes
- the total size of files, mail and databases
- same-panel or cross-panel (for example cPanel to DirectAdmin)
- how the old server can be reached, and whether the switch has to happen outside business hours
If the job turns out larger than described, you get a revised quote before any extra work is done.
Build an estimate: choose what you are moving and the price updates as you go. The fixed price is confirmed after a free check of the old server, before anything moves.
All prices are in USD. Payment by card, bank transfer or Payoneer, with a proper invoice for every engagement.
How a server migration is planned
- Inventory: accounts, domains, mailboxes, databases, cron jobs and any custom configuration on the old server.
- Test migration: a copy of the accounts is moved first so sites can be checked on the new server before anything changes for visitors.
- DNS preparation: TTLs are lowered at least a day ahead so the final switch spreads quickly.
- Final sync and cut-over: at a time agreed with you in advance, outside your busiest hours. Shops and sites that take orders or sign-ups are paused for the final database copy, usually for under 30 minutes, so nothing written during the move is lost. Then a last sync of files and mail, and DNS or IP changes.
- Verification: websites, SSL certificates, mail sending and receiving, cron jobs and file permissions are checked.
- Fallback: the old server stays available until you confirm it can be retired.
Cross-panel moves such as cPanel to DirectAdmin need extra mapping for mail forwarders, DNS templates and PHP settings, which is included in the quote.
Access and your data
- We work with a temporary SSH key or panel login on each server. Never send passwords by email or in the contact form.
- Nothing is deleted on the old server. You decide when to retire it, after you have signed off.
- Our access is removed at the end, and the handover report lists what was removed.
At a glance



Official documentation we work from: cPanel & WHM documentation, DirectAdmin documentation and the AlmaLinux wiki.
Frequently asked questions
Will my sites go down during server migration?
A planned migration uses low DNS TTLs, a test migration and a final sync at a time agreed with you, so the interruption is short. Shops and sites that take orders or sign-ups are paused for the final database copy, usually for under 30 minutes. The old server keeps running until you sign off, so the switch can be reversed.
Will email stop working during the migration?
Mail keeps being delivered. Mail that still reaches the old server while DNS changes is copied across in the final sync, again 24 hours after the switch and once more before the old server is switched off. Mail apps that use mail.yourdomain.com normally need no changes.
What if something is missing after the move?
That is what the checks are for: domains, mailboxes, databases, DNS records, SSL and mail flow are compared with the old server before you sign off, and anything missing is fixed first. The old server is not touched until then.
Can you migrate between different panels?
Yes, including cPanel to DirectAdmin and DirectAdmin to cPanel, with mail forwarders, DNS templates and PHP settings mapped carefully.
How is a migration priced?
A fixed one-time quote based on accounts, data size and whether panels differ, agreed before anything moves and before you share access.
What access do you need, and is it removed afterwards?
A temporary SSH key or panel login on both servers. Never send passwords by email. Access is removed at the end and listed in the handover report.
