Removing a plugin can affect public pages, customer records, checkout, booking, access, or follow-up. Treat removal like an operational change, not just cleanup.

What this guide helps you do

• Decide whether to disable, hide, or remove a plugin.
• Find dependencies before taking action.
• Protect customer-facing pages and historical context.

Before you start

• Confirm the plugin is no longer needed.
• Check for active orders, bookings, memberships, registrations, or customers using it.
• Know which pages, campaigns, and automations link to the plugin.

Do it manually

1. Open Plugins and select the plugin.
2. Review active records, public pages, payments, access rules, and related customer activity.
3. Pause campaigns, journeys, or links that point to the plugin if needed.
4. Disable or hide the plugin first when you need a reversible step.
5. Remove only after confirming no active workflow depends on it.
6. Update navigation and pages that referenced it.

Ask Faster AI

• Audit this plugin before removal. List pages, records, customers, automations, and payments I should review.
• Prepare a safe retirement plan for this plugin with redirect and customer follow-up reminders.
• Tell me whether this plugin can be disabled first instead of removed.

Review before saving or publishing

• Keep historical customer context when possible.
• Do not remove a plugin with active paid access, bookings, or registrations without a migration plan.
• Preview public pages after disabling anything.

Common issues and fixes

• If a page breaks after disabling, restore the plugin or remove the page component and publish again.
• If customers lose access unexpectedly, review membership, order, or registration records.
• If links now 404, update navigation, campaigns, and redirects.

Use it in daily operations

• Prefer disable or hide for the first pass so the change can be reviewed.
• Schedule plugin cleanup after campaign windows, not during them.
• Document what replaced the retired workflow.

Team handoff

• Write down what changed, who owns the next review, and which page, customer record, campaign, or plugin record should be checked next.
• If the work affects customers, include the public URL, test result, and any unresolved placeholder media in the handoff note.
• When Faster AI helped prepare the change, ask it to summarize the draft and review checklist so a teammate can approve the work without retracing every click.

Placeholder media

• Screenshot placeholder: add an annotated screenshot of disable or remove an unused plugin with private customer, payment, and workspace details blurred.
• Video placeholder: add a short walkthrough that shows the manual path, the Faster AI prompt, and the review step before anything goes live.

Related help

• Choose the right plugin for a workflow
• Configure plugin settings
• Review plugin data in customer records