This page is part of the subscription pause recovery guide. It treats the platform renewal as a clock and shows what happens to each record type as it runs.
The clock starts at the notice date
Most subscription platform contracts renew automatically unless the company gives notice by a set date. That notice date, not the renewal itself, is when the decision to move is made, and every later date follows from it: the overlap period when both platforms run, the day old admin access ends, and any deletion window the vendor documents after cancellation.
A partner needs only three dates from the company, read from its own contracts: the notice date, the planned cutover and the end of old access. If nobody knows them, that is the first finding. Never supply a date from a guess or from another company's contract.
How long each pause record tends to stay readable
Retention differs by vendor, plan and configuration, so the table lists what to ask and the windows some vendors document, as examples only.
| Record type | Where it lives | Documented example window | What changes when it passes |
|---|---|---|---|
| Detailed billing events | Billing platform API | Stripe: events from the last 30 days are fully available through the API; older events show a summary view | Field-level detail on what changed becomes harder to read |
| Closed support tickets | Support desk | Zendesk: tickets usually archive 120 days after closing; archived tickets leave views but stay reachable by search and API | Easy browsing ends; records remain |
| Support desk account after cancellation | Support desk | Zendesk: data in an expired account is deleted 90 days after the cancellation date | Tickets, comments and agent notes are gone |
| Pause, skip and resume events | Subscription engine | Set by the vendor's terms; ask the company | Ends with old access if not migrated |
| Voided or uncollectible invoices | Billing platform | Kept while the account exists; ask how pauses were billed | May never have been created if void was chosen |
| Refund and pause policies | Shared drive or wiki | Company retention schedule | Older versions are overwritten |
Stripe
ZendeskThe voided-invoice row needs care. Stripe's documentation on pausing payment collection says invoices for the paused period can be kept as drafts, marked uncollectible or voided, and that with void no record of charges is created for those periods. For a company that chose void, there is nothing to preserve in billing for those months; the engine events and tickets carry the story.
What disappears first
Three losses happen early and quietly, often before anyone notices the platform change has started.
- Field-level change detail. Once short API windows pass, what remains is often the current state of a subscription, not each change that led to it. A pause that moved a renewal date twice may look like it moved once.
- Who initiated each change. Migration tools tend to import active subscriptions and their current dates. The record of whether the customer or an agent paused a contract may not travel.
- History of cancelled or completed subscriptions. A new platform needs active customers on day one. Ended subscriptions, including many resolved pause cases, are the easiest to leave behind.
Tickets usually last longest, because the support desk is rarely replaced at the same time. The risk there arrives only if the desk itself is cancelled.
An Illustrative timeline for one platform renewal
A fictional 220-person coffee subscription company decides to move subscription platforms. The dates below are invented to show the order of events, not a forecast.
| Date | Event | Record types affected | Action owner |
|---|---|---|---|
| Month 0 | Notice given to the current subscription platform | None yet; inventory starts | Head of ecommerce |
| Month 1 | Inventory complete: record classes, years, owners | All, described at metadata level | Retention operations head |
| Month 2 | New platform imports active subscriptions only | Ended subscriptions and initiator history stay behind | Ecommerce lead |
| Month 3 | Old platform contract ends; admin access switched off | Pause, skip and resume events on old platform | Head of ecommerce |
| Month 3 | Support desk unchanged | Tickets and agent notes remain | Customer care leader |
The inventory in month 1 is the step that matters. It records what will be lost in months 2 and 3 while there is still time for the owners to decide what, if anything, the company keeps under its own policy.
Who must approve keeping each record
Keeping a record past its normal life is a company decision, made by the person who owns it and within the limits of its privacy notice, retention schedule and customer terms.
| Record type | Who can approve keeping it | Limit to check first |
|---|---|---|
| Subscription engine events | Head of ecommerce or retention operations | Customer terms, privacy notice |
| Invoices, refunds and voids | Finance lead | Payment and accounting retention rules |
| Tickets and agent notes | Customer care leader with privacy lead | Personal data in free text |
| Policies and macros | Retention operations head | Usually none |
If a retention schedule or customer agreement limits how long pause and payment records are held, that limit stands; the inventory simply records it. The Microsoft 365 guide and what happens to Salesforce data when a contract ends show how fixed post-expiry windows change the order of work, and exporting data before cancelling SaaS covers the general checklist.
Microsoft 365
SalesforceWhat the partner writes down
A partner records answers, never records: the record classes, years covered, system owners, the three contract dates and any limits the company names. The metadata-only Zendesk inventory template gives a format for the support desk line, and the system map shows which keys must survive a migration for cases to stay joined. To decide who receives the note, see who can license subscription pause records.
The introduced company 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 90% of the data is in English. Which records the company may license, whether buyers want them and whether an offer follows stay unknown until SourceX's review.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client has given notice on its subscription platform and years of pause recoveries sit on the old system, register as a partner, check the company against who qualifies and read the program terms before the access date arrives.