Replacing a plugin sounds simple: install the new one, delete the old one. In practice, the old plugin has usually left shortcodes in your pages, settings nobody wrote down, and perhaps data in its own database tables. Here’s a routine that avoids surprises.
Key takeaways
- Write down what the old plugin does on your site before you choose a replacement.
- Always rehearse the switch on a staging copy.
- Shortcodes, widgets and blocks from the old plugin must be replaced on every page that uses them.
- Delete the old plugin only after the new one has run without problems for a week.
Step 1: list what the old plugin actually does
Before shopping for a replacement, note every job the plugin does on your site, not just the obvious one. A contact form plugin might also send a copy to a CRM, save entries, and add a reCAPTCHA. Check its settings pages and note:
- Which pages use it (search your content for its shortcodes or blocks).
- Its settings, with screenshots.
- Any data it stores: entries, galleries, custom post types, uploaded files.
- Integrations: emails, payment gateways, other plugins that depend on it.
Step 2: choose a maintained replacement
Look up the old plugin in our plugin directory: outdated plugins show a “Better alternatives” box with maintained plugins that do the same job, compared side by side on updates, compatibility, ratings and installs. Or run your whole site through the plugin checker to get alternatives for every problem plugin at once. Then check the candidate against your list from step 1, and read our checklist for choosing a WordPress plugin.
Step 3: rehearse on a staging copy
Many hosts offer one-click staging. If yours doesn’t, a backup plugin can clone the site to a subdomain. Do the whole switch there first, so mistakes cost nothing.
Step 4: move settings and content
- Use an importer if one exists. Many plugins can import from their popular competitors (form builders, SEO plugins, gallery plugins). Check the new plugin’s Tools or Import screen.
- Recreate settings by hand using your screenshots where there’s no importer.
- Export entries or data from the old plugin (often as CSV) if you need to keep them.
Step 5: replace shortcodes, widgets and blocks
Once the old plugin is deactivated, its shortcodes appear as plain text like [old_slider id="3"]. Find every page that uses them; with WP-CLI you can search the database without changing anything:
wp db query "SELECT ID, post_title FROM $(wp db prefix)posts WHERE post_status = 'publish' AND post_content LIKE '%[old_slider%'"Replace each one with the new plugin’s shortcode or block, and check widgets and template parts too.
Step 6: test the important paths
- Submit forms and confirm the emails arrive.
- Place a test order if the plugin touches the shop.
- Check the pages that used the old plugin on mobile and desktop.
- Check speed: the new plugin shouldn’t make key pages slower.
Step 7: switch the live site
Take a fresh backup, then repeat the steps on the live site at a quiet time. If the old plugin created public URLs (galleries, event pages, product pages) that change, add redirects so visitors and search engines land on the new pages.
Step 8: remove the old plugin
Leave the old plugin deactivated for a week while you watch for problems, then delete it. Deactivated plugins still sit on the server, as we explain in why to delete inactive plugins.
When there’s no good replacement
Sometimes an old plugin does something no maintained plugin offers. Then the options are to keep it with care (test before every update, watch for security news) or to have it brought up to date or rebuilt as a small custom plugin. Tell us what it does and we’ll suggest the safest route, or do the whole switch for you.
Leave a Reply