How Long Should You Keep an Unused Plugin Licence?

Keep an unused licence only through a named recovery, migration, or reuse window. Assign an owner and expiry. Cancel when evidence no longer justifies carrying it.

How long should you keep an unused plugin licence?

Use the shortest period covering a specific operational need. Review before the next cancellation or renewal deadline. Avoid indefinite “just in case” retention.

Define what unused means

The plugin may be inactive, deleted, replaced, or installed without licence activation. Those states carry different risks. Record the exact condition.

Separate software from commercial entitlement

Plugin files and a vendor entitlement are different assets. Cancelling updates may not remove installed code. Vendor terms define commercial access.

The GPL does not define vendor services

WordPress plugins commonly use GPL-compatible software licences. The Plugin Handbook explains software licensing. Support, updates, downloads, and hosted services can have separate terms.

Inventory the retained entitlement

Record product, plan, account, owner, billing, renewal, expiry, and site allowance. Add connected sites and support access. Preserve authoritative vendor links.

Inventory the retained plugin state

Record installed version, activation status, settings, data, files, and dependencies. Note remaining content references. Licence value depends on recovery needs.

Keep it during a proven rollback window

A recent replacement may still fail on rare workflows. Retained download and support access can shorten recovery. Set a measurable observation gate.

Keep it during incomplete migration

Old data, content, or exports may still need the source plugin. Preserve compatible packages and documentation. Finish migration before cancelling access.

Keep it during contractual retention

Client or organisational agreements may require ongoing support capability. Verify the actual obligation. Assign cost and renewal approval accordingly.

Keep it for scheduled near-term reuse

A documented project may need the same entitlement soon. Name the site and decision date. Compare retention against purchasing later.

Keep it while a service remains necessary

The licence may cover hosted APIs, templates, storage, or account access. Installed code can depend on them. Confirm termination consequences.

Keep it while final support remains valuable

A migration issue may need vendor-specific diagnosis. Schedule testing within useful support coverage. Prepare reproducible evidence before contacting support.

Cancel when no site needs entitlement

Verify production, staging, development, archived, and client environments. Deactivate obsolete connections where appropriate. Preserve the reconciliation record.

Cancel when migration is proven complete

Validate data, content, integrations, jobs, permissions, and rare workflows. Retire old callbacks and credentials. Close the rollback period deliberately.

Cancel when planned reuse lacks ownership

An imagined future project has no present value evidence. Require a sponsor, scope, date, and budget. Otherwise stop carrying overhead.

Cancel when the product is no longer suitable

Unsupported, insecure, incompatible, or strategically rejected software should not become a fallback. Preserve required data. Remove the dependency safely.

Cancel when a replacement owns the contract

Confirm the new owner covers every mandatory behaviour. Update runbooks and training. Keeping both entitlements can hide unresolved migration work.

Review what cancellation changes

• Automatic renewal may stop immediately.
• Paid time may continue until expiry.
• Future downloads may become unavailable.
• Automatic updates may stop.
• Support ticket access may stop.
• Cloud services may stop.
• Account-stored templates may become inaccessible.
• Connected sites may remain recorded.
• Installed code may continue running.
• Reactivation rights may change.
• Renewal pricing may change later.
• Refund rights may have separate deadlines.

Vendor behaviour is not universal

WooCommerce documents that cancellation stops auto-renewal while access continues until expiry. Other products differ. Read the current terms for your purchase.

Expired entitlement may affect updates and support

WooCommerce states active subscriptions enable product updates and support. Installed extensions can continue without activation there. Never generalise that behaviour to every vendor.

Lifetime and recurring licences need different decisions

A perpetual entitlement may have no renewal cost. It still creates account and inventory work. Recurring access adds a dated payment decision.

Do not confuse cancellation with deactivation

Vendor portals and plugin dashboards may expose separate actions. Deactivation can free a site allowance. Cancellation can change future billing.

Do not confuse expiry with deletion

Expired commercial access does not necessarily delete plugin files or data. Deleting the plugin can trigger cleanup. Test product-specific behaviour.

Preserve the final authentic package

Keep the exact authorised archive needed for recovery. Record version, source, and checksum. Store it outside the live plugin directory.

Preserve configuration and export evidence

Export supported settings and retained data before access ends. Redact secrets from review copies. Prove imports on staging.

Preserve invoices and entitlement terms

Keep purchase date, plan, scope, owner, and applicable terms. These records support later recovery. Restrict billing data appropriately.

Preserve account recovery

Organisation-controlled email and multifactor recovery reduce lockout. Remove departed staff access. Do not retain shared personal accounts.

Calculate the carrying cost

Include renewal, administration, access control, review, and accounting work. Add site-limit opportunity cost. Compare against one defined retained benefit.

Calculate the reacquisition cost

Future pricing, product availability, onboarding, and configuration may differ. Do not invent a discount. Use current vendor evidence.

Calculate the recovery value

Estimate consequences if replacement fails during the observation window. Include vendor help and download access. Timebox that value.

Use a retention decision record

• Name the exact unused state.
• Name the retained operational need.
• Name every covered site.
• Name the commercial account owner.
• Record current term and renewal date.
• Record cancellation notice requirements.
• Record access lost after expiry.
• Record saved package and checksum.
• Record data and settings exports.
• Record replacement observation evidence.
• Assign a review owner.
• Set an automatic expiry date.

Review before auto-renewal processing

Allow enough time for evidence and approval. Confirm billing date in the vendor portal. Do not rely on memory or inbox search.

Review after migration milestones

Reconsider retention after cutover, observation, data reconciliation, and source retirement. Each milestone can remove one justification. Close promptly.

Review after ownership changes

Client handoff or business transfer can change responsibility. Decide transfer, sharing, or cancellation under vendor terms. Update account access.

Review after vendor changes

Acquisition, pricing, support, or policy changes can alter retained value. Recheck official terms. Preserve previous decision evidence.

Avoid zombie renewals

Unowned charges can recur after responsible staff leave. Centralise renewal visibility. Require explicit approval for every unused entitlement.

Avoid premature cancellation

Removing support during a risky migration can increase total cost. Keep a deliberate overlap when evidence supports it. End overlap after proof.

Avoid keeping live code for licence value

An entitlement can remain while unnecessary plugin code is removed. Inactive code still needs security consideration. Separate operational decisions.

Avoid deleting evidence after cancellation

Retain authorised financial, contract, and migration records appropriately. Delete secrets and unnecessary personal data. Follow responsible retention policy.

Document the exit

Record cancellation, effective expiry, removed activations, retained artefacts, and replacement owner. Close old reminders. Update the plugin inventory.

Complete the retained-value review

• Identify the exact feature formerly used.
• Identify why active use stopped.
• Confirm whether the need could return.
• Name the project requiring possible reuse.
• Name the person sponsoring that project.
• Set the project’s funding decision date.
• Compare current alternatives before retaining access.
• Check whether stored templates remain valuable.
• Check whether account downloads remain unique.
• Check whether vendor documentation requires login.
• Check whether support covers migration questions.
• Reject vague convenience as sufficient value.

Complete the recovery review

• List failures that could require rollback.
• Estimate each failure’s operational consequence.
• Verify the old plugin still supports current state.
• Verify the saved package installs cleanly.
• Verify settings and data can be restored.
• Verify external services would accept reconnection.
• Verify old credentials remain available securely.
• Verify the recovery runbook still works.
• Test recovery inside an isolated environment.
• Record remaining rollback limitations.
• Set the observation gate ending recovery value.
• Remove recovery justification after that gate.

Complete the commercial review

• Confirm the account holding the entitlement.
• Confirm the legal purchaser and billing owner.
• Confirm renewal currency and applicable taxes.
• Confirm auto-renewal status in the portal.
• Confirm cancellation and notice deadlines.
• Confirm access available after cancellation.
• Confirm access available after term expiry.
• Confirm future renewal or repurchase options.
• Confirm whether grandfathered terms would disappear.
• Confirm whether unused activations can be reassigned.
• Confirm whether transfer is permitted.
• Save current terms with the decision.

Complete the risk review

• Check vendor ownership and maintenance status.
• Check current security advisories and patches.
• Check WordPress and PHP compatibility.
• Check remote service continuity.
• Check account recovery and multifactor access.
• Check exposed keys across former administrators.
• Check connected sites for unknown usage.
• Check whether inactive code remains installed.
• Check whether cancellation affects critical updates.
• Check whether retained data has privacy duties.
• Check whether accounting records require retention.
• Document accepted risks and their expiry.

Complete the cancellation review

• Export required settings before account changes.
• Export retained data through supported tools.
• Download authorised final packages and documentation.
• Deactivate obsolete site connections where appropriate.
• Remove old vendor callbacks and webhooks.
• Revoke obsolete API keys and collaborators.
• Capture the final account and billing state.
• Cancel through the official vendor workflow.
• Save confirmation and effective expiry date.
• Remove obsolete renewal reminders.
• Update finance and software inventories.
• Schedule verification after access expires.

Complete the governance review

• Assign one accountable entitlement owner.
• Assign a backup owner for absence.
• Restrict account access to current staff.
• Record why retention was approved.
• Record the maximum retention period.
• Record evidence required for extension.
• Require explicit approval before renewal.
• Escalate renewal without a current owner.
• Review after any client handoff.
• Review after vendor policy changes.
• Prevent automatic indefinite exceptions.
• Archive the final closure decision.

Complete the site reconciliation

• Search production sites for installed plugin files.
• Search staging sites for active testing use.
• Search development sites for forgotten activations.
• Search multisite networks at network scope.
• Search vendor portals for recorded domains.
• Resolve renamed or migrated site identities.
• Remove activations belonging to deleted environments.
• Confirm client sites have independent entitlement.
• Investigate sites unknown to current owners.
• Record intentional dormant site assignments.
• Preserve evidence before changing portal state.
• Reconcile again after cancellation finishes.

Complete the retained-data review

• Identify plugin data still required operationally.
• Identify data retained only for compliance.
• Identify records safe to remove.
• Preserve exports in useful documented formats.
• Test exports outside the original plugin.
• Protect personal and financial information.
• Record retention periods and deletion owners.
• Remove vendor copies where appropriate.
• Verify backups follow the same decision.
• Document schemas needed for future interpretation.
• Disconnect data recovery from paid access where possible.
• Close retention after approved deletion completes.

Complete the final approval

• Present current cost and retained value evidence.
• Present recovery and migration status.
• Present security and vendor continuity risks.
• Present cancellation consequences and deadlines.
• Obtain accountable approval for retention or closure.
• Record the next action and owner.
• Notify finance before expected billing changes.
• Verify completion inside the vendor portal.

Keep this decision beside the software inventory. Future owners can then understand the entitlement history and final closure evidence.

Know the honest weak case

A short paid overlap can cost less than rebuilding lost recovery access. Approve the overlap explicitly. End it at a proven gate.

Use the unused-licence checklist

1. Define the exact unused state.
2. Separate code from entitlement.
3. Inventory sites, data, and services.
4. Identify one retained operational need.
5. Record term, expiry, and renewal.
6. Verify cancellation consequences.
7. Preserve authentic recovery packages.
8. Export configuration and retained data.
9. Calculate carrying and reacquisition costs.
10. Assign a decision owner.
11. Set a review and expiry date.
12. Cancel after the evidence gate passes.
13. Deactivate obsolete site connections.
14. Update access, reminders, and inventories.
15. Retain required exit evidence.

Frequently asked questions

The verdict

An unused licence needs a deadline, not nostalgia. Review WP Block Suite’s $299 lifetime licence.