WotWP Blog

Your WordPress plugins don't move. Here is what replaces the common ones

An open kraft cardboard moving box on a blue background, with small tools, a padlock, a magnifying glass and white puzzle pieces laid out beside it rather than inside

The short answer

None of your WordPress plugins move with your site, because a plugin is WordPress code and EmDash "does not run PHP, WordPress themes, or WordPress plugins" (EmDash docs). What matters is the job each plugin did. On EmDash, most of those jobs are either built in, no longer needed, or done by a plugin written for EmDash. A few have to be rebuilt.

Here is how the common ones sort out:

  • Built in: your SEO plugin's titles, descriptions and sitemap, and your redirects plugin. EmDash has both in its admin.
  • Not needed in the same way: caching plugins such as WP Rocket, and security plugins such as Wordfence, which mostly guard WordPress's own code.
  • Replaced by an EmDash plugin or a setting: contact forms, image optimization and backups.
  • Rebuilt or left behind: page builders, tracking code and anything custom. A store, member area or online course is a reason to stay put for now.

What replaces each common plugin

The table covers the plugins a typical small business site runs. Find yours by the job it does, not by its name.

WordPress plugin, by job

On EmDash

What you do

SEO (Yoast, Rank Math)

Built in: an SEO panel on each page, a sitemap and `robots.txt`

Check that your titles and descriptions came across

Redirects (Redirection)

Built in: a Redirects page and a log of missed pages

Bring your existing redirects with you

Caching (WP Rocket, W3 Total Cache)

Not needed as a plugin; pages are cached by the site itself

Nothing to install

Security (Wordfence, Sucuri)

Not the same job: no WordPress code or PHP left to scan

Ask who applies EmDash updates

Contact forms (Contact Form 7, WPForms, Gravity Forms)

The Forms plugin for EmDash

Rebuild each form and test that its emails arrive

Backups (UpdraftPlus)

Done by the host, at the database and file storage level

Ask your host how far back a restore can go

Image optimization (Smush, ShortPixel)

Built into how EmDash shows images

Nothing to install

Analytics and tracking code (Site Kit, header-script plugins)

Added to the site's code

List every tag you use

Page builders (Elementor, Divi)

No equivalent; the layouts are rebuilt

See our Elementor guide

The rest of this guide explains each row.

Built in: SEO and redirects

Your SEO plugin. EmDash has its own SEO features: each page gets an SEO panel with a title, a description, a social sharing image, a canonical address and a "Hide from search engines" switch. The site also serves a sitemap at /sitemap.xml and a robots.txt file (EmDash docs). There is no plugin to install or keep updated.

What matters is your existing titles and descriptions. EmDash's WordPress import "can copy Yoast and Rank Math SEO titles and descriptions" when it runs through the EmDash Exporter, the small plugin you add to the old site for the move. The docs add a catch: those copied values land in their own fields, "separate from the SEO panel, so the page template has to render them" (same source). In plain terms, someone has to make sure the new pages actually show them. Our guide to moving your Yoast SEO to a new site covers that check.

Your redirects plugin. EmDash has a Redirects page in its admin for permanent and temporary redirects, and it can mark a deleted page as gone. When you change a published page's address, it adds a permanent redirect from the old one by itself. It also keeps a log of addresses visitors asked for that didn't exist, so you can redirect the common ones (EmDash docs). Redirect rules aren't on the list of what EmDash's WordPress import brings in (EmDash docs), so export the list from your redirects plugin before the move.

Not needed in the same way: caching and security

Caching plugins. WP Rocket and its rivals speed up WordPress by saving finished pages so the server doesn't build them again for every visitor. EmDash's own guide to porting WordPress plugins says not to bring across "a plugin whose only purpose is to implement a WordPress concern that Astro or EmDash already replaces", and names "PHP page caching" as the first example (EmDash docs). On Cloudflare, an EmDash site can store finished pages at the edge, and a page served from there "never runs" the site's code at all. When you publish an edit, the cached copy is cleared and the change "usually becomes visible within seconds" (EmDash docs).

Security plugins. Wordfence and similar plugins scan and shield WordPress itself, and that is where the risk sits: Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, and 91% of them were in plugins (Patchstack). An EmDash site has no WordPress core, themes or plugins to scan.

That doesn't mean nothing needs looking after. EmDash itself releases new versions, and so do any EmDash plugins your site uses. Someone has to apply those updates and check the site afterward. Ask who that is before you move.

Replaced by an EmDash plugin or a setting: forms, backups, images

Contact forms. EmDash has a Forms plugin of its own, described by its makers as a way to "build forms, collect submissions, send notifications" (EmDash on GitHub). Your forms don't import, so each one is set up again: its fields, who gets the email, and the reply the visitor sees. For the emails to go out, the site also needs an email provider. On Cloudflare that can be Cloudflare's own email sending, which "needs no external account or API key" (EmDash docs). Our guide to contact forms after a website migration lists what to test before you trust a rebuilt form.

Backups. UpdraftPlus and similar plugins copy your WordPress database and files on a schedule. On EmDash, backups happen below the site, where the content and files are stored, not in a plugin. On Cloudflare, the database can be rolled back to an earlier point, and Cloudflare "currently retains them for 7 days on the Workers Free plan and 30 days on the Workers Paid plan." Images and other uploaded files need "an object-level backup in addition to the database" (EmDash docs). So the question changes from "which backup plugin?" to "who holds my backups, and how far back can they go?" Our guide to backing up a WordPress site covers the copy to take before the move.

Image optimization. Plugins such as Smush shrink and resize your images. On EmDash, the site's image component does that when a page shows an image: it serves "responsive variants", sized for the screen, and loads images lower on the page only as the visitor scrolls to them (EmDash docs). Your images are copied across in the import (EmDash docs); the optimizing is part of how the new site displays them.

Rebuilt or left behind: page builders, tracking code and custom plugins

Page builders. Elementor, Divi and other builders draw the layout of your pages, and EmDash has no equivalent to install. The layouts are rebuilt as part of the new design. Our guide to moving away from Elementor explains what happens to those pages, and our guide to what happens to your WordPress theme covers the rest of the look.

Analytics and tracking code. On WordPress, Google Analytics, ad tags and chat widgets often arrive through a plugin. On EmDash they go into the site's code. EmDash's guide to Google AdSense, for example, says that setup "uses site code; it does not require an EmDash plugin" (EmDash docs). Make a list of every tag your site loads, so none is forgotten.

Custom and special-purpose plugins. A plugin someone wrote just for your site, a booking system or an event calendar has to be rebuilt as an EmDash plugin or replaced by an outside service. EmDash's docs explain how a developer ports one, starting with an inventory of everything the plugin does (EmDash docs). That is real development work, so get it priced before you commit.

Make your plugin list before anyone quotes

You can do this yourself in your WordPress dashboard, and it makes any quote more accurate.

  1. Open Plugins → Installed Plugins and write down every plugin, active or not.
  2. Next to each one, write the job it does in your own words: "the contact form on the Contact page", "makes the site faster", "I don't know".
  3. Mark the ones you actually use. Inactive plugins and ones nobody remembers installing can usually be left behind.
  4. Sort the rest into the four groups above: built in, not needed, replaced, or rebuilt.
  5. Note the settings that hold your data: your form recipients and confirmation messages, your redirect list, your tracking IDs.
  6. Flag anything the business depends on, such as bookings, payments or a members' area. That is the first question to ask about any move.

Keep the old site running until the new one has been checked page by page. Our website migration SEO checklist covers the rest of that check.

What the plugin part costs

When you compare quotes, ask what happens to each plugin on your list. Moving the content and rebuilding what the plugins did are different pieces of work.

On a move with us, "We rebuild what your plugins did as part of your move, wherever we can", and "Anything new is quoted before we start" (WotWP pricing). A move costs $790 for up to 25 pages, $990 up to 50, $1,290 up to 100 and $1,990 up to 250. Rebuilding page-builder layouts, such as Elementor or Divi pages, is $390 on top.

When to stay on WordPress

Stay on WordPress if a plugin is the heart of your site: an online store, a members-only area, online courses or a complex booking system. Those sites aren't a fit for a move yet. Stay put too if you often add features yourself by installing WordPress plugins. On EmDash, a feature that isn't built in or available as an EmDash plugin has to be built.

Bring your WordPress site into the AI era on EmDash and Astro. We check every URL, redirect, form and search detail against your live site before anything changes, and switch only after you approve the preview, with the rollback written down. After launch we host the site and email you a monthly certificate listing the checks we ran and what changed. A free, read-only check of your public pages shows whether your site is a good fit and the exact price before you ask.

Want to know where your site stands? Check your site for free.

Frequently asked questions

Can I use my WordPress plugins on EmDash?

No. EmDash doesn't run PHP or WordPress plugins, so none of them can be installed on an EmDash site. What carries over is the job each plugin did: SEO and redirects are built in, forms have an EmDash plugin, and custom features are rebuilt.

Do I need Yoast or Rank Math on EmDash?

No. EmDash has an SEO panel on each page, a sitemap and a robots.txt file built in. The import can copy your Yoast or Rank Math titles and descriptions across, but someone should check that the new pages actually show them.

Do I need a caching plugin like WP Rocket on EmDash?

No. EmDash's own docs say not to port a plugin whose only job is PHP page caching. On Cloudflare, an EmDash site can keep finished pages at the edge and clears them when you publish an edit, so changes usually show within seconds.

Do I need Wordfence or another security plugin on EmDash?

Not in the same way. Security plugins mostly guard WordPress's own code, and an EmDash site has no WordPress core, themes or plugins. EmDash and its plugins still get updates, so ask who applies them and checks the site afterward.

What happens to my contact forms when I move?

They don't import. Each form is rebuilt with the Forms plugin for EmDash, which builds forms, collects submissions and sends notifications. The site also needs an email provider set up, so test that every form's emails arrive before the old site goes away.

How do I back up an EmDash site without UpdraftPlus?

Backups happen where the content is stored, not in a plugin. On Cloudflare, the database can be rolled back up to 7 days on the free plan or 30 days on the paid plan, and uploaded files need their own backup. Ask your host what they keep.