Move your website to a new host without losing a day of orders.
We move websites, databases, media, email routing and domain settings to new hosting in staged steps, test everything before the switch and keep a way back. The work covers WordPress, WooCommerce, Next.js and custom sites, delivered from Lahore for clients anywhere.
How do you move a website to a new host without downtime?
Build and test a full copy on the new server first, while the old site keeps running. Lower the DNS record lifetime in advance, freeze content changes briefly, copy the final database and files, then switch the records and watch both servers. Keep the old host live until the new one is proven. Check email records separately, because mail is the usual casualty. A rollback plan means a problem becomes a quick revert and not a crisis.
Six stages from first list to a calm switch.
A migration is a sequence of small, checked steps. The quiet ones before the switch decide how calm the day itself will be, and each stage ends with something you can review.
- 01
Inventory
Pages, plugins, cron jobs, email accounts, forms, redirects, certificates and anything else that lives on the old host are listed.
- 02
Target setup
The new server gets the right PHP or Node version, limits, caching and security settings before any files arrive.
- 03
Copy and stage
Files and database are copied to a private test address, and links and paths are corrected.
- 04
Test
We walk through pages, forms, logins, payments and admin tasks, comparing the copy with the live site.
- 05
Cutover
Content is frozen, a final copy is made and DNS is switched in the agreed window.
- 06
Watch and retire
Logs, errors, orders and email are checked for days. The old host is cancelled only after the new one has proved itself.
The pieces of a website we carry across.
Each piece has its own way of failing, so each one gets its own check.
Files and code
Themes, plugins, uploads and custom code, copied with permissions intact and paths corrected for the new server.
Database
Posts, products, users and orders exported cleanly, with addresses inside the data updated where the domain or folder changes.
Media library
Images, documents and video, often the biggest part of a site, moved in batches and checked for missing files.
Email routing
MX, SPF, DKIM and DMARC records left exactly as they work today, or deliberately updated if mail is also moving.
Certificates and security
SSL issued ahead of time, firewalls and access rules recreated, and old admin accounts reviewed before they reach the new host.
Redirects and rules
Server-level redirects, rewrite rules and caching settings recreated, since these live outside the database and are easy to forget.
What gets counted first.
Surprises during a move are almost always things nobody remembered. A careful inventory removes most of them.
The inventory covers
- Hidden services. Cron jobs, scheduled tasks, mail forwarders, subdomains and old landing pages that still receive traffic.
- Integrations. Payment gateways, shipping tools, CRM links and API keys, many of which are tied to the old server address.
- Size and limits. Database size, media volume, memory needs and upload limits, to make sure the new plan fits the site.
- Traffic pattern. Peak days and hours, so the window avoids sales and the new plan can handle the busiest moment.
- Ownership. Who holds the domain, the DNS, the hosting account and the certificates, because access problems cause the worst delays.
A written inventory also becomes part of your recovery notes later. See website maintenance for keeping them current.
The part of a move people fear, explained.
DNS tells the internet where your site and your email live. Mistakes here are invisible until customers complain.
What we manage
- Registrar and nameservers. We confirm where the domain is registered and which service answers for it, so no record is changed in the wrong place.
- Record lifetime. The TTL is lowered days before the move, so the switch spreads quickly, then raised again after.
- Email records. MX, SPF, DKIM and DMARC are copied exactly. Email lives apart from the website and must be treated separately.
- Subdomains. Shop, blog, staging and mail subdomains are listed, since each has its own record and may point somewhere else.
- Certificates. SSL is issued on the new host before the switch, and redirects from http to https are confirmed.
Changes can take hours to reach every network, so we plan the window and communicate it.
Choosing the destination.
The new home should fit the site, the team and the budget. These are the usual options, and the cheapest one is not always the cheapest once problems appear.
| Criteria | Shared hosting | Managed WordPress | VPS or cloud |
|---|---|---|---|
| Typical site | Small brochure site | Business and shop | Busy shop or app |
| Control | Limited | Moderate | Full |
| Upkeep | Provider handles | Provider handles | Someone must manage |
| Scaling | Weak | Good | Excellent |
| Cost pattern | Lowest | Mid | Depends on size |
Keeping rankings through the move.
A move that keeps URLs and content the same should not change rankings. We verify that, instead of hoping.
What we verify
- URL parity. Every public address resolves the same on the new host, or redirects to its exact new equivalent.
- Crawl access. The robots file and any staging blocks are corrected, so search engines can reach the live site.
- Speed. Response time is compared before and after. A slower server can hurt more than it helps.
- Analytics. Tracking tags are confirmed on the new site, so reports do not show a false drop after the switch.
- Monitoring. Search Console and uptime checks run through the first weeks to catch crawl errors early.
If URLs, platforms or domain names change, you need a full plan. See SEO migrations.
What happens during the switch.
The day is dull on purpose. A rehearsed plan has few decisions left to make.
The cutover plan
- A quiet window. Chosen from your traffic and order data, not from our convenience, and agreed in writing.
- A content freeze. Orders and edits pause briefly, or are synced afterwards, so nothing is lost between the final copy and the switch.
- Fast checks. A scripted list of pages, forms and payments is run straight after the DNS change.
- Clear roles. One person on our side makes the call, and one on yours confirms, so nobody waits for a decision.
- A rollback point. The old server stays untouched and ready, with a clear signal for when we would switch back.
For shops, we run a real test order. See our notes on WooCommerce hosting when choosing a host.
Migration questions, answered.
Straight answers to what clients ask before they start.
Will my site go offline during the move?
Usually not. The old site keeps serving visitors while the new one is built and tested. A short content freeze may be needed for shops and sites that take frequent submissions.
What happens to my email?
Email is a separate service from the website. We record the existing mail settings and keep them unchanged, unless you are also moving mailboxes, in which case we plan that separately.
How long does DNS take to update?
Often minutes to a few hours, but some networks take longer. Lowering the record lifetime beforehand speeds this up, and the old server stays live so nobody sees an error.
Can you move a site from a host that has locked us out?
Often yes, if you can prove ownership of the domain and reach the files or a backup. We explain what access is needed before starting and do not bypass any security.
Do you move domains between registrars?
We can guide a transfer, but you keep control of the registrar account. The domain, nameservers and web host are separate things, and we explain which one you actually need to change.
What affects the price?
Site size, platform type, number of domains and subdomains, email complexity, whether the site is a shop, how much testing is needed and how much old clean-up is hiding in the account.
What if something goes wrong?
The old host stays live as the fallback. If tests fail after the switch, we revert the DNS records and fix the problem calmly, then plan a second attempt.
Move once, move calmly.
Send us your current host, platform and domain details. We will return a written migration plan with the risks, the downtime window and what we need from you.