Free tools Windows power users keep installed
One-click scans. No signup required.
You usually cannot move a running VPS object directly to a different account or hosting company. The reliable approach is to create a point-in-time snapshot when the source supports transferring snapshots, or to provision a new VPS and restore your files, databases, and configuration there. Because the replacement normally receives different IP addresses, plan for DNS, firewall allowlists, monitoring, certificates, and application settings before you cut over.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Keep the original VPS and at least one restorable backup until the new machine has passed production checks. That gives you a defined rollback path if a service, database, scheduled job, or external integration fails after the move.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhat “copy a VPS” actually means
A VPS migration has two separate parts: copying the server’s state and changing the network destination. A snapshot or image captures disks at one moment. It does not continuously mirror later writes, and it does not normally carry the source server’s public or private IP addresses to the replacement.
There are three practical migration patterns:
| Method | Best use | What moves | Main limitations |
|---|---|---|---|
| Provider-native snapshot transfer | Moving within a provider, including a supported account or region transfer | A whole point-in-time disk image, including the operating system, installed packages, users, and configuration captured in the snapshot | Attached volumes, managed services, applications, and IP addresses may be outside the snapshot workflow |
| Snapshot copy to another region | Recreating an instance in a different geographic region under the same provider | A copied snapshot from which you launch a replacement instance | The replacement has new network addresses and may incur snapshot-storage charges |
| Export, restore, and rebuild | Moving between different providers or when no snapshot transfer exists | Application files, databases, uploads, secrets, certificates, and manually recreated system configuration | More planning, validation, and usually a maintenance window; provider-specific resources need separate treatment |
A snapshot is a baseline, not a live replica. Any transaction, upload, log entry, or configuration edit made after the snapshot was taken is absent unless you copy it separately. For write-heavy applications, stop writes or schedule a final backup immediately before the cutover.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Decide which migration path fits your VPS
Use a native snapshot transfer when the provider supports it
This is usually the fastest way to preserve an operating system and server-level configuration. It can retain package versions, service files, user accounts, SSH configuration, and application directories exactly as they existed at snapshot time. You still need to verify resources that are not part of the image and update every setting tied to the old IP.
Use export and restore for a cross-provider move
Different vendors use different image formats, virtual hardware defaults, networking models, and control-plane metadata. A disk image that boots at one provider may not boot cleanly at another. Exporting the data and rebuilding the destination makes those differences explicit: install the destination operating system, restore the application and database, then recreate firewall and service settings.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Use a hybrid approach for large or stateful systems
You can copy static files ahead of time, replicate or dump the database near the maintenance window, and then perform a short final synchronization. This reduces downtime without pretending that a snapshot is current. Keep a final database dump even when you also create a machine snapshot.
Inventory the source before touching it
Make a written inventory and mark which items are included in a snapshot, which require an export, and which must be recreated at the destination. The inventory is your migration checklist and your rollback reference.
- Operating-system release, kernel, architecture, disk layout, swap, and filesystem mounts.
- Web servers, reverse proxies, application runtimes, workers, queues, container engines, and systemd services.
- Databases, replication settings, extensions, users, permissions, scheduled backups, and database connection strings.
- Application code, uploaded media, user-generated files, object-storage credentials, and deployment artifacts.
- Local users, groups, sudo rules, SSH keys, known hosts, deployment keys, and any automation account.
- Host firewall rules, cloud firewall rules, security groups, fail2ban policies, open ports, and outbound restrictions.
- Cron entries, systemd timers, backup jobs, log rotation, monitoring agents, alert destinations, and health checks.
- TLS certificates and renewal mechanisms. Confirm whether certificates are stored on disk, issued by an external service, or recreated during deployment.
- Secrets such as environment files, signing keys, API tokens, encryption keys, and database passwords. Record where each is stored; do not place secret values in a ticket or migration document.
- External systems that allowlist the old IP: payment gateways, databases, mail relays, partner APIs, VPNs, DNS providers, and administrative consoles.
- Volumes, managed databases, Kubernetes clusters, and platform applications attached to the VPS but not represented by its boot disk.
Prepare DNS and a rollback plan
Lower the DNS TTL before the move
If a hostname will point to a new address, lower its DNS time-to-live in advance. The exact propagation time still depends on recursive resolvers and cached records, so do not assume every user will switch immediately. Keep the old service able to answer requests while caches expire.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Define the rollback trigger
Write down the conditions that cause a rollback: failed database checks, missing uploads, elevated error rates, broken authentication, failed payment callbacks, or a certificate problem. Decide who can change DNS, who can stop writes, and how long you will observe the destination before declaring success.
Preserve the source
Do not delete the old VPS as soon as the new one boots. Retain the original instance, the final snapshot or database dump, and any volume backups until the destination has operated normally through at least one complete backup cycle and all critical integrations have been verified.
Copying a VPS with DigitalOcean snapshots
DigitalOcean does not provide a direct “transfer this Droplet” operation. Its support guidance states: “You can’t directly transfer a Droplet to another user, but you can transfer a snapshot of a Droplet.” The workflow is therefore snapshot-based.
Transfer to another account
- In the source team, create a Droplet snapshot after stopping or quiescing write-heavy services. A running snapshot can be usable, but stopping writes gives you a more consistent application state.
- Wait for the snapshot to finish and record its creation time. That timestamp defines the data included in the image.
- If you may need the image in the original team, create a second snapshot first. DigitalOcean moves a transferred snapshot out of the original team; it is not a retained duplicate in both accounts.
- Use the snapshot transfer control to send the image to the destination account or team, then have the recipient accept it according to the provider’s account workflow.
- In the destination account, create a new Droplet from the transferred snapshot. Select an equal-or-larger plan and the required region, storage, and networking options.
- Connect to the new Droplet through its new address. The snapshot includes the SSH keys and user accounts that existed when it was taken, so verify that the expected administrative access works before removing any temporary access.
- Run the service, database, firewall, and application tests described in the validation section below.
- Update DNS and every IP allowlist only after the destination passes those tests. The IP address belongs to the Droplet, not to the snapshot, so the new Droplet does not inherit the old address.
Important DigitalOcean exclusions
Volume snapshots cannot be transferred directly through the Droplet snapshot workflow. Plan a separate volume migration or data copy. Kubernetes clusters and App Platform applications also require separate recreation or redeployment; copying a Droplet snapshot does not recreate their control-plane resources.
Copying an Amazon Lightsail instance
Lightsail snapshots are point-in-time baselines. AWS describes a snapshot as containing the data needed to restore the resource “from the moment when the snapshot was taken.” Snapshot storage is billable, so remove temporary copies only after you have confirmed that the destination is safe to operate without them.
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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Copying between Regions
- Create an instance snapshot and any required block-storage snapshots after quiescing the application or taking a consistent database backup.
- Copy the snapshot to the target Region using the Lightsail snapshot-copy workflow.
- Launch a replacement instance from the copied snapshot in that Region.
- Recreate or attach any storage that was not included in the instance snapshot, then verify mount points and filesystem ownership.
- Test the replacement using its new public address or a temporary hostname.
- Update DNS, monitoring, firewall rules, partner allowlists, and application configuration that references the old private or public address.
A Lightsail instance cannot be directly moved between Regions. The replacement receives different private and public IP addresses, so an apparently identical server can still fail when an integration, database connection, webhook, or monitoring rule is tied to the old address.
Account boundaries
The documented Lightsail process is a snapshot copy and new-instance launch, not a live instance handoff. If you are changing accounts as well as Regions, confirm the current account-transfer options in the Lightsail console and plan on the same replacement-and-repoint model unless the account workflow explicitly supports a direct resource transfer.
Cross-provider migration: rebuild, transfer, restore
When the source and destination vendors differ, assume that you must provision a new VPS and restore into it. DigitalOcean’s migration guidance recommends taking a backup at the old provider, uploading it to the new Droplet, and updating configuration such as database credentials. Vultr describes analogous moves from AWS, Google Cloud, Linode, DigitalOcean, and shared hosting using exported files and databases copied with tools such as scp or rsync, followed by restoration on the destination.
Build the destination
- Create an equal-or-larger VPS with the required CPU, memory, disk capacity, operating-system release, and data-disk layout. Leave enough free space for temporary dumps and logs.
- Apply the destination provider’s firewall and network rules before exposing the application. Open only the ports required for administration, web traffic, APIs, and database access.
- Create the same system users and groups, or create a dedicated deployment user with equivalent permissions. Install the required language runtimes, web server, database engine, queue, and process manager at compatible versions.
- Copy configuration templates and secret references, then inject the actual secrets through the destination’s secure process. Do not casually copy private keys into a public transfer location.
Transfer files with a repeatable command
For a large application directory, run an initial synchronization while the old server remains online, then perform a final synchronization after writes are paused. A typical pattern is:
Recommended Free Tools
rsync -aHAX --numeric-ids --info=progress2 /srv/app/ user@NEW_IP:/srv/app/Review the paths before running it. Preserve ownership and permissions only when the destination user and group IDs are intentionally aligned; otherwise copy the data and correct ownership explicitly. Use encrypted transport, restrict the destination account, and remove temporary transfer keys afterward.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Export and restore databases
Use the database engine’s supported dump and restore tools rather than copying live database files between unlike hosts. Stop writes or put the application in maintenance mode, create the final dump, transfer it, restore it on the destination, and run integrity checks. Update database usernames, passwords, hostnames, socket paths, and connection-pool settings if the destination differs.
Recreate services and scheduled work
Enable services only after their configuration points to the destination’s paths and credentials. Recreate cron jobs and systemd timers, but disable jobs that send email, charge customers, publish content, or delete data until validation is complete. Otherwise a copied scheduler can perform the same action twice when both VPSs are online.
Run the migration safely from start to finish
- Schedule the window. Tell users and integration owners when writes will pause. Identify the last acceptable source transaction and the person responsible for DNS.
- Lower DNS TTL. Change the relevant records before the window and note the previous values for rollback.
- Quiesce the application. Put write-heavy services in maintenance mode, stop workers that consume queues, and prevent new uploads or jobs from starting.
- Create the final consistent copy. Take a provider snapshot when supported, plus final database and file backups when the application needs a stronger consistency guarantee.
- Transfer or restore. Use the native snapshot workflow, or copy files and dumps to the prebuilt destination. Record checksums or row counts for important datasets.
- Reapply configuration. Check ownership, permissions, mount points, firewall rules, service startup order, environment variables, secrets, TLS certificates, and renewal timers.
- Protect against duplicate work. Keep outbound mail, payment jobs, destructive maintenance, and queue consumers disabled until you have decided which VPS is authoritative.
- Test privately. Use the destination IP, a temporary hostname, or a local hosts-file override. Test login, reads and writes, uploads, background jobs, API callbacks, and administrative functions.
- Inspect evidence, not just the home page. Read web-server, application, database, authentication, and system logs. Confirm that health checks represent real dependencies rather than returning success from a static endpoint.
- Switch traffic. Update DNS, load-balancer targets, webhook endpoints, firewall allowlists, monitoring targets, and any licensed service that binds to an IP or hostname.
- Observe and compare. Watch error rates, latency, CPU, memory, disk growth, queue depth, mail delivery, database connections, and certificate status. Compare with the source’s normal behavior rather than relying on one successful request.
- Close the window deliberately. Re-enable scheduled jobs and outbound actions on the destination, confirm that the source is no longer receiving writes, and keep the source available for rollback.
Validate the replacement before declaring success
Storage and data checks
- Compare expected directory sizes, file counts, ownership, permissions, and checksums for critical assets.
- Connect to every production database and verify schema version, migrations, extensions, indexes, users, and representative records.
- Restore a sample backup or run the application’s built-in consistency check if one exists.
- Confirm that attached volumes are mounted after reboot and that the application writes to the intended disk.
Application and network checks
- Test authentication, session persistence, password resets, uploads, downloads, search, payments, webhooks, API clients, and administrator actions.
- Verify TLS certificates, the complete certificate chain, automatic renewal, canonical redirects, and any hard-coded hostname.
- Check DNS resolution from more than one network and confirm that the new address is shown where expected.
- Test IPv4 and IPv6 separately if both are advertised. Confirm that firewall rules allow required outbound connections as well as inbound traffic.
Operations checks
- Reboot the destination and verify that all required services start in the correct order.
- Run a backup and confirm that it completes, is stored off the VPS, and can be restored.
- Trigger a monitoring alert or use a synthetic check to prove that the new target is monitored.
- Review logs for authentication failures, missing environment variables, permission errors, timeouts, and attempts to reach the old IP.
Common failure modes and fixes
The snapshot boots but the application does not
Check service status, boot-time mounts, environment files, filesystem ownership, runtime versions, and firewall rules. A snapshot can preserve a broken service configuration just as faithfully as a working one. Compare startup logs with the source and correct one dependency at a time.
Users reach different servers
This usually means DNS caches still contain the old record or a secondary record was missed. Query the authoritative DNS service, inspect every A, AAAA, CNAME, and load-balancer record, and keep the source online until the expected cache period has passed.
The database is missing recent records
Writes made after the snapshot or initial dump are not included. Stop writes, take a final consistent dump or incremental synchronization, restore it, and compare transaction or row counts before switching traffic.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
External services reject the new VPS
Replace the old address in allowlists, security groups, VPN policies, webhook validation, mail-provider settings, monitoring, and partner integrations. If a vendor cannot update immediately, keep the old VPS available as a controlled relay only when the application architecture supports that safely.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
SSH access is unexpectedly unavailable
Confirm that the snapshot contained the expected user and key, that the destination firewall permits SSH from your administration network, and that the SSH daemon configuration is valid. Use the provider console or recovery mode rather than disabling security controls broadly.
Jobs run twice
Both VPSs may still have cron entries, timers, queue workers, or deployment hooks enabled. Stop the source’s schedulers before cutover, disable destructive jobs on the destination during testing, and re-enable only the authoritative copy.
When to roll back
Rollback is a traffic decision, not an attempt to merge two diverging servers. Stop writes on the destination, preserve its logs and database state for diagnosis, restore the DNS and allowlists to the source, and confirm that the source is accepting requests. If users wrote data to the destination, reconcile those records before reopening normal writes on the source; otherwise you can overwrite valid changes.
Keep a timestamped record of the cutover, DNS changes, database dumps, snapshots, and configuration edits. That record lets you identify exactly which state is authoritative if a delayed DNS cache or background integration produces unexpected traffic.
What happens to domains and IP addresses?
Your domain name does not need to change. Change the DNS records for the hostname to the replacement’s address, or update the load balancer that fronts both systems. The VPS itself normally receives new private and public IP addresses after a snapshot launch, regional copy, or cross-provider rebuild. Any configuration that embeds an IP must therefore be reviewed even when the hostname stays identical.
Certificates are generally tied to names, not to a particular VPS, but the destination still needs the certificate files or a working issuance and renewal process. Test renewal before deleting the old machine, especially when HTTP or DNS challenges depend on a specific endpoint.
Quick Recap
Final decision checklist
- Same provider and supported transfer: use a snapshot transfer, create a duplicate snapshot if the source must retain one, and migrate excluded volumes or managed resources separately.
- Different region: copy the snapshot where supported, launch a replacement, and plan for new private and public addresses.
- Different provider: rebuild the destination, transfer files and databases with encrypted tools, recreate configuration, and validate every dependency.
- Stateful or write-heavy service: schedule downtime or use replication plus a final consistent backup; do not rely on an old snapshot alone.
- Production cutover: lower TTL early, test through the new address, update DNS and allowlists, monitor, and retain the source for rollback.
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.
