Decommissioning Your Old CRM: Stop Paying After Migration
You migrated months ago. The new CRM is live. Yet the old tenancy still bills every month "just in case", while half-alive integrations and orphaned access create real Rand burn and POPIA risk.
A 4–6 week decommission plan recovers that spend and locks archival, licence cancellation, and integration shutdown properly.
Sound Familiar?
These are the exact issues our clients faced when the old CRM outlived the migration:
- The new CRM has been live for months, yet the old tenancy still bills every month "just in case"
- Finance cannot say which seats, add-ons, or ISV connections are still active on the retired system
- Zapier, Make, or middleware still holds API keys into the old CRM, so data can leak or write back quietly
- Nobody owns licence cancellation, archival sign-off, or the POPIA handoff for historical personal information
- Dual-system habits linger: a few people still log into the old CRM, and leadership treats it as free insurance
Salesforce's 2026 price book raised list rates on core clouds (Sales and Service Enterprise near nine percent in market reports), so every month you keep leftover seats "just in case" costs more than the year you migrated. Licence cancellation is not optional housekeeping; it is spend recovery against a rising baseline.
What Structured CRM End of Life Actually Does
Inventory → archive → revoke → cancel. Dual-system spend stops on a date you can defend to the board.
Map the Leftover Estate
Seats, renewals, API keys, iPaaS recipes, and who still logs into the old CRM
Archive for Retrieval
Cold-store records and attachments with labels so history survives licence cancellation
Shut Integrations
Revoke keys, pause recipes, confirm no write-back or silent sync into the retired tenancy
Cancel and Sign Off
Licence notice executed, access dead, finance and compliance get the evidence pack
Everything You Need for Clean System Retirement
Licence and Contract Wind-Down
Seat inventory, renewal dates, notice periods, and a cancellation calendar so you stop paying for a system you no longer run.
Archival Handoff
Cold-store exports of contacts, deals, activity, and attachments with retention labels so history stays retrievable after the tenancy dies.
Integration Shutdown
Every API key, webhook, iPaaS recipe, and connected app is listed, revoked, and verified silent against the old CRM.
Access and Identity Kill
SSO links, user seats, admin accounts, and partner logins are revoked on a named date with evidence for compliance review.
POPIA Retrieval Path
Archived personal information stays searchable for DSARs and retention duties, without keeping a live, half-managed CRM online.
Spend Recovery Dashboard
Monthly licence burn, soft dual-system cost, and target savings so the CFO sees the decommission pay for itself in weeks.
Platforms We Decommission After Migration
From R49K/Month Leftover Seats to Zero in Five Weeks
How a 28-person professional services firm in Johannesburg stopped paying for Salesforce eight months after cutover and locked a clean archival handoff.
The Lingering Old CRM
- New HubSpot live for eight months; Salesforce still billed 18 Enterprise seats
- About R49,000 every month in leftover licences, treated as cheap insurance
- Eleven Zapier and middleware connections still authenticated into the old tenancy
- No named owner for licence cancellation, archival sign-off, or access revocation
- Finance could not prove which personal records would survive if the tenancy vanished
The Decommission Plan
- Cold archive of four years of contacts, deals, and activity with retrieval labels
- All eleven integrations revoked and verified silent against Salesforce
- Seats cancelled on contract notice; SSO and admin paths closed the same week
- Sign-off pack for finance, IT, and compliance with spend recovered and access dead
- Team stopped dual-system habit; HubSpot became the only live CRM
Before vs After Decommission
How It Works
From first conversation to cancelled licences and signed archival handoff in 4–6 weeks.
Inventory the Old Stack
Seats, renewals, integrations, archives already taken, and who still has login rights. We quantify the monthly burn.
Free Scoping Call
30-minute call to set the 4–6 week decommission plan, archival scope, and licence cancellation milestones.
Archive, Revoke, Verify
We lock cold archives, revoke API keys and seats, cancel licences on notice, and prove the old CRM is unreachable.
Sign-Off Pack
Evidence for finance, IT, and compliance: what was archived, what was shut, and what spend recovered.
Frequently Asked Questions
How is CRM decommission different from a migration rollback plan?
A rollback plan is contingency during cutover if go-live fails and you need the old CRM warm. Decommission is structured retirement after a successful migration: archival handoff, licence cancellation, integration shutdown, and stopping dual-system spend. Keeping the old CRM "just in case" for months after validation is not a rollback plan; it is unmanaged cost and compliance risk.
How long should we keep the old CRM after a successful migration?
Industry guidance typically keeps the old system available for a short audit window after cutover, often around 60 days, while validation closes. Planned parallel running is usually 4–12 weeks. When nobody owns end-of-life, dual-CRM periods commonly stretch to 14–20 months and the cost scales almost linearly with that overlap.
What does leftover CRM licensing actually cost in Rand?
Salesforce Sales Cloud Enterprise lists near $165 per user per month on the 2026 price book (about R2,720 at R16.50 to the dollar). HubSpot Sales Hub Enterprise lists near $150 (about R2,480). Dynamics 365 Sales Enterprise lists near $105 (about R1,730). Eighteen leftover Salesforce Enterprise seats alone are roughly R49,000 every month until you cancel.
What POPIA risks come from an orphaned old CRM?
Under POPIA you remain responsible for personal information even if the system is rarely used. Unmanaged access, stale API keys, and unsupported platforms holding customer data weaken security safeguards and make DSARs harder. Decommissioning should archive what you must retain, destroy or de-identify what you must not keep, and revoke every path into the retired tenancy.
What does a structured CRM decommission cover?
A typical 4–6 week programme inventories seats and renewals, completes cold archival with retrieval paths, shuts integrations and API credentials, revokes user and admin access, executes licence cancellation against contract notice, and delivers a sign-off pack for finance and compliance. It is system retirement, not another migration.
How much does CRM decommission planning and delivery cost?
Focused decommission programmes for mid-market CRM estates typically land between R25,000 and R65,000 depending on integration count and archival depth. Against R49,000 a month in leftover Enterprise seats, most clients recover the fee in the first cancelled billing cycle.
Stop Paying for a System You Already Left
If the migration succeeded months ago and the old CRM is still on the invoice, you are funding risk and habit, not insurance.
Tell us which platforms you left and which you run now, how many seats still bill, and which integrations might still touch the old tenancy. We will map a 4–6 week decommission plan with archival, licence cancellation, and shutdown milestones.