Migrating a WordPress with no downtime: how the migrator works inside
A read-only plugin, a key that signs every request and a destination that isn't touched until everything is in. Why the source site stays online the whole time.
Zygore team · · 4 min read
The classic migration is: download everything over FTP, export the database, upload it, import it, fix URLs, and cross your fingers. Zygore's migrator does the same, but in the order that avoids the scare.
The plugin only reads
You install a plugin of ours on your current WordPress. It writes nothing there: it reads files and database when the panel asks, and only if the request is signed with the key you generated. Without the key, it doesn't answer.
It tests first
Before moving anything, the panel tests the connection and shows you which WordPress it is, which PHP version it uses and how big its database is. If something doesn't add up, you see it there.
The destination isn't touched until the end
Everything downloads first to a separate area of the destination site. Only when it's complete is the site replaced. If the connection drops halfway, your Zygore site stays as it was. And if the destination already had content, a backup is taken first and we ask you to type the domain to confirm.
You switch DNS, when you want
Throughout the process your source site stays on its host, online. When you've checked everything is right on Zygore, you point the domain. Until then, nobody notices anything.
What doesn't migrate
Email. The migrator brings the website: files and database. If your email was on the previous host, that's another conversation (and another product: Micorreo360). And if your site isn't WordPress, message us and we'll see how to bring it.