Software Tenant Offboarding Checklist

Tenant offboarding should be a controlled transition, not a single delete button. The checklist needs to protect the customer’s data, revoke access, close connected work, and leave evidence that the right steps happened in the right order.

Start with an approved request

Capture the tenant, requester, reason, effective date, approver, retention requirements, and support owner. Separate a planned departure from an incident, suspension, unpaid account, or legal hold.

Inventory records and dependencies

List users, roles, files, reports, exports, API keys, webhooks, queues, scheduled jobs, integrations, caches, search indexes, logs, backups, billing records, and vendor copies.

Export before destructive work

Generate a usable export, protect the download, set an expiration, verify relationships and attachments, and obtain the customer’s confirmation where required. Keep the export event and checksum or equivalent evidence.

Revoke access in layers

Suspend users, invalidate sessions, disable service accounts, revoke tokens, remove integrations, stop scheduled jobs, and update provider access. The tenant isolation checklist helps identify scopes that are easy to miss.

Handle retention and billing

Apply retention, backup, legal hold, and deletion rules deliberately. Stop future billing, resolve open invoices or credits, and record which financial or compliance records must remain.

Confirm completion and monitor

Send a clear completion summary, preserve audit evidence, and monitor for new logins, queued work, failed deletions, unexpected exports, or vendor callbacks. Review the process after each system or policy change.