DMCA notices: no action · Netherlands · Romania · Moldova · Pay in BTC, USDT, USDC, ETH, SOL, LTC, XMR
Language: English
Configure a VPS

Guide · migration without downtime

How to move a website to an offshore VPS?

Move files, database and DNS from a current host to an offshore KVM server, with a final sync so no comment or order is lost.

Last updated: · 5 min read

Quick answer

How to move a website to an offshore VPS?

To move a website to an offshore VPS, lower the DNS TTL a day ahead, set up the same web stack on the new server, copy the files with rsync, dump and import the database, test, run a final sync, then switch the A record. An IronKVM VPS is ready within 1 hour, so 8 steps fit in one evening.

In brief
  • RFC 1035 defines the TTL as how long a DNS record may be cached; lower it before the move.
  • rsync copies only what changed, so a second run right before the switch is short.
  • mariadb-dump --single-transaction dumps InnoDB tables without blocking the site.
  • Issue the HTTPS certificate on the new server after the DNS switch.
  • Keep the old host running until the new one has served traffic for a few days.

What moves, and with which tool?

Parts of a website migration and the tool used for each, from the rsync and MariaDB manuals and RFC 1035
PartToolCommand
Filesrsync over SSHrsync -az --delete old:/var/www/site/ /var/www/site/
Databasemariadb-dumpmariadb-dump --single-transaction db > db.sql
Database importmariadb clientmariadb db < db.sql
DNSYour DNS providerLower TTL, then change the A and AAAA records
HTTPScertbotcertbot --nginx -d example.org

What are the steps to move a website to an offshore VPS?

  1. Lower the DNS TTL

    A day before, set the TTL of the A and AAAA records to 300 seconds so the switch spreads quickly.

  2. Order and prepare the VPS

    Pick the plan and country, then install the same stack as the old host: nginx, PHP, MariaDB.

  3. Copy the files

    Pull the web root from the old server with rsync over SSH. A trailing slash copies the contents, not the folder.

  4. Copy the database

    Dump it on the old server with mariadb-dump --single-transaction and import it on the new one.

  5. Test before the switch

    Add the new IP for your domain to the hosts file of your own computer and browse the site.

  6. Run the final sync

    Pause writes on the old site, run rsync and the database dump again, and import.

  7. Switch DNS

    Change the A and AAAA records to the new VPS. Visitors arrive as caches expire.

  8. Add HTTPS and close the old host

    Run certbot on the new server, watch the logs a few days, then cancel the old plan.

On the new VPS: copy files and database
# files: dry run first, then the real copy
rsync -az --dry-run -e ssh old@OLD_IP:/var/www/example.org/ /var/www/example.org/
rsync -az --delete -e ssh old@OLD_IP:/var/www/example.org/ /var/www/example.org/
# database: dump on the old server, import here
ssh old@OLD_IP 'mariadb-dump --single-transaction wordpress' > /tmp/wordpress.sql
sudo mariadb wordpress < /tmp/wordpress.sql

Why lower the DNS TTL before you move a website?

Because resolvers keep the old address for as long as the TTL says. RFC 1035 defines the TTL as the time a record may be cached before the source is asked again. With a TTL of one day, some visitors still reach the old host a day after the switch.

Set a short TTL, such as 300 seconds, at least one old TTL period before the move. After the switch, raise it again. Mail records (MX) do not need to change if only the website moves.

How do you avoid losing data during the move?

Run the copy twice: a full copy days ahead, and a short final sync with writes paused. The rsync manual explains that --delete removes files on the receiving side that no longer exist on the sender, and --dry-run shows what would change without changing anything. Use both.

For the database, the MariaDB manual says --single-transaction starts a transaction before the dump, so InnoDB tables are read consistently without blocking the site. For WordPress, put the old site in maintenance mode before the final dump. Keep the first dumps as a fallback; the VPS backup guide turns them into a daily routine.

Why move a website to an offshore VPS at all?

Because the current host’s notice policy may take a lawful site down. According to IronKVM's survey of 16 November 2026, 9 of 30 offshore hosts act on DMCA notices and 6 forward them; 4 say they ignore them. IronKVM takes no action on DMCA takedown notices or on other foreign copyright notices: the VPS stays online and no customer data is handed over because of such a notice. Ignoring DMCA notices does not make illegal content acceptable. What runs on an IronKVM VPS must be legal in the country of its datacenter.

The DMCA ignored VPS page compares the policies. Once the files are across, set up the web server and Let’s Encrypt.

Can you move between IronKVM countries the same way?

Yes, with the same steps: order a new VPS in the other country, copy, switch DNS, then delete the old one. Changing country means ordering a new VPS in the other country: copy the data across, then delete the old VPS from the dashboard. Deleting a VPS ends it with the days left on it, so time the move near the end of its term. Each new server gets its own IP address, so the DNS step is needed every time.

Moving a website to an offshore VPS: questions

Will the site go down during the move?

Not if both servers run during the switch. Old caches reach the old host, new ones the VPS.

What is the best time to move a website?

When traffic is lowest, and after the lowered TTL has had time to spread.

Can I move a WordPress site with a plugin instead?

Yes, migration plugins work. rsync and a database dump do the same job without extra software.

Do I need to change my domain registrar?

No. Only the DNS records change. The domain can stay where it is.

How fast is the new VPS ready?

A member of the team builds each VPS by hand once the payment is confirmed on its network: usually a few minutes, one hour at most. The dashboard shows the status, then the IP address.

Verdict
  • Lower the TTL, copy twice, test with your hosts file, then switch DNS: a website moves without downtime.
  • IronKVM is ready within 1 hour of payment, so the new server can be prepared the same day.
Sources (5)
  1. RFC 1035: Domain names, implementation and specification — IETF (read 2026-11-16)
  2. rsync(1), Debian trixie — Debian (read 2026-11-16)
  3. mariadb-dump — MariaDB Foundation (read 2026-11-16)
  4. Certbot user guide — Electronic Frontier Foundation (read 2026-11-16)
  5. IronKVM offshore VPS survey (CSV) — IronKVM (read 2026-11-16)

Move your website to IronKVM

Ingot, 2 vCPU, 4 GB RAM, 80 GB NVMe, 4 TB traffic, $8.25 a month on 12 months, in 3 countries.

From $4.46/month · no KYC

Configure a VPS