Move a business website without losing the essentials

1. List what the current website does

Write down the important pages, images, downloads, forms, business email addresses and integrations. Save a backup or export from the existing host and record the live page addresses customers already use.

FutureHost’s website import copies the public front end. It does not copy databases, plugins, customer accounts or server code. Shops, forums and other systems with private data need a separate migration or rebuild plan. The review can identify pages that are not suitable for an automatic copy.

2. Run the review before changing anything

Use Import my website to review a site you own or have permission to copy. The review checks eligibility and estimates the pages, files and work involved. Read the result and any warnings before starting the copy.

The review is free. Importing requires a paid plan: Website supports up to 10 pages and Business up to 50. The import screen shows the estimated AI cost and your available AI balance. Review these together with the website subscription before confirming.

3. Rebuild and inspect the draft

Follow the import workflow to copy and package the eligible content, then rebuild it in your workspace. Keep the old website running while you review the result. Downloads and archives are useful backups, but a successful copy alone does not prove every page works.

Compare the important pages with your original. Check image quality, headings, internal links and navigation. Reconnect enquiry forms and external integrations deliberately: copying their appearance does not necessarily preserve their behaviour.

• Check every high-value service page and its main call to action.
• Test contact links, downloads and submitted enquiries on a phone.
• Replace outdated details and confirm you have the right to reuse the images and copy.

4. Prepare URLs, email and the domain change

Keep existing public page paths where possible. If a page must move, arrange a redirect from the old path and test it; do not assume the import creates every redirect automatically. Record the new canonical address and review the sitemap.

Treat email as a separate service. Leave existing MX and authentication records in place if mail stays with the current provider. Before changing website DNS, record the current routing values so you can restore them if a material problem appears.

5. Switch only after the new site passes review

Connect your domain through the FutureHost dashboard and follow the account-specific DNS instructions. Wait for the domain and HTTPS status to become active, then check the exact public address in a fresh browser session.

Test the main pages and one full enquiry after the switch. Keep the previous hosting available during the transition, monitor customer contact routes and fix broken links promptly. Cancel the old service only after you have confirmed the website, email and any retained data are where you expect them to be.