Wind-downs and transitions
Read-only licenses vs archive exports: the cheapest way to keep old system records
By SourceX Editorial · Updated
Short answer
The cheapest way to keep old system records after closing is usually a verified export to storage the company controls, with a short read-only overlap to check it. Pay for a read-only or minimum license only when you need the application itself to read linked records, or when a legal hold or audit needs native access.
Key takeaways
- A vendor grace period after cancellation is a deadline to finish exports, not a retention plan.
- Read-only access is worth paying for only when exports lose the links between records you must keep.
- Retention duties, such as tax limitation periods and open claims, set how long access must last.
- An archive is only cheap if it is verified; an unverified export becomes a costly reconstruction later.
- Document format, field definitions and checksums so the archive stays readable without the vendor.
What is the cheapest way to keep old system records after closing?#
For most closing or downsized companies, the cheapest way to keep old system records is a verified archive export held in storage the company controls. The cost is mostly one-time staff effort, and the ongoing cost is storage and a named custodian rather than seats.
A read-only or minimum license costs more over time but keeps the application's screens, search and record links. That matters for some systems, such as an ERP where an invoice, a shipment and a credit memo only make sense together, and much less for a help desk or chat tool whose export already carries the conversation.
Four options compared on cost and access#
The four options below cover nearly every decision a CFO faces when a system is retired. The right answer often differs by system, so run the comparison per system rather than once for the whole company.
- Hidden costs of keeping a license: an admin who must stay trained, renewals that auto-extend the term, and vendor price changes at renewal.
- Hidden costs of an archive: the export and verification effort, a data dictionary, and someone to answer requests later.
- Hidden costs of a service: onboarding, per-volume fees, and a second migration when that contract ends.
| Option | What drives cost | Access you keep | Main risk | Best when |
|---|---|---|---|---|
| Keep the full subscription | Seats, tier and renewal term | Everything, including edits | Paying for features nobody uses | Operations or collections are still running |
| Downgrade to a read-only or minimum tier | Fewer seats, lower tier, vendor terms | Look-ups and often exports | Tier change switches off objects or exports | Native look-ups are needed for a defined period |
| Export to a company-held archive | Staff time to export and verify, plus storage | Files you control, no application | Lost links if relationships are not exported | Records stand on their own once exported |
| Move to an archive or backup service | Service fees and migration effort | Search through the service's viewer | Another vendor to manage and eventually exit | Large volumes with long retention duties |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Letting the subscription lapse is the most expensive option#
Letting a subscription lapse without exporting looks cheapest on paper because it costs nothing this quarter. It moves the cost into the future, when a dispute, an audit, a tax question or a buyer request arrives and the records no longer exist.
The cost of reconstruction is rarely small. Rebuilding customer histories from email, re-creating ledgers from bank statements or asking former staff what happened on a job all take more time than a planned export, and some records cannot be rebuilt at all.
Vendor grace windows are deadlines, not archives#
Vendor grace windows after cancellation vary widely, and every one of them ends. The table summarizes what several vendors' own documentation or terms say; confirm the current version for your account, because these policies change.
| System | What happens after cancellation |
|---|---|
| QuickBooks Online | Intuit support content describes a one-year read-only period in which data can be reviewed, exported and printed but not changed |
| Microsoft 365 | Most business subscriptions move from Expired to Disabled, when only admins can access and back up data, and then to deletion |
| Salesforce | Customer data is made available for export if requested within 30 days after termination, then may be deleted |
| HubSpot | For hubs other than Marketing Hub Professional and Enterprise, no access to customer data after termination |
| Zendesk | Sign-in ends after the billing cycle, and irreversible deletion begins 90 days after cancellation |
| Atlassian cloud | The site stays accessible for 15 days after the subscription ends, then paid-plan data is retained for 60 days before permanent deletion |
How long do you need access?#
Retention duties, not preference, should set how long any access lasts. The IRS says to keep records that support income, deductions or credits until the period of limitations for that return runs out, generally 3 years with longer periods in specific cases, and to keep employment tax records for at least 4 years after the tax is due or paid.
Other duties stack on top: customer contracts with audit rights, warranties still in force, open claims or litigation holds, lender requirements and state rules. Map each system to the longest duty that touches its records, then choose the cheapest option that covers it.
- Tax and accounting: general ledger, invoices, bills, payroll and fixed asset history.
- Customer obligations: warranties, service commitments, audit clauses and dispute files.
- Employment: personnel, time and benefit records under federal and state rules.
- Legal holds: anything relevant to a pending or reasonably expected claim, kept unchanged.
- Commercial options: records that might support a later sale, license or buyer question.
A decision rule for each system#
A simple decision rule keeps the read-only question from turning into a debate for every system. Answer the questions in order and stop at the first one that settles it.
| Question | If yes | If no |
|---|---|---|
| Is there a legal hold or audit that needs native screens? | Keep access and document why | Go to the next question |
| Do exports lose links between related records you must keep? | Price a minimum license for a defined period | Archive export is enough |
| Will staff need weekly look-ups during the wind-down? | Keep a minimum tier for that period only | Archive and cancel |
| Does the vendor offer a read-only or reduced tier at all? | Compare its cost with the export effort | Plan the export as the only route |
| Could the records support a later license or sale? | Export at full fidelity, with attachments | Export to meet retention duties |
Illustrative: a distributor retires an ERP and a help desk#
Illustrative: a fictional industrial distributor is downsizing after selling a division. It runs an on-premise ERP with years of orders, returns and credit memos, a cloud help desk for customer service, and a shared chat tool.
The CFO applies the decision rule. The help desk export carries full conversations, so the team exports, verifies and cancels it; the chat tool is archived the same way. The ERP is different: order lines, shipments and credits only make sense together, and an open customer dispute needs native look-ups. The company keeps one read-only seat for a defined period, exports full tables with their keys in parallel, and sets a date to retire the server once the dispute closes.
The archive is documented with a field dictionary and checksums, so a later custodian can read it without the ERP, and the read-only seat ends on the date the CFO set rather than renewing by default.
Archive formats that keep records usable, and where SourceX fits#
An archive export keeps its value when it preserves structure, context and proof of completeness. Export tables with their primary and foreign keys, conversations in JSON or another nested format, and attachments as files named by record ID, then add a manifest listing every file with a checksum and a data dictionary explaining fields and codes.
Those same properties matter if the company later considers licensing. In the SourceX Enterprise Data Value Framework, data cleanliness, recency and rights raise value, while preparation cost and privacy burden reduce net value, so a documented archive keeps preparation cost down. SourceX reviews archives on metadata first, and any package follows the SourceX five-step transaction, with the company approving each step and keeping ownership of its records.
Frequently asked questions
Can a read-only license still be used to export data?
Often, but not always. Some vendors keep export tools in reduced tiers, while others remove them or limit them to admins. Intuit, for example, says data in a cancelled QuickBooks Online account can still be exported during its read-only period. Confirm export rights in writing before choosing a tier.
Who pays for licenses after the company dissolves?
Someone with authority must keep paying and administering them, such as officers during winding up, an assignee or a trustee. Without a named payer, subscriptions lapse on a closed card. Give each retained system an owner, a payment method and an end date in the wind-down budget.
Should we keep the old servers instead of exporting?
Powered-down servers make a weak archive. Hardware fails, database and operating system licenses lapse, and nobody remembers the passwords. If you keep a server image, also export tables and documents to open formats and test that the image still starts.
Is cloud storage for the archive a cost worth worrying about?
Storage is usually the smallest cost in the decision, well below seats and staff time. The real ongoing cost is custody: someone who holds access, answers requests and applies the retention schedule. Name that person or firm before the last employee with system knowledge leaves.
How do we prove the archive is complete?
Compare record counts and date ranges with the live system before cancelling, open a sample of records including attachments, and write down who checked what and when. Store that note with the manifest; without it, nobody can later show the archive matches the system it replaced.
Sources
- After cancelling QuickBooks Online, data stays available in read-only mode for one year, during which it can only be reviewed, exported and printed. Source
- QuickBooks Online data can still be exported while a cancelled account is within its one-year read-only period. Source
- Most Microsoft 365 business subscriptions move through Expired and Disabled states, when only admins can access and back up data, before deletion. Source
- Under the Salesforce Main Services Agreement, Customer Data is made available for export if requested within 30 days after termination, after which Salesforce has no obligation to maintain it. Source
- For HubSpot hubs other than Marketing Hub Professional and Enterprise, HubSpot will not provide access to Customer Data after termination or expiration. Source
- Zendesk starts permanently deleting Service Data 90 days after cancellation or termination, and the process cannot be reversed. Source
- Once a Zendesk account is cancelled, sign-in ends after the billing cycle and data is deleted under the deletion policy. Source
- After a cancelled Atlassian subscription period ends, the site stays accessible for 15 more days, then data is retained 60 days for paid plans before permanent deletion. Source
- Keep records supporting income, deductions or credits until the period of limitations runs out, generally 3 years with longer periods in specific cases; keep employment tax records at least 4 years after the tax is due or paid. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.