Category: Hosting Basics

The email that usually starts this process is the renewal notice. You signed up at $2.95 a month, and the invoice in front of you says $143.88 for the year ahead — plus the domain, plus whatever SiteLock upsell got attached along the way. I’ve moved a lot of sites off Bluehost over twenty-plus years of running websites, and it’s almost always that email that finally pushes people out the door.

Here’s the part nobody tells you: most of the top search results for “how to migrate from bluehost to another host” are written by Bluehost. They are not motivated to make leaving feel easy. Done in the right order, the actual move takes one afternoon of hands-on work, your visitors never see a broken site, and the only genuinely dangerous step is the one everyone skips — email. This guide walks the whole sequence, in order, with the free tools your new host gives you.

Grab everything before you touch anything

Migrations go wrong when people start moving things before they’ve inventoried what they have. While your Bluehost account is still fully alive, collect the following — it takes fifteen minutes and it’s the cheapest insurance you’ll ever buy.

• A full backup you control. Not Bluehost’s backup — yours. Run an export with a plugin like UpdraftPlus or Duplicator and download it to your own machine.
• Screenshots of your DNS zone. Every A record, CNAME, MX, and TXT record. You will want these when something obscure — a verification record, an old subdomain — stops working three weeks later.
• A list of every email address on the domain. Including the forwarding-only ones people forget exist. This list drives the whole email section below.
• Your PHP version. Match it (or go newer) on the destination so plugins don’t misbehave on arrival.
• Domain status. If your domain is registered at Bluehost, you don’t have to transfer it today — you can leave it there and just repoint DNS. If you do want it out, unlock it and request the EPP code now, because transfers take days.

Pick your destination first

The migration tooling lives on the destination side, so choose the new host before you touch the old one. For Bluehost refugees I usually point people at one of two exits, depending on budget.

If you left because of the renewal price, Hostinger is the natural landing spot — ~$3–12/mo at the time of writing, noticeably faster than the shared box you’re leaving, and its migration tool does the heavy lifting for free. If you left because of performance or you’re running anything that makes money, Cloudways gets you managed cloud servers on DigitalOcean, Vultr, or AWS from ~$11–14/mo, with a free migrator plugin and a support team that actually reads your ticket. I run sites on both; the honest comparison is in our Hostinger vs Cloudways breakdown.

If you’re wondering whether to spend more for a fully managed platform instead, start with is managed WordPress hosting worth it — the short answer is “yes, above a certain revenue line” — and the current picks live in our best managed WordPress hosting guide. The full roster of everything we test is on the recommended hosting page.

Move the site with free migration tools

You should not pay anyone to move a standard WordPress site off Bluehost. Every host worth moving to ships a free migrator, and they all work the same way: the new host pulls a copy of your site while the old one keeps serving traffic. Nothing goes down because nothing gets deleted.

On Hostinger, it’s hPanel → Websites → Migrate: hand over the WordPress admin credentials for the Bluehost site and their system copies everything to the new server automatically. On Cloudways, you install the Cloudways WordPress Migrator plugin on the Bluehost site, paste in the destination details from your Cloudways dashboard, and it streams the whole site over. In both cases you get a temporary preview URL when it finishes — that URL is the star of the next step.

The manual route — export an archive, upload it, restore — still works fine, and it’s the fallback when a migrator chokes on a huge database or a security plugin blocks the connection. But try the free tool first. In my experience it succeeds on the first run for the large majority of ordinary sites.

Test before you flip DNS

Right now you have two complete copies of your site: the live one on Bluehost and the new one sitting behind a preview URL. Do not change DNS until the new copy passes inspection. Click through your ten most important pages. Log into wp-admin. Submit every form — contact, checkout, newsletter — and confirm the submissions arrive. Check that the SSL certificate on the new server is issued and valid for your domain (most hosts provision it automatically once DNS points at them, but staging certs let you verify the rest first).

Want to test the real domain against the new server before the public cutover? Edit your computer’s hosts file to point your domain at the new server’s IP. Your machine — and only your machine — will see the new site on the real URL, cookies, HTTPS and all. It’s a five-minute trick that has caught broken permalinks and hard-coded URLs for me more times than I can count.

The zero-downtime DNS cutover

Downtime during a migration is almost always a DNS mistake, and it’s entirely avoidable because of one fact: during propagation, both copies of your site are live. Visitors whose DNS has updated see the new server; everyone else sees Bluehost. Nobody sees an error. Your job is just to keep both copies identical while the world catches up.

• 24–48 hours before: lower the TTL on your domain’s A record to 300 seconds. This tells resolvers worldwide to re-check frequently, which shrinks the switchover window from a day to minutes for most visitors.
• Cutover moment: pick a quiet window, freeze content — no new posts, and pause orders or comments if you run any — then update the A record (or nameservers) to the new host.
• After: with a 300-second TTL, most traffic lands on the new server within an hour. Stragglers on sluggish ISP resolvers can take 24–48 hours, which is exactly why the Bluehost copy stays untouched and online.

One nuance: changing just the A record is faster and keeps your existing mail records intact. Changing nameservers moves everything at once — including MX records — so if you go that route, make sure the new DNS zone already contains your mail settings before you switch. This is where those screenshots from step one earn their keep.

Email — the step that burns people

Here is the single most expensive mistake in host migrations: the site moves perfectly, the owner cancels Bluehost, and every @yourdomain mailbox vanishes with the account. The website was never the fragile part. Email is.

If your mailboxes live at Bluehost, they need a new home before you cancel anything. Hostinger includes email hosting on most plans, so budget movers can recreate their mailboxes there. Cloudways doesn’t host mailboxes (it offers a paid add-on), and premium managed platforms like Kinsta and WP Engine don’t host email at all — that’s normal for the category, not a defect. For anything business-critical I’d put mail on a dedicated provider like Google Workspace or Zoho regardless of host, so your email never depends on where your website lives again.

The safe sequence: create the new mailboxes first, update your MX records to the new mail provider, send and receive a test from every address, then leave the old Bluehost mailboxes alive for another week or two to catch stragglers. If there’s history you care about, drag it across via IMAP in any desktop mail client before the old boxes go dark.

The don’t-cancel-yet checklist

Bluehost keeps billing until you cancel, which creates pressure to pull the trigger early. Resist it. The overlap costs you a few dollars; cancelling early can cost you your inbox. Cancel only when every box below is checked.

• Site loads from the new server — verify with a propagation checker like whatsmydns.net, not just your own browser.
• HTTPS is valid on the new host, with no mixed-content warnings.
• Every form and checkout works on the live domain, not just the preview URL.
• Email sends and receives on the new MX records, from every address on your list.
• Backups are running on the new host — don’t inherit the no-backup habit that made this move scary.
• Your domain is safe — either transferred out or confirmed renewable at Bluehost independently of the hosting plan.

On refunds: Bluehost has historically offered a money-back window on hosting (about 30 days) and pro-rating beyond it has varied — read the current terms before you assume anything. Whatever you’re owed, the domain is yours either way. I typically keep the old account alive for one to two weeks after cutover, then cancel and screenshot the confirmation.

Frequently asked questions

How long does it take to migrate from Bluehost to another host?

Plan for one afternoon of hands-on work spread across two or three days of elapsed time. The automated migration itself usually runs 30 minutes to a few hours; the elapsed time comes from lowering TTL in advance and letting DNS propagate afterward — both of which happen while you do other things.

Will my website go down when I switch hosts?

Not if you keep the Bluehost copy online through the cutover. During DNS propagation both servers hold a complete copy of your site, so every visitor sees a working version. Downtime only happens when people delete the old site or cancel the old account before propagation finishes.

Does Bluehost charge a fee to transfer my website away?

No. Your files and database are yours, and the free migration tools at hosts like Hostinger and Cloudways pull the site out without Bluehost’s involvement. A domain transfer is the only thing with a cost — typically about one year’s renewal paid to the new registrar, which usually extends your registration by a year.

Can I keep my domain at Bluehost after moving my hosting?

Yes. Domain registration and web hosting are separate services — point the domain’s A record or nameservers at your new host and the site moves while the registration stays put. Plenty of people run this way for a year and transfer the domain later, at renewal time, when it’s cheapest.

Should I cancel my Bluehost account right after migrating?

No — wait one to two weeks. You want the old copy alive as a safety net through DNS propagation, and you especially want the old mailboxes reachable until every email address is confirmed working at its new home. The small overlap in hosting fees is cheap insurance.

Want the guided version? Our free courses walk you through this start to finish — including “Launch Your First Website with Claude.”

Last month I rebuilt the same five-page consulting site three ways: once in a closed AI builder, once with 10Web’s AI generator, and once by hand in WordPress. The builder took 11 minutes. The AI-assisted WordPress build took about 40. The manual build ate most of an afternoon. If speed were the whole story, this comparison would be one sentence long.

It isn’t. After twenty-plus years running sites — currently dozens of them, spread across every host I review — I can tell you the decision hinges on two questions almost nobody asks up front: who owns the site when you want to leave, and how much control you get over the things Google actually ranks. Answer those honestly and the choice mostly makes itself. Here’s how I’d make it in 2026.

The quick verdict

If the site is disposable — an event page, a one-off landing page, something you won’t care about in a year — a closed AI builder is fine and genuinely fast. If the site is an asset you plan to grow, use WordPress, and let AI do the heavy lifting so you’re not trading ownership for convenience. Most people reading this land in the second group, and in 2026 the AI-assisted WordPress path costs about the same as a builder subscription while leaving you with a site you actually own.

It’s not two options anymore — it’s three

Most comparison articles still frame this as builder vs. WordPress, as if your only choices were drag-and-drop convenience or a weekend of tutorials. That framing is stale. There are three distinct paths now, and the middle one changes the math.

• Path 1: Closed AI builders. Wix ADI, Squarespace’s AI tools, Framer AI. You describe the site, it appears, you tweak. Fastest start, tightest cage.
• Path 2: AI-assisted WordPress. Tools that generate real, editable WordPress. 10Web builds a complete WordPress site from a prompt on Google Cloud infrastructure, and Hostinger bundles the strongest cheap AI builder I’ve tested with hosting that starts around ~$3/mo at the time of writing. You can also point Claude at a blank WordPress install and get shockingly far — I documented that experiment in Can Claude build a website?
• Path 3: Manual WordPress. Pick a theme, build it yourself or hire someone. Maximum control, maximum time.

Path 2 is the one the old articles miss. It gives you roughly the speed of a builder with the ownership profile of WordPress — which matters more than most beginners realize, for reasons I’ll show you next.

The ownership test: who holds your site when you want to leave?

Here’s the test I apply before recommending any platform: export your site today, and tell me what you’re holding. With WordPress, you’re holding a database and a folder of files that will run on essentially any host on earth. Migration is a solved problem — I’ve moved WordPress sites between hosts in under an hour, dozens of times.

With a closed builder, the honest answer is: not much. Most builder “exports” give you flattened HTML with the interactivity stripped out, or a content file that no other platform can read natively. Your design, your page structure, your e-commerce setup — those live inside the builder and stay there. The vendors don’t hide this; they just don’t lead with it. The practical effect is that leaving means rebuilding, and rebuilding is exactly the pain you paid the builder to avoid. That’s the lock-in problem in one sentence: the switching cost compounds every month you stay.

This is what makes the AI-assisted WordPress path interesting. When 10Web generates a site, the output is a normal WordPress install — real posts, real pages, a real theme you can edit or replace. If you outgrow the platform, you take the site with you. The AI was scaffolding, not a cage. I go deeper on what that actually looks like in my 10Web AI builder review.

SEO control: where builders quietly lose

Let me be fair first: builder SEO is no longer the disaster it was in 2018. Titles, meta descriptions, sitemaps, mobile rendering — the big platforms handle the basics competently now. For a five-page brochure site that gets its traffic from a Google Business Profile and word of mouth, the SEO gap barely matters.

It starts to matter the moment content becomes your growth strategy. On my WordPress sites I control schema markup down to the property level, restructure internal linking across hundreds of posts programmatically, choose exactly which plugins handle caching and image optimization, and read server logs when something looks off in Search Console. On a closed builder you get whatever SEO surface the vendor exposes, and when they don’t expose the thing you need — a specific schema type, a crawl fix, an edge redirect rule — you file a support ticket and wait. I’ve watched sites plateau on builders not because the content was weak but because the platform capped what was technically possible.

Short version: builders rent you competent-enough SEO. WordPress hands you the keys and lets you decide how far to drive.

Side-by-side comparison

Honest downsides of each path

No path is clean, and pretending otherwise is how bad recommendations get made. Here’s what I’d warn a friend about for each.

• Closed builders. The lock-in compounds. Intro pricing roughly doubles at renewal on most platforms. And the AI design output is convincing until you need something the template system can’t express — then you hit the walls fast.
• AI-assisted WordPress. It’s still WordPress underneath. Plugin updates, an occasional compatibility hiccup, and a dashboard with more options than a beginner strictly wants. Generated designs also need an hour of human tidying — AI layouts are 85% right and confidently wrong about the rest.
• Manual WordPress. Time and decision fatigue. Fifty thousand plugins is a feature until you’re choosing between six caching plugins at midnight. Security and backups are your job unless your host covers them — one more reason host choice matters more than theme choice.

The 60-second decision flowchart

Answer three questions in order and stop at the first exit.

• 1. Will this site still matter in 18 months? If no — event page, temporary campaign, testing an idea — use whatever builder you can drive fastest and don’t overthink it.
• 2. Is content or search traffic part of the plan? If yes, that’s a WordPress answer. The SEO ceiling and the ownership test both point the same direction, and you’ll feel the builder’s walls within a year.
• 3. How much do you want AI to do? On a tight budget, Hostinger gets you hosting plus a capable AI builder for less than a builder subscription alone. If you want the strongest prompt-to-finished-site experience on real WordPress, that’s 10Web — I compare the two head-to-head in Hostinger vs 10Web. And if you’d rather have an AI agent build on hosting you fully control, start with my guide to the best AI web hosting.

That’s the whole decision. Speed is a tiebreaker, not a strategy — ownership and SEO control are what you’ll care about in year two.

Frequently asked questions

Is an AI website builder better than WordPress?

For speed on a short-lived site, yes. For anything you plan to grow, no — WordPress gives you full ownership of your files and database plus an SEO ceiling builders can’t match. In 2026, AI-assisted WordPress tools deliver most of the builder speed without the lock-in, which removes the main reason builders used to win.

Can I move my site from an AI website builder to WordPress?

Only partially. You can usually export text and images, but design, structure, and any e-commerce configuration typically have to be rebuilt by hand. That rebuild cost is the core of the lock-in problem — it grows with every page you add, which is why I recommend deciding on ownership before you build, not after.

Is WordPress better for SEO than website builders?

For basic on-page SEO, the gap has mostly closed. For everything past the basics — granular schema, programmatic internal linking, crawl diagnostics, edge redirects, plugin-level performance work — WordPress wins decisively because nothing is walled off. If search traffic is your growth channel, that control compounds.

Do professionals still use WordPress in 2026?

Overwhelmingly. It still powers around 40% of the web, and the tooling has gotten better, not worse — the modern workflow is often an AI layer generating and editing a standard WordPress site underneath. Professionals stay because the platform is portable, extensible, and owned by no single vendor.

Want the guided version? Our free courses walk you through this start to finish — including “Launch Your First Website with Claude.”

The last site I launched with Hostinger’s AI builder went from blank prompt to live URL in 41 minutes — and 15 of those were me second-guessing a headline. The generation itself, the part that used to eat a weekend of theme-hunting and demo imports, took under two minutes. The speed is real. So are the traps: renewal pricing most beginners never read, an email setup that is not where you expect it, and an SEO panel almost everyone skips on the way to the publish button.

I run sites across every host we review here, and I have used this builder enough times to know exactly where people get stuck. This walkthrough covers the whole path — generation, editing, domain, SEO, and the settings that bite you six months later. Work through it in order and you should be live inside an hour.

What you need before you start

Three things: a Hostinger plan that includes the builder, a domain, and an uninterrupted hour. The builder ships with the cheap tiers — entry pricing runs roughly $3–12/mo at the time of writing, which is why Hostinger owns the budget end of this market. Most annual plans include a free domain for the first year, so if you are starting from zero, one checkout covers everything.

Pick the entry-level plan unless you already know you need more — the builder features are the same, and upgrading later takes two clicks. Sign up through Hostinger, choose your term carefully (more on why in the settings section), and you will land in hPanel, the control panel where everything below happens.

Still deciding whether this builder is the right tool at all? Read our full Hostinger AI website builder review first. This tutorial assumes you have decided and want it done.

Step 1: Generate your site in four clicks

From hPanel, the path is: Websites → Add website → Hostinger Website Builder → Create a website with AI. Four clicks, then a short form asking for your brand name, website type, and a description.

The description box is the only part worth slowing down for. The AI builds the entire site — structure, copy, images — from those few sentences, so give it real material. Mine follow a simple pattern: what the business does, who it serves, and the tone I want. Something like: “A mobile dog grooming service in Austin serving busy professionals. Friendly, practical tone. Emphasize convenience and transparent pricing.” Two or three specific sentences beat a paragraph of vague ones.

Hit create and wait. In my runs, generation takes 60–90 seconds and produces a complete multi-section site with draft copy and stock images, plus a choice of layouts and color palettes. Pick the one closest to right and move on — you will change less than you think.

Step 2: Edit the sections that matter

The editor is grid-based drag-and-drop — sections stack vertically, elements snap into place inside them. You can rebuild everything. Don’t. Three edits carry most of the result:

• Rewrite the hero headline yourself. AI-generated headlines are grammatical and dead. Yours should say what you do and for whom in under ten words.
• Replace the stock images. The AI pulls generic photos. Swap the hero image and anything with faces for your own — real photos convert, stock reads as filler.
• Cut pages down to what you will maintain. The AI often generates five or six pages. A launch site needs three or four good ones — Home, Services, About, Contact.

The built-in AI writer can regenerate any text block if you feed it direction — useful for service descriptions, weak for anything that needs personality. Global styles for fonts and colors live in the left sidebar and cascade site-wide, so fix branding there instead of section by section.

Step 3: Connect your domain

If you claimed the free domain at checkout, this step is already done — skip ahead. For a domain registered elsewhere, you have two options:

• Point your nameservers to the pair Hostinger displays in the domain-connection screen. This hands Hostinger full DNS control and is the easiest path for beginners.
• Add an A record at your current DNS host pointing at the IP Hostinger shows you. This keeps DNS management where it already lives — my preference when a domain carries existing email records.

Propagation usually lands within 15 minutes to a couple of hours in my experience, though the official warning is 24–48. SSL is free and automatic — once the domain resolves, give it a few minutes and confirm the padlock appears. If it has not after an hour, retrigger the certificate from the website settings rather than waiting it out.

Step 4: SEO basics before you hit publish

Every page has an SEO panel — title, meta description — and the AI will draft both. Take the draft, then edit it: put the phrase people actually search at the front of the title, and make the description a reason to click, around 150 characters. The AI drafts are accurate but generic, and generic loses the click.

Beyond the panel, three quick tasks before launch: upload a favicon in settings (the default placeholder makes a site look abandoned), connect Google Search Console so you can see what you rank for, and add alt text to the images you replaced. None of this ranks you by itself — skipping it just guarantees you stay invisible longer.

The settings beginners miss

This section exists because these four items generate more support tickets and angry-renewal stories than everything else combined.

• The renewal term. That advertised ~$3/mo is an intro rate for the term you pay upfront — renewals typically run two to four times higher. Buy the longest term you will genuinely use, then set a calendar reminder 30 days before renewal so the new rate never surprises you. This is the most common complaint about every budget host, and it is entirely avoidable.
• Email is not automatic. Plans include free email accounts, but nobody creates the mailbox for you. Go to Emails in hPanel, create name@yourdomain.com, and if your DNS lives elsewhere, add the MX records it hands you. Do this before you print business cards.
• Auto-renewal defaults to on. Fine if intentional — just confirm the card and the term are what you meant them to be.
• Backups are weekly on cheap tiers, not daily. Before any big redesign, generate a manual backup. It takes thirty seconds and has saved me exactly twice — which is enough.

Where the builder runs out of road

Honest limits, because every tool has them. The Hostinger builder is not WordPress — there is no plugin ecosystem, the blogging tools are basic, and there is no clean export. Your site lives inside the builder, and leaving means rebuilding. For a services site, a portfolio, or a local business front door, none of that matters. For anything you expect to grow — a content site, a store beyond the basics, custom functionality — it eventually will.

Two upgrade paths are worth knowing before you need them. If you want AI generation but on real, editable WordPress, our Hostinger vs 10Web breakdown covers exactly that trade-off. And if you would rather skip site builders entirely, can Claude build a website shows the workflow I now use for most new launches — an AI agent building a real site on ordinary hosting, nothing locked in. Our best AI web hosting guide ranks every option in one place.

The builder is the right call when speed beats flexibility — and at these prices, Hostinger is the cheapest legitimate way to get a real site live this afternoon. Just make the choice knowing what the exit costs.

Frequently asked questions

Is the Hostinger AI website builder free?

No — there is no free tier. The builder comes bundled with hosting plans starting around $3/mo at the time of writing, and the 30-day money-back window is effectively your free trial. For what it includes — hosting, builder, SSL, usually a first-year domain — it is the cheapest complete package I have tested.

How long does it take to build a website with Hostinger AI?

Generation itself takes 60–90 seconds. A realistic prompt-to-published timeline — editing copy, swapping images, connecting a domain — is 45 minutes to a few hours depending on how picky you are. My fastest real launch was 41 minutes.

Can I edit my website after the AI creates it?

Yes. Everything the AI generates is editable in the drag-and-drop editor — layout, text, images, colors, fonts. Treat the generated site as a first draft, not a final design.

Can I move my Hostinger builder site to WordPress later?

Not directly — there is no export to WordPress. You would rebuild the site, though your plan typically includes WordPress hosting, so the host itself can stay. If a future migration matters to you, weigh that before you build here.

Outgrown the builder already, or want the guided version of all this? Our free courses walk you through launching start to finish — including “Launch Your First Website with Claude.”

Web Host Training has one goal: make you genuinely good at hosting websites — without charging you a dime. Every tutorial and every video course here is free, funded by affiliate partnerships instead of paywalls.

We cover the fundamentals every site owner needs — choosing a host, WordPress, domains and DNS, performance, and security — plus the topic nobody else is teaching yet: hosting for AI agents. As agents start building and managing real websites, the infrastructure that serves them is becoming a skill of its own. That’s the frontier this site is built for.

New guides land every week, and the first video courses are in production now. Start with the guides, check the courses, and if a guide saves you an afternoon, that’s the whole point.