The cost of software tenant offboarding depends on how much data and connected access must be handled when an organization leaves. A safe process may include export, verification, retention decisions, access revocation, billing changes, and a record of what was completed.
Define the offboarding states
Separate requested, approved, export-ready, suspended, retained, deleted, and completed states. State who can initiate, approve, pause, and reverse each step and what customer communication is required.
Inventory tenant data
List records, files, reports, search indexes, caches, logs, backups, integrations, API keys, scheduled jobs, and vendor copies. The tenant isolation checklist helps identify where tenant scope must be enforced.
Price exports and verification
Budget for export formats, large files, relationships, timestamps, attachments, encryption, download access, expiration, checksums, and a customer verification step. An export that cannot be understood or confirmed is not a complete handoff.
Include access and billing work
Plan user suspension, sessions, service accounts, webhooks, integrations, subscriptions, invoices, credits, and provider access. Keep revocation separate from deletion so a customer can confirm the handoff before irreversible work occurs.
The customer data deletion checklist and data retention checklist cover the policy and evidence layers.
Account for backups and vendors
Document what remains in backups, how long it remains, which vendor owns deletion, and how restoration would affect a completed offboarding. Include queues, analytics, support tools, and file storage in the review.
Plan support and audit evidence
Ongoing cost includes exception handling, customer questions, access reviews, provider changes, tests, documentation, and a durable completion record. Measure offboarding time, failed exports, reopened tenants, and unresolved dependencies.
Tenant exits still require manual detective work? Ask Vertinus to scope offboarding by data, access, and evidence.