How to Migrate WordPress to Decentralized Hosting

Already have a WordPress site on Bluehost, WP Engine, Kinsta, SiteGround, GoDaddy, or Hostinger? You can move it to the Flux decentralized cloud without losing content, and usually without any downtime. This guide walks through the whole migration — from choosing a method to flipping your DNS — so you end up with a faster, censorship-resistant, lock-in-free WordPress site.

Why migrate WordPress to decentralized hosting?

People switch for a few consistent reasons: managed hosts get expensive after the first-year promo ends; a single provider is a single point of failure and a single point of censorship; and proprietary panels and egress fees make you feel trapped. Moving to a Web3 host on Flux gives you three redundant instances across independent nodes, no central account that can be suspended, standard WordPress with no vendor lock-in, dedicated resources from $2.99/month, and the option to pay with FLUX crypto. You own your data and can move again anytime — the opposite of lock-in.

Before you start: a pre-migration checklist

• Take a full backup of your current site (files + database). Never migrate without one.
• Note your PHP and WordPress versions so you can match or exceed them.
• List active plugins and themes; deactivate anything you no longer use to travel light.
• Record your domain's current DNS records so you can reproduce them.
• Lower your domain's DNS TTL a day ahead to make the final cutover fast.

Step 1 — Deploy a fresh WordPress on Flux

First, create your destination. Sign up, pick a plan and a region close to your audience, and deploy a new WordPress site — it's live in under 30 seconds on a free .app.runonflux.io subdomain with SSL. You'll import your existing content into this instance before pointing your domain at it, so your live site stays up the whole time.

Step 2 — Choose your migration method

Option A: Migration plugin (easiest)

Plugins like All-in-One WP Migration, Duplicator, or Migrate Guru package your entire site — files, database, plugins, themes, and media — into a single archive. Install the same plugin on your new Flux WordPress, upload the export, and it rebuilds the site for you. This is the recommended path for most people because it handles the database search-replace (URLs) automatically.

Option B: Backup restore

If you already run a backup plugin (UpdraftPlus, Jetpack VaultPress, etc.), restore its backup set onto the new site. Flux also supports restoring from a remote backup URL and a built-in file browser for uploading archives directly.

Option C: Manual migration

For full control, export the MySQL database with mysqldump (or phpMyAdmin), copy the wp-content folder, import the database on the new instance, update wp-config.php credentials, and run a search-replace to swap the old URL for the new one. This is the most hands-on route and best suited to developers.

Step 3 — Import your content and verify

Run your chosen import into the Flux WordPress instance. Then, using the temporary .app.runonflux.io subdomain, click through the site: check the homepage, a few posts and pages, images and media, menus, forms, and — if you run a store — WooCommerce products and checkout. Confirm plugins are active and settings carried over. Fix anything now, while your production domain is still safely pointing at the old host.

Step 4 — Test before you switch DNS

Preview the site thoroughly on the subdomain. If you want an even more accurate test using your real domain, add a temporary entry to your computer's hosts file so only you resolve the domain to the new site. Verify SSL, permalinks, and any hardcoded URLs. Only proceed once you're confident the migrated site is a faithful copy.

Step 5 — Point your domain (the cutover)

When you're happy, update your domain's DNS: add a CNAME record pointing to your Flux app address and set your custom domain in the dashboard. Because you lowered the TTL earlier, the change propagates quickly — often within minutes. SSL for your domain is handled automatically. Keep the old host running for 24–48 hours until propagation completes worldwide, so no visitor hits a stale server.

Step 6 — Post-migration cleanup

• Confirm the site loads over HTTPS on your real domain with a valid certificate.
• Re-test forms, login, search, and checkout on the live domain.
• Enable automatic backups on the new site.
• Submit your sitemap in Google Search Console and check for crawl errors.
• Once everything is stable for a couple of days, cancel your old hosting plan.

Will migrating cause downtime or hurt SEO?

Done in this order — build the new site, import, test, then switch DNS — migration causes effectively zero downtime, because your domain only moves after the copy is verified. Your URLs stay the same, so there's no SEO loss; if anything, faster load times and better uptime on a redundant network can help rankings. Keep the same permalink structure and you won't need redirects.

Get started

Ready to leave your current host behind? Deploy your destination site, then follow the steps above. The full Web3 WordPress hosting guide covers what decentralized hosting changes and how to deploy from scratch.