Plan an exit that preserves usable, permitted records

Identify the permissions that survive

List the categories involved in exit: buyer-submitted information, delivered model outputs, documentation, historical revisions and any vendor-owned software. Ask what the agreement permits the buyer to retain, transfer or continue using after the term. These are different questions. Permission to archive an old report does not necessarily authorize generating new outputs, redistributing the report or transferring the supplier's methodology to a replacement provider.

WIPO's licensing checklist explicitly raises survival and termination questions. It does not grant a universal right to an export or to continued use. Have qualified reviewers assess the actual agreement, third-party restrictions and applicable requirements. Record the resulting scope in the exit plan so engineering does not discover at the final transfer that a technically available dataset cannot be used as intended.

• Separate archive retention, transfer and continued operational use.

Specify an interpretable export package

Define the export's record population, time range, identifiers, units, timestamps, revisions and accompanying documentation. Include a manifest that states expected files or records and the schema needed to read them. Ask how deleted, superseded and unavailable observations are represented. A set of current values can be adequate for one task but insufficient for reconstructing what was published at an earlier decision time.

NIST SP 800-146 recommends planning asset return and migration during procurement. For model licensing, translate that into a small rehearsal while both parties can still fix omissions. The buyer's receiving team should load a representative export independently of the supplier's viewer. An export that can only be interpreted through an expiring portal has not yet demonstrated the portability the plan assumes.

• Test interpretation outside the supplier's application before access expires.

Reconcile a fictional final delivery

In a hypothetical fictional exit, the agreed archive manifest lists 240 daily files and their checksums. The receiving team obtains 238 files, all matching their listed checksums. Two files are absent, so file completeness is 238 divided by 240, or 99.17% rounded. Successful checksum verification of the received files does not make the missing dates disappear or prove that individual records are economically correct.

The buyer keeps the export task open. The fictional supplier then delivers the two missing files, and the team confirms 240 of 240 expected files before checking row counts and identifiers. One delivered file contains a validly transferred but undocumented revision code. That semantic issue requires clarification even though file completeness now reaches 100%. Transfer integrity, completeness and interpretability are separate acceptance questions.

• Check transfer integrity, completeness and meaning independently.

Sequence the transition around verified receipt

Agree a timeline for export generation, transfer, verification, correction and access closure. Identify any overlap period and its commercial terms before relying on it. The buyer should know what happens if the final export fails acceptance near the termination date. Do not assume the supplier must provide free continued access; any bridge arrangement needs its own authorized scope and documented agreement.

Freeze the relevant export population at a defined cutoff, then identify how later corrections are delivered if they are included. Without that boundary, the buyer can repeatedly reconcile one version while the supplier changes another. Assign a person who can confirm the receiving system is ready and a different checkpoint for ending old credentials. Closing access before verification can turn a correctable omission into an urgent dispute.

• Define the export cutoff and handle later corrections explicitly.

Keep preservation and disposal decisions compatible

Inventory buyer and supplier copies before requesting deletion. Separate records that may be removed from records subject to an applicable retention requirement, legal hold or agreed archival permission. The responsible legal and records teams should determine those obligations. Procurement should not issue a blanket instruction to delete everything when the buyer still needs authorized evidence of prior decisions or unresolved commercial matters.

NIST SP 800-88 Revision 2 provides guidance on media sanitization. Use it to inform questions about the supplier's disposal method and evidence, not to assume that an account closure sanitizes all storage. Ask how active data, support attachments, replicas and backups are addressed. Where delayed backup expiry or another authorized exception applies, record its scope, access restrictions and expected completion evidence.

• Resolve preservation requirements before authorizing irreversible disposal.

Close credentials and dependent workflows

List human accounts, service keys, scheduled requests, support access and any applications that consume the old feed. Revoke or replace them through the buyer's authorized process and confirm the result. Stopping payment does not prove that credentials are disabled, and disabling credentials does not prove that contractual commitments are closed. Treat those technical and commercial tasks as separate items with evidence.

Check downstream displays and archived reports for stale links or misleading current labels after the service ends. Where continued display is permitted, show the appropriate historical context. Where it is not permitted, follow the reviewed removal plan. The replacement workflow should identify its own source and approval rather than silently reusing the old supplier's label for a different analytical product.

• Verify access closure and downstream labeling separately from final billing.

Issue a bounded exit receipt

The final receipt should identify the export manifest, checks performed, unresolved exceptions, retained permissions, revoked access and outstanding invoices or disposal confirmations. Store it with the procurement record in a location the buyer can access without the terminated service. A remaining issue should have an owner and due date rather than being hidden under a general statement that the contract is finished.

In the fictional example, completion waits for the revision-code explanation and the agreed closure evidence, not merely the final file count. A failed portability rehearsal is a procurement finding, not proof of a universal legal remedy. All scenario details are invented. The aim is a verifiable transition that respects the actual agreement and applicable obligations without claiming ownership of material the buyer never licensed.

• Close the exit only when remaining interpretation and access issues are accounted for.

Source notes

1. WIPO GREEN: Licensing Checklist, survival and termination
2. NIST SP 800-146: Cloud Computing Synopsis and Recommendations, migration
3. NIST SP 800-88 Revision 2: Guidelines for Media Sanitization