Knowledge base
Package a WordPress site your old host will not let us reach, and hand us one link to pull it across.
You almost certainly do not need this plugin, and it says so on its own screen.
If your old host gives you FTP, SSH, cPanel, Plesk or DirectAdmin, put those details into the migration form on Zinn® instead. We fetch the site directly, we install nothing on your old server, and there is nothing left behind afterwards. That is faster and safer than packaging the site up, and it is what almost every migration uses.
Some hosts hand you a WordPress login and nothing else — no FTP account, no shell, a control panel with its API switched off, or every port firewalled. If our checker says it could not reach your host on any of the usual ways in, this is the way through.
archive, a few hundred files at a time so it works on hosts that cut long requests off.
the source.
Anyone who has it can download your whole site, database included. It is a long random address so it cannot be guessed, and the folder cannot be listed — but if you paste it somewhere public, that is the same as publishing your site's database.
The plugin deletes the package automatically 24 hours after it was built, and there is a Delete the package now button. Use it as soon as your migration has finished, then remove the plugin.
Building a package needs roughly as much free disk as your site takes up, on the old server. The screen works this out for you before you start and tells you if it cannot — a server that runs out of space part way through takes the site down, which is why it asks first.
It cannot restore, and it cannot package a site that is already broken. It is PHP running inside the site it is copying, so the site has to be able to load. A site that is down needs SSH or our managed migration service.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →