Move a website from shared hosting to a VPS in a controlled overlap: inventory every dependency, lower DNS TTL when appropriate, create and verify backups, build a compatible and secured VPS, restore the files and database, recreate SSL, cron, mail and DNS services, test privately, then change DNS and monitor both servers. Keep the shared account online until real traffic and transactions are stable.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What changes when you move to a VPS
Shared hosting bundles your site with a provider-managed operating system, web server, runtime, database and control panel. A VPS gives you an isolated virtual server and more control, but you become responsible for much of the stack. The migration therefore moves more than HTML and images: it moves application state and the services that make the site reachable.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A successful cutover preserves four things:
- Content: source files, uploads, themes, plugins and hidden configuration files.
- State: databases, user accounts, orders, comments, sessions and other records that change over time.
- Services: web-server rules, runtime extensions, scheduled jobs, SSL renewal, mailboxes and forwarding.
- Reachability: DNS records, firewall rules, API allowlists and the domain’s canonical HTTPS behavior.
Do not cancel the shared plan when the new server first displays the homepage. The old host is your fallback while DNS caches expire and while you confirm that writes, mail and background tasks work on the VPS.
Choose the VPS operating model before you build
The server model determines who performs routine administration and which migration tools are available. No universal VPS size or provider ranking is established by the migration procedures; select resources from your measured traffic, memory use, storage and database workload.
#1 Best Overall
- 2.80 GHz processor speed ensures efficient operation with consistent reliability
- Intel Xeon 2.80 GHz processor provides enterprise-grade performance with built-in security and remote management capabilities
- Quad-core (4 Core) processor core helps server process data quickly and reliably for maximum productivity
- 1 processors supported for faster processing and improved access to data, optimizing performance under heavy loads
- With 16 GB memory, you can multitask between applications seamlessly, keeping productivity high and response times quick
| Option | Administrative responsibility | Control panel and tooling | Best fit | Trade-offs to check |
|---|---|---|---|---|
| Self-managed VPS | You patch the operating system, harden SSH, configure the web server and database, monitor logs and arrange backups. | Usually command-line based; transfers use SSH, SCP or provider tools. | Teams comfortable operating Linux and troubleshooting the full stack. | Maximum control, but more work and a larger failure surface if updates, permissions or recovery are neglected. |
| Managed VPS | The host handles an agreed portion of patching, monitoring, security and support; confirm the exact service boundary. | May include migration assistance and a panel, depending on the plan. | Owners who need VPS resources without running every system service themselves. | Less low-level control and an ongoing management charge; verify backup retention, restore testing and response times. |
| cPanel/WHM-based VPS | You still own the server, while the panel manages accounts, domains, mail and many transfer tasks. | cPanel/WHM can streamline account transfers, DNS and SSL, but applications may still need manual checks. | Sites already organized as hosting accounts or administrators who want familiar account workflows. | Licensing, panel version compatibility and panel-specific permission or configuration behavior. |
Build a migration inventory
Export or write down the current account’s configuration before changing anything. Operational migration guidance consistently treats dependencies as important as the site files.
Domains and web roots
- List every primary domain, parked domain, addon domain, subdomain and staging hostname.
- Record each document root, rewrite rule, redirect, canonical URL and whether the site forces HTTPS.
- Note the web server and runtime versions, enabled extensions, upload limits, PHP handlers or other application workers.
Databases and application secrets
- Record database engine and version, database names, users, hosts, ports, character sets and connection limits.
- Store credentials securely; do not paste them into tickets or public notes.
- Identify environment files and configuration files that contain salts, API keys, payment settings or absolute paths.
Scheduled and external work
- Copy every cron entry, its schedule, command, working directory, runtime path and log destination.
- List webhooks, external API allowlists, payment callbacks, monitoring probes and integrations that restrict source IP addresses.
- Record queue workers, search indexers, image processors and other tasks that may not run from a browser request.
Mail, certificates and DNS
- Inventory mailboxes, aliases, forwarders, autoresponders, SMTP credentials and spam or delivery settings.
- Record the SSL certificate issuer and renewal method, including HTTP or DNS validation dependencies.
- Export the complete DNS zone: A and AAAA records, CNAMEs, MX, TXT (including SPF, DKIM and verification records), SRV and any delegated nameservers.
Plan DNS and the overlap window
DNS changes are cached according to each record’s time to live (TTL). If you control the authoritative zone, lower the relevant A and AAAA record TTL before the move, while the old server is still serving the site. cPanel identifies 3600 seconds as a standard TTL timeout in its 2026 migration guidance and advises restoring the normal TTL after the migration. A lower value can shorten the period in which resolvers retain the old address, but it cannot force every resolver or browser to forget an existing cache immediately.
Choose a maintenance window that avoids your busiest write activity. Keep the shared host active for at least the time needed for DNS propagation and for you to observe normal traffic, mail and scheduled jobs. If your DNS is managed elsewhere, make the TTL change at that provider; changing a record on the wrong zone has no effect.
Create and verify backups on the source host
Make backups before provisioning changes or editing DNS. A backup is useful only if it can be read and restored.
Rank #2
- Model: Dell OptiPlex 7050 Small Form Factor (SFF)
- Processor: Intel Core i7-7700 3.60 GHz
- Memory: 32GB DDR4 Ram
- Storage: 1TB Solid State Drive (SSD) Fast Boot + Storage
- Operating System: Windows 11 Pro (64-bit)
Files
- Use the hosting panel’s full-account backup when available; it preserves more than the public document root.
- Also create a separate archive of each site’s files, including hidden files such as
.htaccessand environment files. For WordPress, includewp-contentand its uploads, themes and plugins. - Download the archive to storage that is independent of the shared host. Record its size, checksum if available and creation time.
Databases
- Export each database with the provider’s backup tool or a command-line dump such as
mysqldump, using the correct character set and transaction options for your engine. - Save the dump outside the source account and verify that it contains expected tables and a recent record. Compressing a dump does not prove it is restorable.
- Take a final incremental or fresh dump immediately before cutover if the site continues to receive writes during the initial copy.
Prove the recovery path
On a disposable database or the new VPS, test that the archive extracts, the dump imports, credentials work and the application can read its data. Keep the original backup untouched so a failed test cannot destroy your only copy.
Provision and harden the VPS
- Create the VPS with an operating system supported by your application and a region that meets your latency, data-residency and compliance needs.
- Apply operating-system updates before exposing the site. Create a non-root administrative account, use SSH keys where possible, disable unsafe password or root login according to your operating system’s guidance, and restrict SSH to trusted networks when practical.
- Configure a host firewall. Allow only required services, normally SSH, HTTP and HTTPS; open database ports only for explicitly required private connections.
- Set the server time zone and time synchronization. Incorrect time breaks certificates, cron schedules and signed API requests.
- Set up off-server backups, retention and alerting before the site becomes the only copy on the VPS.
Managed services may perform some of these tasks, but confirm what is included rather than assuming that “managed” covers application updates, mail or restore testing.
Free tools Windows power users keep installed
One-click scans. No signup required.
Install a compatible web stack
Match the source environment first. A newer runtime can expose deprecated functions or extension differences; an older database can fail to import newer syntax or character sets. Install the web server, PHP or another required runtime, runtime extensions, database engine and process manager your application expects. Then set limits such as upload size, memory, execution time and worker counts to values that accommodate the existing site.
Create a separate virtual host or server block for every domain. Set each document root, index order, rewrite handling, log path and HTTPS redirect deliberately. Do not copy a shared host’s global configuration blindly: provider defaults may include modules or security rules that are absent on a VPS.
Rank #3
- Dell PowerEdge R730xd 24B SFF 2U Server
- 2x Intel Xeon E5-2690 v4 2.6Ghz 14-Core (28-cores Total)
- 128GB DDR4 RAM – 4x 1.2TB 10K SAS 2.5” 12Gb/s
- Dell H730P mini 2GB 12Gb/s RAID
- 2x 750W PSU - 2x 10Gb SFP+ 2x 1Gb (RJ45) NIC
Copy files and restore the database
- Transfer archives over SSH/SCP, SFTP or the provider’s transfer utility. Keep the original archive until post-cutover checks are complete.
- Extract each site into its intended document root, preserving ownership, groups, symbolic links and hidden files.
- Create a database and least-privilege database user. Import the dump, then update the application’s connection settings with the new database name, user, password, host and port.
- Set ownership so the web-service account can read application files and write only to directories that genuinely need it, such as uploads, cache or generated media.
- Reapply rewrite rules and test that the VPS web server permits the directives used by the application. cPanel identifies incorrect permissions and broken
.htaccessrules as common post-migration issues. - Replace hard-coded absolute paths or old hostnames in configuration only where the new layout requires it. Search carefully; an indiscriminate database replacement can corrupt serialized data or unrelated text.
For WordPress, copy wp-content and the database, verify the site’s configured URL and home URL, and ensure the PHP extensions required by its active theme and plugins are installed. A temporary provider URL is not a reliable test for a domain-dependent CMS because redirects, cookies, canonical URLs and mixed-content rules may behave differently.
Recreate services that do not live in the web directory
SSL and HTTPS
Install the certificate for every hostname and configure automated renewal on the VPS. Test both HTTP-to-HTTPS redirects and direct HTTPS access, including intermediate certificates. If renewal uses DNS validation, make sure the DNS API credentials or manual process still exists after the move.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchCron and workers
Recreate cron entries with absolute paths to the intended runtime and working directory. Run each job manually once, inspect its output, and confirm that overlapping executions cannot duplicate mail, orders or other actions. Rebuild queue workers and restart policies if the application uses them.
Decide whether mail remains with the existing provider or moves to the VPS. Recreate MX, SPF, DKIM and DMARC records consistently with that decision, then test inbound delivery, outbound delivery, forwarding and autoresponders. Copying website files does not copy mailboxes.
Rank #4
- MODEL P74439-005: Compact and affordable HPE ProLiant MicroServer Gen11 powered by Intel Pentium Gold G7400 3.7GHz processor, ideal for file sharing, NAS, and basic business workloads
- READY OUT OF THE BOX: Includes 16GB DDR5 UDIMM memory (expandable to 128GB), one 1TB SATA 6G Business Critical HDD, embedded Intel VROC SATA, dedicated iLO-M.2 port kit, 180w external power adapter and 1/1/1 warranty for dependable plug-and-play server operation
- WHISPER-QUIET & SPACE-SAVING: Ultra-compact mini tower design fits easily in small office spaces; supports wall, flat, or vertical placement for deployment flexibility
- INTEGRATED REMOTE MANAGEMENT: Comes with HPE iLO 6 and embedded TPM 2.0 for secure, license-free remote server administration through shared port access
- EXPANDABLE DESIGN: Two PCIe slots (including PCIe 5.0) and four LFF-NHP drive bays provide robust options for storage and component scalability. Features new MR408i-p controller support for enhanced storage performance
Firewall and allowlists
Replace the old shared-host IP in payment gateways, APIs, database access rules, monitoring systems and partner allowlists. Remove broad temporary firewall exceptions after testing.
Test the new site privately before DNS
cPanel’s migration guidance says to verify each website before changing DNS. Use a local hosts-file entry that maps the real domain to the VPS IP, or use another private test mechanism that preserves the production hostname in the request. This lets the application generate realistic links without sending public traffic to an unfinished server.
Functional checklist
- Open the homepage, representative deep links, category or search pages and custom 404 pages.
- Sign in and out, exercise administrator functions and confirm session cookies use the intended domain and HTTPS flags.
- Submit forms, upload files, create or edit content and verify that the resulting records appear in the database.
- Test checkout, subscriptions, webhooks, API calls and any integration that depends on an allowlisted IP.
- Run cron and queue tasks manually, then confirm their scheduled execution and logs.
- Check redirects, canonical URLs, robots directives, sitemap output and absence of mixed-content warnings.
- Send test mail in both directions and verify that the application can deliver notifications.
- Review web-server, runtime and database logs for permission errors, missing modules, connection failures and 5xx responses.
Compare important pages and recent records with the source host. Do not mark the migration successful merely because the front page loads.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Cut over DNS safely
- Freeze or announce a short write window if the application cannot reconcile changes made on both servers. For a busy database, take the final dump after stopping writes or put the application into maintenance mode.
- Perform the final file sync and database import, then repeat the critical private tests.
- Change the authoritative A and AAAA records, or change nameservers only when the entire zone has been recreated and verified. Leave unrelated records intact.
- Keep the old host online. Query the domain from multiple networks and resolvers, and check that both IPv4 and IPv6 reach the intended VPS.
- Restore the normal DNS TTL after the migration is stable, following the zone provider’s procedure.
DigitalOcean’s migration guidance recommends leaving the old provider running during propagation. Its WordPress guide, published in 2013, says some scenarios can finish within hours; that is an old, scenario-specific observation, not a current guarantee. File size, database volume, mail, DNS caching and testing determine your actual duration.
Best Value
- 【AMD Ryzen 4300U True 4-Core CPU: Outperforms N95 & i3-10110U】KAMRUI P2 Mini PC is equipped with true 4-core AMD Ryzen 4300U processor built on advanced 7nm Zen2 architecture，This means you get consistent, unthrottled performance for hours on end, whether you’re running multiple browser tabs, streaming 4K content, or managing virtual machines. Compare that to Intel N95 (4 efficiency cores that throttle under load) or Intel i3-10110U (only 2 cores total), and the difference is night and day: The KAMRUI P2 AMD Ryzen 4300U (28W) is 40% faster than the Intel i3-10110U and 25% faster than the Intel N95 in multi-core tasks, ensuring smooth, lag-free performance even during heavy workloads.
- 【Integrated AMD Radeon Graphics: 2.5X Stronger for Tri 4K】The KAMRUI P2 AMD 4300U Mini PC have unlocked the full potential of the built-in AMD Radeon Vega 5 graphics with 28W power delivery, making it 2.5 times stronger than the Intel UHD graphics found in the N95 and i3-10110U. This means you can enjoy Tri 4K@60Hz displays without a single stutter, perfect for productivity setups, home theaters, or even light photo/video editing and casual gaming. While the Intel N95/i3-10110U struggle to run a single 4K display without lag, The KAMRUI AMD 4300U Mini PC handles Tri 4K effortlessly, turning your workspace into a high-efficiency hub or your living room into a premium entertainment center.
- 【Large Storage Capacity, Easy Expansion】KAMRUI Pinova P2 mini computers is equipped with 16GB LPDDR4 for faster multitasking and smooth application switching. 512GB M.2 SSD ensures fast startup, fast file transfers and plenty of storage space,eliminating slow loading times and ensuring fast responsiveness. the two storage slots (1x M.2 2280 SATA/NVMe PCIe3.0 slot, 1x M.2 2280 SATA slot) can be combined to provide up to 4TB of total storage(Not included). This gives you enough space for all your projects, media and data.
- 【4K Triple Display】KAMRUI Pinova P2 4300U mini desktop computers is equipped with HDMI2.0 ×1 +DP1.4 ×1+USB3.2 Gen2 Type-C ×1 interfaces for faster transmission, Triple 4K@60Hz Display, KAMRUI P2 mini computer is ideal for visual home entertainment, home office, conference rooms, etc. USB3.2 Gen2 Type-A port ×2 with a transfer speed of up to 10 Gbps (21 times faster than USB 2.0) for efficient data transfer. Ideal for seamless multitasking between spreadsheets, browsers and presentations, or for an immersive entertainment experience.
- 【USB3.2 Gen2 Type-C 10Gbps, Versatile connectivity】KAMRUI P2 mini desktop pc fast and versatile connectivity! The USB3.2 Gen2 Type-C port offers a data transfer rate of 10Gbps and simultaneously supports DisplayPort 1.4 video output. The P2 AMD Ryzen 4300U Mini PC is complemented by Gigabit LAN, WiFi and Bluetooth, so nothing stands in the way of a productive working environment.
Monitor the overlap and define rollback
For the first hours and days, watch access and error logs, CPU, memory, disk space, database connections, SSL renewal status, queue depth, form submissions and email delivery. Check transactions that matter to your business rather than relying only on uptime probes.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesBefore cutover, write down rollback triggers: sustained 5xx errors, failed payments, missing writes, broken mail or an unrecoverable security issue. If a trigger occurs, point DNS back to the shared host, restore the TTL you documented, stop writes to the VPS if they could diverge, and investigate using logs and the untouched backups. A rollback is harder if both servers accept new data, so decide how you will reconcile any records created during the overlap.
When the observation period confirms stable traffic, take a final backup from the VPS, archive migration notes and only then cancel the shared account. Retain backups and DNS records according to your normal recovery policy.
Troubleshooting common migration failures
| Symptom | Likely cause | Action |
|---|---|---|
| Homepage works but internal links return 404 | Rewrite module, server-block rule or .htaccess handling differs. |
Enable the required rewrite support, verify the document root and inspect web-server error logs. |
| Blank page or 500 error | Missing runtime extension, incompatible version, syntax error or permission problem. | Read runtime and web-server logs, compare versions with the source, install the required extension and correct ownership. |
| Uploads fail or disappear | Wrong writable directory, restrictive PHP/runtime limits or missing storage mount. | Check the upload path, permissions, size and timeout settings, then upload a test file and verify it persists. |
| Users are logged out or carts empty | Changed cookie domain, HTTPS setting, session storage or application URL. | Use the production hostname in private tests, inspect cookie flags and restore the expected session backend. |
| Scheduled tasks never run | Cron was not copied, uses a different runtime path or lacks environment variables. | Run the command as the service account, use absolute paths and capture output to a log. |
| Mail is missing or rejected | MX, SPF, DKIM, DMARC, mailbox data or outbound credentials were not recreated. | Confirm where mail is hosted, restore the matching DNS records and test inbound and outbound delivery. |
| API or payment callbacks fail | The integration still allowlists the shared-host IP or the VPS firewall blocks the connection. | Update the allowlist to the VPS address and permit only the required ports. |
| Some visitors see the old site | DNS caches are still within their TTL or an A/AAAA record was missed. | Query authoritative and public resolvers, check both address families and keep the old host online until caches expire. |
A practical WordPress migration sequence
WordPress combines files, a database and domain-aware configuration, so use a two-pass copy when the site receives frequent edits:
- Copy the initial files and database to the VPS while the shared site remains live.
- Configure the VPS, PHP extensions, virtual host, SSL and permissions, then test privately with the real domain mapped locally.
- Schedule a short maintenance window, disable writes or enable maintenance mode, copy changed files, export a final database dump and import it.
- Confirm the WordPress home and site URLs, login, media upload, permalinks, forms, scheduled actions and outgoing mail.
- Change DNS, monitor both servers and keep the shared account until the overlap checks pass.
This sequence reduces downtime but does not eliminate the need to reconcile data if users can write to the old site during the final copy.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Migration completion checklist
- Every domain, subdomain, document root and DNS record is accounted for.
- Files, hidden files and databases have verified, off-server backups.
- The VPS is patched, access-controlled, firewalled and backed up.
- Runtime, database and extensions match application requirements.
- Virtual hosts, permissions, rewrites, SSL and renewal are working.
- Cron, workers, mail, API allowlists and monitoring are recreated.
- Private tests cover navigation, authentication, writes, uploads, redirects, HTTPS, transactions and logs.
- DNS changes include required A/AAAA records, and the old host remains available during propagation.
- Post-cutover monitoring is clean before the shared account is retired.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
