Build a dependency map
Content and data
Posts, metadata, taxonomies, custom tables, options and uploaded files.
Rendered output
Blocks, widgets, shortcodes, templates, feeds and structured data.
Automation
Cron tasks, emails, webhooks, imports, exports and external APIs.
Search footprint
Indexed URLs, canonicals, internal links, sitemaps and backlinks.
Acceptance tests
- All required content appears in the replacement.
- Important URLs remain stable or redirect once to a relevant page.
- Editors can complete common tasks without hidden legacy steps.
- Feeds, search, forms and scheduled jobs behave as expected.
- The old code can be removed without database errors.
- A rollback has been tested before production change.
Frequently asked questions
Should an abandoned plugin be replaced immediately?
Known active exploitation or an unpatched vulnerability raises urgency. Even then, preserve data and provide safe temporary containment or replacement rather than deleting blindly.