Move from WordPress

Keep the site. Retire the server.

Paste your WordPress address and we move it onto the Internet Computer: same theme, same pages, same URLs. No PHP, database or plugins left to patch, and no rebuild.

What you stop running

A WordPress site is a stack you have to keep patched.

PHP, the web server, MySQL, the theme and every plugin each ship security fixes on their own schedule. After the move, visitors are served files from a replicated network. There's nothing left at request time to exploit or update.

Today
VisitorWeb servernginx / ApachePHP + pluginsruns on every requestMySQLone databaseYour page
After the move
VisitorIC gatewaymany operatorsYour canisterreplicated, certifiedYour pagesame HTML, same URL
How it works

Check, move, verify. In that order.

You see what will change before anything is created, and proof that it worked afterwards.

01

Check your site

Paste your address. We read what any visitor can see (WordPress version, pages in the sitemap, forms, search, comments) and tell you up front what carries over and what doesn't. Nothing is created yet.

02

Move it

We copy every public page with the theme's styles, scripts, images and fonts, rewrite the links, and publish the copy to an asset canister on the Internet Computer.

03

Verify every old URL

Once it's live we request every page we copied from the new site and show the result: how many old URLs answer, which didn't, and what changed on the way.

04

Point your domain

Add your domain when you're happy. Until then your WordPress keeps serving it, untouched. Keep it as a private editor, or switch it off.

What carries over

Everything a visitor sees.

  • Every public page and post, at its original URL
  • Your theme: styles, scripts, fonts and images
  • Media library files linked from your pages (PDFs, images, video)
  • sitemap.xml and robots.txt, so search engines keep their map
  • Contact forms, rewired to your Webstead inbox
  • Old addresses WordPress redirected, as redirect pages
What doesn't

Anything that needs PHP to answer.

Site search and new comments

Both run PHP on every request. Existing comments stay on the page; the forms to add new ones are removed.

Logins, members and shops

Membership areas and WooCommerce carts or checkout need a server. If your site is really an app, it needs a rebuild, not a copy.

Your wp-admin

It stays on your WordPress. Keep it private as your editor, or switch it off.

Pick the right move

A copy, a rebuild, or staying put.

Move to WebsteadRebuild as a canister appStay on WordPress hosting
Best forContent sites: pages, posts, a contact formSites that are really apps: logins, user dataShops and member sites that rely on plugins
Time to liveMinutesA project, often weeksAlready live
Looks the sameYes, it's the same HTMLRebuilt to matchYes
Server to patchNoneNonePHP, MySQL, plugins
Who does itYou, in a few clicksA developer or coding agentYour host and you
Questions

Before you move.

Do I need to install a plugin or give you my WordPress password?

No. The move reads your site the way a visitor does, over its public address. There's no plugin, no export file and no admin login, so nothing on your WordPress changes.

Will my URLs and SEO survive?

Yes. Every page keeps its exact path (for example /2024/05/hello-world/), your sitemap.xml and robots.txt come along, and pages that WordPress redirected get a redirect page at the old address. After the move we test every copied URL on the live site and list any that don't answer.

What happens to my contact form?

Contact forms (Contact Form 7, WPForms, Gravity Forms and plain HTML forms) are rewired to your Webstead form inbox, with an email to you for each submission. They need no PHP afterwards.

What doesn't carry over?

Anything that needs PHP to answer a visitor at request time: site search, posting new comments, logins and member areas, and WooCommerce carts and checkout. Existing comments stay visible. The check step lists what your site uses before you commit.

Can I keep writing in WordPress?

Yes. Keep WordPress somewhere private and keep editing there; one click on Webstead copies the latest version again. Or turn WordPress off entirely once the copy is live. It's your choice.

How is this different from rebuilding the site on the Internet Computer?

A rebuild rewrites your application as canister code, which is the right call when the site is really an app with logins, user data or custom logic. Most WordPress sites are content: pages, posts and a contact form. For those, the copy is the same site, live in minutes rather than a project.

Does it work for sites that aren't WordPress?

Usually. The move works on any site whose pages are plain HTML at public URLs, including Drupal, Joomla and hand-written PHP sites. WordPress is the case we've tuned it for.

See what your WordPress would look like on Webstead.

The check is free and read-only. Free while in beta; your WordPress isn't touched.