Changing your web hosting provider does not have to mean changing your domain name, redesigning your website or losing business email. But a careless migration can interrupt enquiries, forms, orders or staff logins.
The safer method is to prepare the new environment, test it and change traffic only when you know it works. Here is a practical migration plan for business sites, blogs and online stores.
Step 1: Write down what must move
A website may involve more than a `public_html` folder. Before touching the live server, identify:
- Website files, themes, plugins and uploaded media.
- Databases and their connection settings.
- PHP version, extensions, background jobs and rewrite rules.
- SSL/TLS configuration and any CDN or caching service.
- Contact forms, transaction emails and external APIs.
- Domain DNS, business email, subdomains and redirects.
If your business uses a separate email hosting service, document that too. A website migration should not accidentally move or break your email service.
Step 2: Create a complete, restorable backup
For a WordPress site, copy both the files and the database. Confirm the backup is readable and store a safe copy away from the old server.
For a custom application, record its configuration and dependencies. Do not include secret passwords in a publicly accessible archive or ordinary email attachment.
A backup is only truly useful if you can restore it. Test important data on an isolated environment whenever possible.
Step 3: Prepare your new hosting account
Compare the new server's supported software with your site. Verify the PHP runtime, database compatibility, storage, available processing capacity and any required cron jobs before importing the site.
If the existing site uses a framework, queue worker or unusual directory layout, ask the new provider whether the environment supports it. Do not assume that every hosting package works for every application.
You can compare Intek Host cloud hosting plans or WordPress hosting options depending on the type of website you operate.
Step 4: Restore a copy to the new environment
Upload the site files and import the database through the supported tools. Update the configuration to point to the new database and any environment-specific directories or credentials.
Use a preview URL, staging hostname or hosts-file method where appropriate. Some WordPress sites need careful handling of the site URL and serialised settings; use tools designed for the application rather than blindly replacing every string in the database.
Keep the old site serving visitors during this stage.
Step 5: Test the site before changing DNS
Open the new copy and test the features most likely to affect your business:
- Homepage and important service or product pages.
- Images, CSS, fonts and JavaScript.
- Contact forms and outbound notification emails.
- Admin login and user permissions.
- Customer accounts, search and checkout if applicable.
- Scheduled tasks, payments and integrations.
- HTTPS and redirects.
For an online shop, use a safe staging payment mode rather than attempting real customer payments on a test copy.
Step 6: Plan how to handle new content and orders
A migration can cause data loss if visitors continue changing the old site after you copy its database. Blogs with occasional comments face less risk than active stores receiving orders every minute.
Choose a cutover plan based on the application. You may need a short maintenance window, a final database sync or another method to keep transactions consistent. Never assume that changing DNS alone transfers orders created after the database copy.
Step 7: Make the DNS change deliberately
Once the new site passes testing, update the appropriate DNS record or nameserver configuration. Lowering DNS TTL in advance can help some resolvers refresh sooner, but it cannot guarantee an instant global switch.
Preserve email-related DNS records. If you change nameservers, make sure the new DNS zone contains the existing MX, SPF, DKIM, DMARC and other required entries before cutover.
Avoid multiple simultaneous domain, website and mailbox migrations unless there is a clear reason and a detailed plan.
Step 8: Monitor the launch
After changing DNS, check the site from more than one network and device. Review web-server errors, page loading, contact form submissions and transaction notifications.
Some visitors may still reach the old destination temporarily due to DNS caching. Keep the old environment available for a sensible overlap period, based on your business requirements and provider terms.
Step 9: Keep a rollback option
Do not cancel the old hosting account immediately. Keep a verified backup and a short written plan for returning traffic to the original setup if a critical problem appears.
If customer data changed after the cutover, carefully reconcile it before rolling back. Reverting server files without considering new orders or messages can create a second incident.
Common website migration mistakes
- Migrating only the files when the database holds most content.
- Forgetting email DNS records when changing nameservers.
- Testing the homepage but not the contact form or checkout.
- Cancelling old hosting before all visitors reach the new site.
- Ignoring cron tasks, environment variables or required PHP extensions.
- Uploading backup archives into a public web directory and leaving them exposed.
Frequently asked questions
Do I have to transfer my domain? Usually not. You can point an existing domain to a new hosting provider.
Can a site move without downtime? Some migrations achieve a very smooth cutover, but an exact zero-downtime outcome depends on the software, DNS arrangement and data-change requirements.
How long should I keep the old hosting? Keep it until you have checked traffic, transactions, mail dependencies and a practical rollback plan. Your application and contract determine the appropriate period.
Move with a plan, not a gamble
A well-organised hosting move can protect your online presence and provide room for growth. Explore Intek Host hosting plans and review the migration guidance available for your type of website before ordering.
