Check notice deadlines, export access, migration assistance and data deletion before renewal, then build a practical exit timetable from your actual contract.

Direct answer: Find the applicable contract and identify the notice deadline, renewal commitment, service end date, export period and deletion arrangements separately. Test a permitted export before committing to another term, and obtain written clarification for anything that would prevent a safe exit. Do not cancel a critical service merely to avoid renewal if you cannot yet preserve the data and continue the work; negotiate an authorised transition instead.

The date money leaves your account may be later than the date on which you must decide. Equally, access to a download after cancellation is useful only if it includes the records, relationships and attachments your team needs.

My recommendation is to treat exit readiness as a renewal requirement even when you expect to stay. The exception is an urgent continuity decision where a short, explicitly agreed extension is safer than a rushed departure. That extension should buy specific preparation time, not postpone the same unanswered questions indefinitely.

Applies to: a small organisation reviewing a business software agreement. UK data-protection context is identified below; commercial rights depend on the actual contract and governing law. This is a practical review method, not legal advice on a particular agreement.

Build an exit record alongside the renewal decision

Use The renewal exit-terms review, an editorial method that connects contractual dates to the practical work of leaving. It keeps five records together: the agreement, the notice route, the usable export, the transition responsibilities and the final data disposition.

This follows a narrower question within the technology retrospective for small teams. You are not reviewing every aspect of the supplier. You are establishing whether the next commitment leaves your team able to stop using it responsibly.

Gather the signed order form, referenced terms, amendments, renewal correspondence and any data-processing agreement. Note which entity bought the service and which person is authorised to make contractual decisions.

Keep these documents in an approved location with access limited to relevant colleagues. Do not upload a confidential contract or customer export to an unapproved comparison or AI service merely to summarise it.

If documents conflict or the applicable version is unclear, record the uncertainty and seek written clarification. A public pricing page or a sales conversation is not evidence of your particular termination arrangement.

Identify the dates that actually control the decision

Read for the notice period and how notice must be delivered. Check whether the contract refers to calendar days, working days, receipt rather than sending, a named address or a particular account action. Do not assume an ordinary support request fulfils that requirement.

Then identify what happens at renewal: term length, minimum commitment, applicable charges and any conditions for reducing seats or changing service level. Payment frequency and commitment length are different questions.

Record the effective service end date separately from the last payment date. Ask what happens to ordinary users, administrators, integrations and exports at that point. A read-only period and continuing full service are not interchangeable.

Give each deadline an owner and a second person who can locate the evidence. A reminder on the original purchaser's private calendar is not enough for a team dependency.

Before sending any cancellation or deletion instruction, confirm authority, recovery arrangements and continuity. This review authorises investigation, not an irreversible action on a critical shared account.

Prove that an export supports the work you must retain

List the information needed after departure. Depending on the task, this may include records, files, attachments, dates, ownership, relationships, comments and a history of important decisions. Do not assume “export available” includes every one of them.

Use a synthetic or otherwise authorised sample first. Export it through the documented process for your account tier, then inspect it outside the source application. Check representative complex records as well as simple ones.

Success means a colleague can find the relevant information and interpret its connections using the proposed destination or archive. A file that exists but cannot preserve an essential relationship is not an adequate exit result.

Record exclusions explicitly. You might accept losing decorative formatting while requiring every customer attachment and original timestamp. That is a business decision to make before migration, not an unpleasant discovery after deletion.

If a supplier offers migration assistance, establish its scope, price, scheduling and acceptance criteria in writing. “Help available” does not establish who repairs missing fields or whether assistance can finish before access ends.

Keep return, retention and deletion distinct

Exporting information to your organisation does not prove that the supplier has deleted its copies. Nor should deletion happen before your authorised retention and recovery needs have been resolved.

For UK controller–processor arrangements, the ICO's guidance says the contract must address returning or deleting personal data at the controller's choice when the contract ends, and deletion of existing copies unless UK law requires storage. It also discusses safeguards where backup deletion is not immediate. See the ICO's end-of-contract provisions.

A controller determines the purposes and means of processing; a processor handles personal data on its behalf. Do not assume that description covers every role a software supplier performs. Ask the responsible data-protection professional to resolve unclear responsibilities.

The ICO marked this guidance as under review when checked on 11 September 2026. Requirements vary by country, sector and contract. Obtain qualified local advice for a specific dispute or uncertain retention obligation, rather than treating this checklist as a legal determination.

Ask the supplier what becomes inaccessible, what is retained, for how long, under what authority and who confirms completion. Keep the response with the exit record, not in a departed colleague's inbox.

Work backwards from a hypothetical renewal

Assume a hypothetical contract would renew for £960 at day zero. Its invented terms require notice thirty calendar days before renewal and provide fourteen days of export access after service ends. These are illustrative contract terms, not market norms or a description of any vendor.

If the review starts forty-five days before renewal, the time available before the notice deadline is 45 − 30 = 15 days. Waiting until the renewal week would miss that assumed decision window.

A sensible illustrative sequence is to test the export by day minus forty, reach the authorised decision by day minus thirty-five, and complete the specified notice process by day minus thirty-two. That gives two days before the assumed notice deadline, but the required margin depends on the actual delivery and acknowledgement rules.

Plan migration and verification before service ends. The fourteen-day post-service export window is contingency, not a reason to begin the first download after the team loses normal access.

Suppose an alternative arrangement costs an illustrative £520 and migration assistance costs £160. Against the £960 renewal, the simple difference is £960 − £520 − £160 = £280 of potential cash reduction, assuming comparable periods and no additional taxes, penalties or overlap charges.

If internal preparation takes six hours, that is six hours of team capacity, not automatically a further cash payment. Include it in the workload decision. Missing the notice requirement could change the cash comparison completely, so do not present £280 as an assured saving before the actual agreement is checked.

Resolve uncertainty before it becomes dependence

For each unanswered question, write down the consequence and who can supply evidence. For example, uncertainty about attachment export belongs with the technical owner; an ambiguous notice clause belongs with the commercial decision-maker and, where needed, a solicitor.

If an export test fails, preserve the source and document the missing item. Do not repeatedly cancel and restore the account to discover how termination behaves. Ask for a safe test environment or a written description of the actual transition.

A reasonable decision may be to renew while correcting an exit weakness. State why continuity outweighs the immediate saving, assign the corrective work and schedule its verification well before the next notice deadline.

Do not accept an unresolved inability to recover essential records as a permanent background inconvenience. It is a dependency the organisation must consciously own and address.

Complete the review before the notice deadline

  1. Today, identify the agreement owner and collect the applicable documents. Find the notice deadline before discussing replacement products.
  2. Within the next two working days, write a dated exit record covering notice, commitment, access, export and deletion. Mark unknowns rather than guessing.
  3. Schedule an authorised sample export this week and reserve time to inspect its completeness outside the supplier's system.
  4. Obtain written answers and make the renewal or transition decision with enough margin for the actual notice process.
  5. Stop cancellation if authority, essential data or continuity is unresolved. Seek an agreed extension or qualified advice; do not assume that simply withholding payment safely ends the contract.

Frequently asked questions

Does cancelling a payment also cancel the software contract?

Do not assume so. The payment mechanism and contractual notice process are separate matters, and stopping a charge may leave an obligation or interrupt access without completing a valid exit. Read the applicable agreement and follow the authorised route for your account. If the wording is disputed, get written clarification and qualified advice for the governing jurisdiction before acting. Preserve correspondence and payment records in the meantime. This is particularly important for a shared operational service where a sudden suspension would affect other people. A provider's express confirmation that a particular action ends the agreement is evidence worth retaining, not a rule to generalise.

Can a salesperson promise an easier exit than the written terms?

A reassuring conversation is not enough evidence for your operational plan. Ask for the specific proposed change in writing and have the person responsible for the agreement confirm how it becomes part of the applicable contract. Do not decide legal enforceability yourself from the job title of the person who made the promise. An export demonstration can establish a technical capability, while a contractual commitment addresses whether and when it will be provided to you. Keep both kinds of evidence. If the renewal decision depends on the promise and its status remains uncertain, escalate it before authorising another commitment.

Should we download all customer information during the review?

Not as the first step. Begin with a synthetic or otherwise authorised sample that can test formats, relationships and attachments without creating an unnecessary copy of the whole dataset. A full export may be necessary later, but plan its destination, permissions, protection and retention before starting. Confirm who is authorised to receive it and how you will reconcile changes made after the export. If sensitive or regulated information is involved, use the organisation's approved migration process and obtain specialist advice where required. A review designed to reduce supplier dependence should not create an uncontrolled archive on a personal laptop.

What if the vendor only offers a PDF export?

Decide whether a PDF supports the information you must retain. It may be adequate for reading a final report but unsuitable for continuing structured enquiry tracking, preserving linked records or importing information into another system. Test a representative export and ask a colleague to complete the required retrieval task outside the source application. If important functions are missing, ask about other documented formats or assistance available on your actual contract. Do not assume a conversion tool will reconstruct lost relationships correctly. Accept the limitation only when the authorised owner understands the consequence and the retained information still meets the task and applicable obligations.

Is a deletion certificate enough to finish the exit?

Treat it as one piece of evidence, not the entire exit process. Check that it identifies the relevant account or dataset, scope, date and any retained copies or exceptions. Also confirm that your organisation has the information it is authorised and required to keep, and that former integrations and access arrangements have been addressed. Do not demand immediate destruction of material subject to a legitimate retention requirement without qualified advice. The practical objective is a documented, understood disposition of data rather than a reassuring document title. If the certificate's meaning is unclear, ask the responsible supplier contact to explain its coverage in writing.

Should we stay with a supplier if migration would cost more than renewal?

Possibly, but compare the full decision rather than one invoice. Migration expense, internal effort and disruption can justify staying with a service that still meets the team's needs. Poor access to essential records, unacceptable permissions or a serious unresolved dependency may justify spending more to leave. Separate the immediate renewal choice from the work needed to improve future exit readiness. If you stay, give that work an owner and a date before the next notice deadline. Do not claim migration saves money when it does not; a defensible decision may instead buy better control, continuity or a more appropriate risk position.

Sources and verification

Twokq Tech

This article is practical guidance. Apply it in proportion to your tools, evidence, risks, and responsibilities.