Move a site without downtime

A site migration without downtime means you copy files and databases to the new server, preview everything there, and only then change DNS. You keep the old host online until public resolvers catch up, so visitors never hit a half-moved site.

When we pull the account and when you export

If the old server is cPanel and remote access works, open a ticket with the URL, username, and password. We can pull the full account for you. You preview on our side, then you switch nameservers to ns1.logicweb.com and ns2.logicweb.com when you are ready.

If the old host blocks remote access, send a cpmove file or a files-plus-SQL dump and tell us which one you are providing. Non-cPanel setups such as Plesk or plain FTP still move as a copy. They are simply not the free cPanel pull, so the handoff takes a bit more care on your side.

A simple brochure site can often cut over on a quiet afternoon. A store with live checkout needs a short window for the final database dump so orders stay consistent. Apps that write constantly cannot honestly claim zero downtime; plan a brief freeze so the data matches on both ends.

The order that actually avoids downtime

1. Lower your DNS TTLs about a day before you plan to switch.
2. Copy the files and the database. Update wp-config or similar so the app uses the new database user.
3. Preview with a hosts file entry. Test a real login or checkout, not only the homepage.
4. Let AutoSSL issue certificates once DNS can see the name on our side, then change nameservers or A records.
5. Keep the old host billed and online until public resolvers agree on the new address.

rsync -a –dry-run /source/ /dest/

Run a dry-run first so you can see whether paths would nest as public_html/public_html or skip wp-content/uploads. When the listing looks right, run the same command without dry-run. If mail moves with the site, update SPF so it lists the new outbound IPs. Do not remove the old config until the new site has handled a real login or checkout.

Preview before the world sees it

A hosts file entry is how you prove the copy works before DNS changes. Use it to click through the important paths on the new server. Only after that test should you change nameservers or A records. Same price at renewal applies on the new plan, and you still have the usual 30-day money-back window on hosting and VPS if the move does not fit.

Most “downtime” after a careful site migration is really slow DNS or waiting on TLS, not missing files. Leave the old host up until resolvers settle, and you give yourself a clean rollback if anything still needs a tweak.