Pakistan
USA
Canada
UK
Dubai
Australia
Germany
- Never cut over before the new copy is fully tested on its own address.
- Lower the DNS TTL a day or two ahead so the switch propagates quickly.
- Keep the old host live until DNS has settled everywhere.
- Shops and membership sites need a content freeze or a final delta sync.
Why migrations cause downtime in the first place
Most downtime comes from one avoidable mistake: pointing the domain at a new server before the new server is ready. The copy is half imported, the SSL certificate is missing or a hard-coded address sends visitors back to the old host. Customers see errors, and search engines see them too.
The safe approach separates building from switching. You treat the new host as a staging environment, test everything there on a temporary address, and only when it is proven do you change where the domain points. DNS changes take time to spread, which is why the old server stays up during the switch.
The effort is mostly planning. A small brochure site can move in a couple of hours. A WooCommerce shop with live orders needs more care because the database changes while you migrate. Our WordPress migration services follow the same sequence on any size of site.
The migration sequence we use
Follow the order. Skipping the early steps is what causes the late-night emergencies.
- Audit and back upRecord the PHP version, active plugins, theme, cron jobs, email setup and DNS records. Take a full backup of files and database and store it off the server.
- Lower the DNS TTLA day or two before the move, reduce the TTL on the domain's A and CNAME records so changes spread in minutes, not hours.
- Build the copy on the new hostCreate the site, copy files, import the database and update the configuration file. Run a search-replace on the database if the address changes, using WP-CLI or a tool that handles serialised data.
- Test with a hosts file overrideEdit your computer's hosts file to point the real domain at the new server. You see the new site under the real address while everyone else still sees the old one.
- Freeze content and take a final syncPause editing, comments and orders. Export the latest database and re-import, or sync only the changes.
- Switch DNSUpdate the records to the new server. Keep the old host running so visitors still resolve to a working site during propagation.
- Verify and monitorCheck forms, checkout, redirects, SSL, sitemaps and search console. Watch logs for errors for several days.
Migration methods compared
Choose the method that fits the size and sensitivity of the site.
Method | Best for | Risk | Notes |
|---|---|---|---|
Migration plugin | Small to mid-size sites | Timeouts on big databases | Fast; check serialised data and large files |
Manual files and database | Developers, larger sites | Human error | Most control; scriptable with WP-CLI |
Host-provided migration | Moving into a managed host | Hidden differences in setup | Often free; still test before DNS |
Staged sync with final delta | Shops and active sites | Needs planning | Best for near-zero downtime |
Handling shops, forms and email without losing data
A brochure site can pause without damage. A shop cannot. If you take orders while you migrate, those orders land in the old database after you copied it. The fix is a short content freeze, or a plan to import the new orders afterwards. For WooCommerce, we usually schedule the switch in a quiet window, put the store in maintenance mode only for the final sync, and then reopen it on the new host. That keeps the pause to minutes instead of hours.
Email is the quiet casualty. If your mail runs through the old hosting account, changing the DNS can break it. Check the MX records before you start and keep them unchanged if your email lives elsewhere, such as Google Workspace or Microsoft 365. If email is hosted on the old server, move it first or plan the mailboxes carefully.
Forms, payment webhooks and scheduled tasks all depend on the server. Test each on the new host before the switch, including a real test transaction, and rebuild any cron jobs that the old host ran for you. For stores, our guide to WooCommerce development covers the extra checks.
Post-migration checks
Run through this list before you consider the job finished.
- SSL certificateConfirm HTTPS works on every page and that no mixed content warnings remain.
- Permalinks and redirectsOpen old URLs, key landing pages and any redirects. Resave permalinks if pages return errors.
- Forms and email deliverySubmit every contact and checkout form, and confirm messages arrive.
- Search engine settingsVerify the site is not set to discourage indexing, and that robots.txt and sitemaps are correct.
- Analytics and trackingCheck GA4, Tag Manager, pixels and Search Console properties still receive data.
- PerformanceCompare page speed against the old host. Caching and PHP settings often need tuning; see how to speed up WordPress.
- SecurityReset passwords, confirm file permissions, and review the checklist in WordPress security for business sites.
Mistakes that cause downtime or lost rankings
The classic error is changing the domain, theme and structure at once. If you move host, switch to HTTPS and redesign in one weekend, you cannot tell which change broke what. Separate them. Another frequent mistake is forgetting the redirect map when URLs change, which can drop organic traffic. Keep the same URLs wherever you can.
Teams also forget to disable the staging copy's indexing, so a test site ends up in search results, or they leave the old site's caching plugin active with the wrong paths. And some migrate the database without a proper search-replace, leaving hard-coded old addresses in widgets and builder data. Elementor in particular stores addresses in its own data, so use its replace tool after the move.
If the move is part of a wider speed or hosting change, consider whether to fold in speed optimization afterwards, not during, so you can attribute improvements correctly.
Rollback planning: your insurance policy
Plan for the migration to fail, then be pleasantly surprised when it does not. A rollback plan is simple: the old site stays untouched, DNS can be pointed back, and you have written down the original records. If the new host shows a problem you cannot fix within a short window, you switch back and investigate calmly.
Rollback is hardest on sites that accept data. If orders or form entries arrived on the new server before you rolled back, you need to export them and re-enter them on the old one, or you lose them. That is why the first hours after cutover deserve close watching, with someone assigned to check the order list, form submissions and error logs.
Document everything in a short runbook: who does what, when DNS changes, who checks which pages, who calls whom. Even for a small site, a one-page plan prevents the panic that comes from improvising. Our maintenance plans include this kind of checklist so the next move is easier.
Pakistan notes: hosts, bandwidth and timing
For businesses in Pakistan, hosting choice affects both speed and reliability. Moving from a local shared host to a managed international host, or the reverse, changes latency to your audience. Choose the data centre near the majority of your visitors, and keep a copy of every backup outside the server you are leaving.
Large uploads over local internet connections can fail, which is a reason we run transfers server to server rather than downloading and re-uploading from a home connection. Timing matters too. Avoid switching before a sale, Eid trading period or a major campaign, and avoid load-sensitive hours when your own audience is most active.
We run migrations from Lahore for clients across Pakistan, the UAE, UK and USA, scheduling cutovers at hours that suit your customers rather than ours.
Junaid's take
I treat a migration as a rehearsal followed by a short performance. The rehearsal is the full copy and test on the new host. If that goes well, the real switch is almost boring, and boring is what you want.
My firm advice is to keep the old hosting account paid for at least a couple of weeks after the move. It is cheap insurance. If something odd appears, you can compare behaviour or roll back in minutes.
If your site earns money or handles leads, do not experiment with a plugin and hope. Have someone check the staging copy and run the cutover with you. You can contact our team to schedule a migration, and it helps to read about what drives WordPress cost first, so you know what to ask for.
Junaid has worked on WordPress for more than 18 years, across SEO, paid media, web development and custom software. He founded SEOnumber1, builds WordPress plugins, CRMs and web applications, has served 500+ clients in 48 countries, and holds Google Ads, Analytics and Google Blue and Green Belt certifications. He is a National Level Award Winner in Digital Marketing. Read his story or ask a question about this article.