Public testing phase We’re in a public testing phase — feel free to look around, but we’re not taking orders yet. Ordering opens 1 October 2026. Reserve your place →

Move your site — or your database. Free.

Files, database, email and DNS from the host you are on today — or a MySQL, MariaDB or PostgreSQL database on its own. Point the importer at what you have — a backup, a link or SSH access — and it copies, checks and previews. An engineer steps in only when something needs a hand.

Request your free migration

Tell us what you are moving and where it lives today. We'll reply within one business day with a plan and a time.

What are you moving?
Which engine is it?

We don't convert between engines: a PostgreSQL database arrives as PostgreSQL, a MySQL one as MySQL. Not sure which you have? Say so and we'll look.

A rough answer is fine. It decides how the move runs, not whether it can.

Can we reach it where it is?

SSH is the better path: it lets us count the rows in every table on your old host before the export and compare them with what arrives here. From a dump we can only check what arrived against what the dump contained — a weaker check, and we tell you which one you got.

How it works

  1. You point the importer at what you have — a backup, a download link or SFTP access to your current host.
  2. It copies your files, database and mailboxes to veldhost and checks them on a preview address.
  3. You check the preview and switch your domain over when it looks right — typically zero downtime.

An engineer steps in only when something needs a hand — that is what this form is for. Every step shows up in veldhost Manage once you have an account, preview link and all, so you can see where your site has got to without asking.

Rather do it yourself, right now?

Every veldhost site has Move an existing site here: upload a backup (All-in-One WP Migration, Duplicator, UpdraftPlus or a plain zip + .sql), paste a download link, or let it pull straight from your old host over SFTP. It lands on a preview address in minutes; you connect the domain when it looks right.

How the self-serve move works →

How a database move works

  1. You say which engine it runs on, roughly how big it is, and whether the machine it lives on is reachable over SSH.
  2. The importer takes the dump — over SSH from your old host, or from the file you upload — and loads it into a MySQL/MariaDB or PostgreSQL database here.
  3. You get the comparison: every table, the rows counted on your side, the rows that arrived, and every statement the load could not apply.

A PostgreSQL database arrives as PostgreSQL and a MySQL one as MySQL — we don't convert between engines. Anything you give us to reach the old host is encrypted, handed to the job once, and deleted the moment it starts.

We count the rows, table by table

The thing worth worrying about in any database move is the one that quietly loses rows. So we count them. When we can reach your old host, an exact COUNT(*) is taken per table there, before the export, and compared with what landed here — missing tables and short tables both named, on a report you see.

Every statement the load could not apply is collected and counted as well — all of them, not only the first. From a dump you send us we compare against what the dump itself contained, which is a weaker check, and we say so rather than dress it up.

What it costs

Nothing. The migration is free with any hosting plan — you only pay for the plan itself once you're live and happy.

Your old host stays untouched

We copy — never move or delete. If anything's not right, your existing site keeps running exactly as before. We read your database; we never write to it. Nothing there is dropped, renamed or altered, so if the result isn't right you are exactly where you started.