We confirm scope and price in writing. The main factors are:
- Site size and complexity.
- Number of sites or domains.
- Email accounts to move.
- Store or booking data that changes during the move.
- Testing depth and monitoring.
Hosting fees are paid to the host and are separate from our fee. Some hosts offer free migration, which may suit simple sites. We tell you where a free service is enough and where independent care is worth paying for.
Tell us about your site and current host, and we will reply with a plan and a quote.
Choosing the type of hosting is part of the decision. Shared hosting places many sites on one server and is the cheapest, which suits small brochure sites with modest traffic. Virtual private servers and managed WordPress hosting give more dedicated resources and often better speed and support. Cloud hosting spreads load across several machines and can scale with demand. We explain these options in simple terms and match them to your traffic, budget and the skills of your team.
Location matters for speed. A server physically closer to your customers usually responds faster, so a business serving India often benefits from a host with servers in or near the country. A content delivery network can also help by serving static files from locations nearer to visitors. We check how the site performs from your main markets before and after the move.
Security is reviewed during migration. We make sure the new server runs supported software versions, that file permissions are correct, that old admin accounts are removed and that SSL certificates are installed and renewing. A migration is a good moment to clean up unused plugins and themes, scan for malware and strengthen logins, so that you do not carry old problems to the new host.
Domains and DNS are handled with care. The domain registration is separate from hosting, and it should stay under your control. We document the current DNS records, including mail, verification and subdomain entries, and recreate them where needed. Lowering the TTL ahead of time and checking propagation afterwards helps make the switch quick and visible to us.
Communication is part of a good migration. We tell your team when the move will happen, what to avoid during the window, such as publishing new content or taking orders by hand, and how to report any issue. A short note at the end confirms that the move is complete and the old hosting can be closed.
Some migrations involve extra complexity, such as multiple sites on one account, subdomains, staging copies, custom server settings or older software that the new host does not support. We identify these early, because they affect timing and cost. Where software is outdated, we recommend updating or rebuilding parts of the site as a separate, planned task, instead of moving a fragile setup unchanged.
A rollback plan is always prepared. If a serious problem appears after the switch, we can point DNS back to the old server while the issue is fixed, because the old site has been kept intact. This safety net is the main reason we do not close the old hosting on the day of the move.
For stores and booking sites, we plan the final data sync carefully. Orders, enquiries and bookings that arrive during the move are copied across, so nothing is lost. We often place the site in a short maintenance mode at the moment of final sync, then reopen on the new server. Customers see a brief notice, not an error.
After the move, we also review hosting settings that affect performance, such as caching, compression, image handling and database optimisation. A new server with default settings is rarely at its best, and small tuning steps often give noticeable gains in speed and stability.
