Back to all posts
Process7 min read·November 1, 2026

How to Safely Decommission Old Business Software

TB
ThynkBlox Team
Engineering

How do you decommission old business software safely?

Decommission old business software by confirming that nobody still depends on it, preserving the records you need, and shutting down access and services in a controlled order. Then cancel the associated contracts and verify what happened to every copy of its data. Treat retirement as a separate decision from migration: a working replacement is the starting point, while evidence that the old system can close safely is the finish line.

How is decommissioning different from migration?

Migration moves records and business work into the replacement. Decommissioning closes the remaining responsibilities attached to the old system.

Use separate acceptance criteria for each. Migration acceptance might confirm that orders, balances and attachments arrived correctly. Retirement acceptance should confirm that remaining users have somewhere to work, historical records are accessible, integrations have moved or stopped, and deletion has been checked.

If those migration checks remain unresolved, return to the data migration plan for replacing business software before authorising shutdown.

Give one person responsibility for coordinating retirement. Ask the owners of business processes, records, access and supplier contracts to approve their respective parts.

Who and what still depends on the old system?

Start with an inventory, then check it against actual use. Ask each department what it still opens the old software to do, including occasional tasks such as resolving an old dispute or preparing a periodic report.

Review these dependencies:

  • People: employees, external partners, administrators and occasional users.
  • Connections: incoming and outgoing integrations, scheduled imports, exports and notifications.
  • Reports: dashboards, saved queries, spreadsheet connections and recurring extracts.
  • Background work: queued transactions, scheduled tasks and failed items awaiting retry.
  • Shared services: storage, identity connections and credentials also used by the replacement.

Record an owner, a replacement or closure action, and a verification method for each dependency. Do not accept “probably unused” as a completed check.

For an integration, ask both sides to confirm the change. A successful replacement connection is useful evidence; also check that the old connection has stopped receiving or sending work.

What should the retirement checklist contain?

Use evidence-based completion criteria. “Export requested” and “supplier contacted” describe work in progress.

AreaAction before closureEvidence to keep
Remaining usersMove each remaining task or agree to stop itBusiness owner confirms the task works without the old system
IntegrationsRedirect or disable each connectionTest result and confirmation from the receiving owner
Historical recordsPreserve approved records with a usable access routeSuccessful retrieval by an authorised user
RetentionReview applicable obligations and deletion restrictionsApproved record schedule and documented exceptions
CredentialsRevoke access dedicated to the retired systemRevocation records and rejected access attempts
ContractsClose subscriptions and related servicesWritten cancellation and final billing confirmation
Data deletionRemove approved copies and resolve exceptionsDeletion evidence, verification results and remaining-copy register

Keep this record somewhere accessible after the old software closes.

How will people access historical records?

Design the archive around questions people need to answer. “Find an old invoice and its supporting attachment” is a better acceptance test than “open the export.”

Define which records to preserve, which fields explain them, who may access them and how access is approved. Include attachments, relevant history and enough context to interpret codes or relationships.

Test retrieval with a business user who did not create the archive. Ask them to locate a record, understand it and produce the required supporting material without opening the old application.

A raw database export should have an agreed reader, instructions and a tested retrieval process. If records need a specialist to interpret them, account for that dependency before ending support.

A read-only copy of the old application can be a temporary archive option. Give it an owner, restricted access, a support arrangement and an explicit exit condition. Record it as an ongoing service rather than a completed retirement.

What retention obligations should you resolve first?

Before deleting anything, ask the relevant records owner and qualified adviser to identify applicable legal, contractual and business requirements. Confirm whether any dispute, investigation or preservation instruction restricts deletion.

For each record category, document:

  • What must remain and why.
  • Who can access it.
  • What event permits a later deletion review.
  • Who approves deletion.
  • How exceptions will be tracked.

Avoid applying one blanket rule to every record. Separate records approved for deletion from those approved for continued retention, and document the reason for each decision.

Use the software data retention and deletion policy guide to structure that review. Confirm current requirements through the relevant official authority or your legal adviser.

Last reviewed: October 2026.

In what order should you shut the system down?

Choose the sequence around the dependencies you found. A practical starting order is:

  1. Confirm the replacement handles remaining business tasks. Include occasional work.
  2. Stop new work entering the old system. Redirect users, forms, imports and connected services.
  3. Resolve unfinished work. Reconcile queued, failed and partially completed transactions.
  4. Capture the final approved records. Check archive contents and retrieval.
  5. Run a controlled shutdown. Define what you will observe and what would justify reopening.
  6. Complete permanent closure. Revoke dedicated access, remove resources and finish deletion checks.

Choose an observation period that includes relevant business activity. A quiet interval is weak evidence if the task you need to observe has not occurred.

Before the controlled shutdown, define who can authorise recovery, which records would need reconciliation and when that recovery option ends. Keep any recovery copy under the approved retention decision.

Which credentials and permissions need revoking?

Inventory human accounts and machine access separately. Include administrator accounts, supplier access, service accounts, API keys, access tokens, certificates, database credentials and backup access.

For each credential, establish whether it belongs only to the old system or is shared. Move shared dependencies to separate credentials before revoking the old access.

Remove permissions granted by other services too. Check identity-provider access, storage permissions, integration authorisations and recovery routes.

Verify closure with an attempted sign-in or connection using the retired access. Record the rejection without retaining the secret itself. Confirm that the replacement still completes the affected task.

When should you cancel contracts and subscriptions?

Check contract terms early so notice requirements can inform the retirement plan. Coordinate the effective cancellation with final exports, archive testing and any support needed to finish closure.

List the main software subscription alongside hosting, storage, backup, support, integration services and licences purchased specifically for it. Identify shared services before cancelling anything.

Request written confirmation of cancellation, the effective end of service, final charges and the supplier's data-handling process. Clarify whether export access ends before deletion is complete.

Assign someone to check subsequent billing and resolve any remaining charge. A cancellation request alone should not close the contract item.

How do you verify data deletion?

Create a copy register before deletion. Include production data, replicas, test environments, exports, attachments, logs, backups and supplier-managed copies.

For each location, record the approved action, responsible owner and verification method. After deletion, inspect the relevant storage or account where possible and confirm that the old application cannot retrieve the records.

For supplier-managed data, request evidence covering the agreed scope. Ask what remains in backups or other retained copies, why it remains, who can access it and what will trigger its removal.

Keep unresolved copies visible. Where retention is required or immediate deletion is unavailable, record the exception, access restrictions and next review action. Mark deletion complete only for the scope the evidence supports.

What common mistakes should you avoid?

  • Equating replacement launch with retirement. Require separate closure evidence.
  • Deleting before testing the archive. Prove retrieval first.
  • Leaving read-only access open indefinitely. Assign ownership and an exit condition.
  • Revoking a shared credential without checking dependencies. Separate access first.
  • Cancelling support before final extraction. Coordinate the end of service with remaining work.
  • Accepting “data deleted” without scope. Identify which copies the statement covers.

Pause permanent closure if a critical task still depends on the old system, required records cannot be retrieved, or a deletion restriction remains unresolved.

What are the frequently asked questions?

Can we keep the old system as an archive?

Consider it only with explicit ownership, access controls, support costs and a later closure decision. Test whether a separate archive would meet the retrieval need.

Should we delete all backups immediately?

Use the approved retention and recovery decisions to determine their treatment. Document each remaining copy and its removal condition; do not assume application deletion covers backups.

Who should approve final retirement?

Ask accountable owners to approve business continuity, record access, access revocation, contract closure and data handling. Give the coordinator the evidence needed to record the final decision.

When is decommissioning complete?

When every checklist item has verified evidence or an explicitly owned continuing obligation. Remaining archives and retained copies should have named owners, access rules and future actions.


*Replacing software and planning its retirement? Start a conversation →*

Ready to build?

Let's turn these ideas into your next product.

Start your project