Vendor offboarding is the controlled end of a vendor relationship: removing access, retrieving or deleting data, settling contractual obligations and updating records, so no data, access or liabilities are left behind.
What Vendor offboarding means
Offboarding is where many risks resurface. Accounts and API keys stay active, data sits in the vendor's backups, and sub-processors keep copies. The contract decides what you can demand, so the work starts at contracting, not at termination. Plan it when the contract is signed, and confirm the plan before the end date.
GDPR Article 28(3)(g) requires the processor to delete or return personal data at the end of the services. DORA Article 30(2)(d) requires access, recovery and return of data on termination, insolvency, resolution or discontinuation of the provider's business. NIST CSF 2.0 GV.SC-10 covers activities after a supplier relationship ends.
Keep a checklist per tier and keep the evidence: the deletion confirmation, the access removal record and the updated inventory or register entry. Check that integrations and single sign-on connections are removed on your side too, since they often outlive the contract.
What to check in vendor documents
- Return of data in the agreed format, and confirmation that it is complete.
- Written confirmation of deletion, including backups and sub-processors, with dates.
- Removal of user accounts, API keys, integrations and network access.
- Obligations that survive termination, such as confidentiality.
- Updates to the vendor inventory and the register of information.
Related terms
- Exit strategyAn exit strategy is a documented plan for ending a vendor relationship, planned or forced, and moving the service to another provider or in-house without unacceptable disruption, including data return, transition support and timelines.
- Data processing agreement (DPA)A data processing agreement (DPA) is the contract between a controller and a processor that sets the terms GDPR Article 28(3) requires for processing personal data on the controller's behalf, including instructions, security, sub-processors, deletion and audits.
- Register of informationThe register of information is the record DORA requires every financial entity to keep of all its contractual arrangements for ICT services, at entity, sub-consolidated and consolidated level, in the templates set by Implementing Regulation (EU) 2024/2956.
- GDPR Article 28GDPR Article 28 is the provision of Regulation (EU) 2016/679 that governs how a controller uses a processor: the processor must give sufficient guarantees, act only on documented instructions and be bound by a contract with set minimum terms.
Sources
- Regulation (EU) 2016/679 (GDPR)eur-lex.europa.eu/eli/reg/2016/679/oj
- Regulation (EU) 2022/2554 (DORA)eur-lex.europa.eu/eli/reg/2022/2554/oj
- NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0doi.org/10.6028/NIST.CSWP.29
Summarised for practitioners, not legal advice. Check the source text for your own obligations.