How to migrate WordPress to a VPS without losing email, forms, or SEO
Published on 2026-11-14 by frfrand
Checklist for moving WordPress to a VPS while keeping data, DNS, HTTPS, email, forms, and SEO rankings.

# How to migrate WordPress to a VPS without losing email, forms, or SEO
Changing WordPress hosting seems like a task of copying files and restoring MySQL. However, the most expensive incidents usually affect what no one tested: form messages, email DNS, certificates, images, redirects, or payments. A correct migration must preserve the business while changing the infrastructure.
Audit before moving anything
Take inventory of domain, DNS, email providers, MX records, SPF, DKIM, and DMARC, SSL certificate, PHP and database versions, cron, plugins, theme, storage, tasks, and external connections. Record current URLs and export a list of relevant pages. Check Search Console and analytics status before intervening.
Identify where the mailboxes are hosted: they can be completely independent of the web server. Never change MX records to migrate a website if you are not going to migrate the email.
Consistent backups
Obtain a verifiable copy of files and database. If there is WooCommerce, reservations, or forms that store submissions, schedule a short final synchronization window to avoid losing new data. Note down credentials and secrets that will need to be reconfigured securely; do not paste them into a public document.
Prepare the VPS
Install a compatible PHP version, database engine, and required extensions. Configure web server, reasonable limits, PHP processes, minimal permissions, external backups, and monitoring. Restore the copy in an isolated environment and test the site without touching the public domain.
Verify absolute paths, upload permissions, upload limits, outgoing email, scheduled tasks, and payment functions. Use a hosts file or a temporary domain to test, making sure not to index a staging copy.
DNS and HTTPS certificate
Reduce TTL in advance when you have control over the zone, but remember that caches can retain previous responses. Prepare the TLS certificate and check domain functionality with the new server before the final change. Modify only the necessary A/AAAA or CNAME records for the web; keep email and related TXT records.
Avoid introducing domain changes, permalink structure changes, and design changes at the same time: each change adds risks and complicates diagnosis.
Cutover and validation
During the chosen window, synchronize the latest changes, temporarily stop writes if your business requires it, change DNS, and verify that the new site is the one receiving traffic. Test real form, email reception, images, sessions, 404s, cookies, sitemap, robots.txt, and priority pages. In e-commerce, validate test purchases without generating unwanted real charges.
Keep the previous environment available for rollback until the migration stabilizes; avoid operating two independent databases accepting orders simultaneously.
Maintain positioning
If URLs remain the same, server migration normally does not require new redirects. If paths change, use permanent URL-to-URL redirects; do not send all pages to the homepage. Check canonical, sitemap, and indexing, and monitor 5xx errors, latency, and organic traffic after the change.
Frequently asked questions
### Should I move mailboxes to the VPS? No. You can keep them with their current provider while keeping their DNS.
How long does DNS take?
It depends on TTL, caches, and configuration; an exact time cannot be guaranteed.
Can I test without pointing the domain?
Yes, using local resolution or controlled staging.
Resources
DNS A, MX, and TXT records, TTL and IP changes and Google migration guide. At ArduMaker, VPS deployment and maintenance can be organized as part of the migration project.