A vendor offboarding checklist template is a step-by-step list for ending a supplier relationship cleanly. It makes sure access is removed, your data comes back or is destroyed, final invoices are settled and the contract is formally closed.
It is the exit plan you run every time a supplier contract ends, whether you are switching tools, consolidating suppliers or terminating for poor performance. Each task has an owner, a due date and a place to store evidence that it was done.
Procurement usually owns the checklist, but most tasks sit with other teams: IT removes access, the privacy lead confirms data deletion, AP pays the last invoice and legal closes the contract. A shared checklist stops each team assuming another has done its part.
The risks of a sloppy vendor exit are quiet ones: an API key that still works, customer data sitting on a former supplier's servers, or an auto-renewal invoice that arrives six months later.
Every account, key, VPN and building pass the vendor holds, revoked and logged.
What data comes back, in what format, and written proof the rest is deleted.
Last invoices matched, credits claimed, recurring payments stopped.
Notice served on time, surviving obligations noted, contract marked closed.
Your equipment, licences and materials returned, and theirs sent back.
Documentation, configurations and open issues handed to the new owner.
Ready to use in Excel, Google Sheets and PDF. Fill it in, save it, reuse it.
Confirm the exit date, the replacement and who owns each task. Check the notice period in the contract.
Serve written notice by the contract's deadline and request the data, assets and documents you need back.
Move the work to the new supplier or team while the old vendor is still under contract.
On exit day, revoke access, stop payments and collect assets. Get deletion confirmed in writing.
Pay the final invoice, archive the records, review the vendor and mark the contract closed.
Start with six lines: access removed, data returned, final invoice paid, contract closed, assets back, handover done. Add owners and dates once you have run it once.
Run the full checklist for any vendor that held your data, systems access or physical assets. For a low-risk supplier, such as a one-off print job, the final invoice and contract checks may be all you need. The download adds owner, due date and evidence columns to every line.
Store proof for every check: a screenshot of disabled accounts, the deletion certificate and the vendor's notice acknowledgement.
Most vendor exits fail on timing: notice served a week too late, or access removed before the data came back. Set the exit date once in the tracker and every deadline moves with it. The sample shows a 60-day exit from an analytics tool.
| Task | Area | Owner | Days before exit | Due | Status |
|---|---|---|---|---|---|
| Serve non-renewal notice | Contract | Procurement | 60 | 02 Oct 2026 | Done |
| Request full data export | Data | Data lead | 30 | 01 Nov 2026 | Done |
| Move dashboards to new tool | Knowledge | Analytics team | 14 | 17 Nov 2026 | In progress |
| Revoke SSO and API keys | Access | IT security | 0 | 01 Dec 2026 | Planned |
| Receive deletion certificate | Data | Privacy lead | -14 | 15 Dec 2026 | Planned |
| Pay final invoice and close PO | Invoices | AP | -30 | 31 Dec 2026 | Planned |
Illustrative exit from Orbit Analytics, exit date 01 Dec 2026. Negative days fall after the exit date.
Works in Excel and Google Sheets. Put the exit date in cell B1 of a Settings tab.
| Col | Header | Entry or formula | What it does |
|---|---|---|---|
| A | Task | Text | One action per row |
| B | Area | Drop-down: Access, Data, Invoices, Contract, Assets, Knowledge | Groups tasks for reporting |
| C | Owner | Name or team | One owner, never a shared inbox |
| D | Days before exit | Number, negative if after exit | Sets the deadline |
| E | Due | =Settings!$B$1-D2 | Moves if the exit date changes |
| F | Status | Drop-down: Planned, In progress, Done | Updated by the owner |
| G | Overdue | =IF(AND(F2<>"Done", | Flags late tasks |
| H | Evidence | Link | Screenshot, certificate or email |
| I | Progress | =COUNTIF(F:F, | Share of tasks complete, in one cell |
Check the contract and any data processing agreement for the return and deletion terms before you write to the vendor. Ask specifically about backups and subprocessors, since those are the copies most often forgotten. Keep the deletion certificate with the contract record.
| Data type | Ask for | Proof to keep |
|---|---|---|
| Customer or employee personal data | Export, then deletion including backups | Signed deletion certificate with date |
| Business records and reports | Full export in CSV or native format | File list and checksum or row counts |
| Configurations and integrations | Settings export and documentation | Handover document signed by the new owner |
| Credentials you shared with the vendor | Nothing back: rotate them yourself | Change log showing the new keys |
| Data held by subprocessors | Vendor's written confirmation it is deleted | Included in the deletion certificate |
Subject: Data return and deletion for [Contract name], ending [Exit date] Hi [Vendor contact], As confirmed in our notice dated [Notice date], our agreement ends on [Exit date]. Before that date, please: 1. Export all [Company] data to [Format] and share it via [Secure method] by [Export date]. 2. After we confirm the export is complete, delete all remaining copies, including backups and data held by your subprocessors. 3. Send a signed certificate of deletion stating the date and method by [Certificate date]. Please confirm receipt of this request and name the person responsible on your side. Thanks, [Your name] [Title], [Company]
The final invoice is where vendors most often overcharge, usually by billing a full period after the exit date or missing a pro-rata credit. Check it against the contract before AP pays. Contract closure matters just as much, because a missed notice date can renew the whole agreement; see how auto-renewing contracts catch teams out.
Illustrative figures for Orbit Analytics. Pro-rata credit = annual fee x unused days / 365. Refunds apply only if the contract allows them.
| Field | What to enter | Example |
|---|---|---|
| Contract | Name and reference from the contract register | Orbit Analytics MSA, C-0412 |
| End date and reason | Date the contract ends and why | 01 Dec 2026, replaced by an existing tool |
| Notice served | Date and method, with the vendor's acknowledgement | 02 Oct 2026, email and portal, acknowledged 03 Oct |
| Surviving obligations | Clauses that continue after the end | Confidentiality 3 years, audit rights 1 year |
| Final amount paid or credited | Net figure after credits | Credit of 8,480.55 received |
| Closed by | Name and date | Priya Shah, 05 Jan 2027 |
Keep the notice factual: the contract, the end date, the clause you rely on and what you need from the vendor before exit. Don't argue the reasons for leaving in the notice itself. If you are terminating for cause rather than letting the contract lapse, have counsel review the wording first.
[Date] [Vendor legal name] [Vendor address] Re: Notice of non-renewal, [Contract name and reference] In line with clause [Clause number] of the agreement dated [Agreement date], we give notice that [Company] will not renew the agreement. Services will end on [Exit date]. Before that date, please: - Return all [Company] data and materials as set out in our separate request - Confirm the final invoice amount, including any credits due - Name a contact to manage the handover Please acknowledge this notice in writing by [Reply date]. Yours sincerely, [Name] [Title], [Company]
Most exits start too late. Spendflo tracks renewal and notice dates on every contract.
See how it worksThe contract reaches its end date and you choose not to renew. Serve notice before the deadline.
A replacement is chosen. Overlap the two for long enough to move data and users.
The vendor breached the contract. Follow the contract's process and involve legal early.
Two tools or suppliers do the same job and one is being retired.
The vendor is acquired or fails a risk review, and you decide to leave.
| Onboarding step | Offboarding step |
|---|---|
| Risk and security review | Confirm data deleted and access revoked |
| Contract and DPA signed | Notice served, contract closed, surviving clauses noted |
| Vendor master record and bank details | Vendor set to inactive, payments stopped |
| Accounts and access granted | Accounts and keys revoked |
| Kick-off and documentation | Handover and exit review |
A clear supplier onboarding process records what access and data each vendor received, which is exactly the list you need when they leave.
Notice periods of 30-90 days are common, so begin planning a full quarter before the end date.
List every login, key and integration from the onboarding record before exit day.
Pull your data while the vendor's systems are still open to you.
Shared tasks between IT, AP and legal are the ones nobody finishes.
Record why the vendor left, so the next buyer sees it before re-engaging them.
Without a signed certificate you have no proof your data is gone.
Card subscriptions often outlive the contract because AP never saw them.
Revoking logins before export can lock you out of your own records.
An active vendor record lets new POs and invoices slip through after exit.
Read the contract's term and notice clause, then put the exit date in the tracker.
Send the exit notice and the data return request on the same day.
Move users, data and documentation to the new owner while the vendor is still contracted.
Revoke access, collect the deletion certificate, settle the final invoice and mark the contract closed.
Northwind Logistics serves non-renewal notice to Orbit Analytics on 02 Oct, 60 days before the 01 Dec exit. Data comes back on 01 Nov, SSO and API keys are revoked on exit day, and the deletion certificate arrives on 15 Dec. AP disputes a 4,200.00 December invoice and receives a pro-rata credit. All figures are illustrative.
Every part on this page, in Excel, Google Sheets and PDF, with the examples filled in.
Focus on SSO, API keys, integrations and data export. Read more on SaaS access control.
Focus on knowledge transfer, returned equipment and intellectual property in work they produced.
Focus on open POs, returns, final deliveries and stock held at the supplier's site.
Best for tracking evidence and deadlines.
Best when IT, AP and legal all update one file.
The 24-point checklist, ready to print.
Spendflo has handled 15,000+ agreements, with renewal tracking that flags notice dates early.
See contract trackingA good vendor offboarding checklist removes access, recovers your data, settles the final invoice and closes the contract in the right order. Exits go smoothest when renewal and notice dates are tracked from the day the contract is signed.
Twenty-four checks across access, data, invoices, contract, assets and handover.
Open the checklist →2Export first, then get deletion confirmed in writing.
Open data return →3Check the final invoice, claim credits and stop recurring payments.
Open the close-out →Quick answers to what people ask most about the vendor offboarding checklist template.
A vendor exit checklist covers six areas: access removal, data return and destruction, final invoices, contract closure, assets and knowledge transfer. Each step needs an owner, a deadline and evidence that it was done. Download the template for all 24 checks with an owner column.
You decide the exit date, serve notice, transition the work, cut off access and payments, then close out the contract and records. Running it in that order means you recover your data before access ends. Download the exit tracker to plan each date back from the exit.
It is a list of every task needed to end a relationship cleanly, so nothing is forgotten when a vendor or employee leaves. For vendors it focuses on access, data, payments and the contract. You can download a vendor version free on this page.
Onboarding usually runs through a risk and security review, contract and DPA signature, vendor master and bank details, account set-up and a kick-off. Offboarding reverses those steps when the relationship ends. Download this checklist to pair with your onboarding record.
You can download it free on this page in Excel, Google Sheets or PDF. It includes the 24-point checklist, an exit tracker, a data return request and an exit notice.
Vendor management
Purchase orders
Contracts
Sourcing and RFx
Budgets and business cases
Procurement
Accounts payable
Purchasing
Software buying
Supply chain
Spendflo tracks contracts, renewals and supplier onboarding in one place, so you know what each vendor holds and when to give notice.
Enter your work email and we'll unlock every format.
Didn't start, or need another format? Pick one below.
Google Sheets: upload the file to Google Drive, then open it with Google Sheets.
