This retention timeline is part of exception handling records for AI agents. It is for customer platform consultants working on a plan consolidation or billing migration who want to know what disappears, when, and who decides.
The retention clock, record by record
Not every record ages the same way. Current state usually survives a consolidation; the history of how it changed often does not.
| Record type | Where it lives | Typical window | What happens at the end | Who approves keeping it |
|---|---|---|---|---|
| Billing change events | Billing platform, for example Stripe | Retrievable through the Events API for 30 days | Older events no longer returned; the subscription's current state remains | Finance or billing owner |
| Identity events | Identity platform, for example Okta | System Log query returns 90 days | Older events not returned unless streamed or exported | IT owner, with the data owner |
| Support tickets | Helpdesk, for example Zendesk | Archived in most cases 120 days after closing | Out of views and reports; still reachable by search and API | Customer support director |
| Ticket change history | Helpdesk audits | Kept with the ticket | Archived tickets drop out of the account-wide audit list; read ticket by ticket | Customer support director |
| Legacy plans and contracts | Acquired product's billing system and CRM | Until retirement | Gone, or reduced to a summary migrated into the new system | COO, CFO or CEO |
The pattern is consistent: the further a record is from current state, the shorter it lives. A billing platform will always show what a customer pays today. It may not show what it paid in 2022, why that changed, or which exception covered the gap.
What disappears first during plan consolidation
Three things tend to vanish in this order.
- Event detail. The 30-day and 90-day windows above run continuously. Any change older than that exists only if the company already kept it somewhere else. Okta offers log streaming to external platforms for exactly this reason, and many companies send billing events to a warehouse. Whether this company does is the first question.
- Legacy plan history. Consolidation projects migrate active customers onto current plans. The acquired system's history of old plan codes, grandfathered features and one-off deals usually stays behind. When the system is retired, that history goes with it unless someone decides otherwise.
- The mapping between old and new. The table that says which legacy account became which current account is often a spreadsheet owned by the integration team. Once the project closes, nobody maintains it.
Tickets are the most durable. Archiving changes how they are found, not whether they exist. That is why helpdesks often hold the complaint long after billing and identity have lost the decision.
The inventory before a system change
Ask the customer support director, at the level of what exists:
- Which systems hold plan histories, permission changes and support resolutions, and from which year?
- Are identity events streamed or exported anywhere, and since when?
- Are billing events copied to a warehouse or kept only in the platform?
- When is the acquired product's billing system scheduled to be retired, and who set that date?
- Does a mapping from legacy accounts to current accounts exist, and who keeps it?
- Roughly how many entitlement exceptions a year, and since when?
Write down the answers as ranges and names. If answering would mean logging in to a system, ask instead. Partners never ask for or handle raw client records. The software consolidation handoff checklist covers the wider project, and the system map for entitlement records shows which keys need to survive.
Who must approve keeping it
The partner never decides what is kept. Each record class has an owner, and keeping it past its default window is that owner's call, often with the executive above them.
- Event streams and exports need the IT owner to set them up and the data owner to agree that keeping them is appropriate, because identity events carry personal data.
- Legacy system retirement is usually a decision for the COO or CFO, sometimes written into the integration plan.
- Ticket retention sits with the customer support director, within the company's retention policy.
Do not recommend keeping or exporting anything. A partner's job is to notice that a real access event exists, such as a documented retirement date, and to ask who decides. That is real urgency; an invented deadline is not. The software consolidation introduction plan covers when to raise it, and the software consolidation guide covers the project itself.
Qualification: what the inventory settles
The inventory tells SourceX which records exist, for how long, in which system and under whose ownership. It does not settle whether they can be licensed. Customer contracts may limit use of account data, identity logs carry personal data and acquisition agreements can carry their own terms. Those questions belong to the company and SourceX in rights review. The who-can-license decision tree shows who should be in the room.
The company also needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client's consolidation has a dated retirement and the owner can say what exists before it, register as a partner, check the company on who qualifies and read the program terms before introducing its decision-maker.