Getting started
Can licensing old records help pay for a system migration?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Licensing old records can help pay for a system migration, but it cannot be budgeted as funding, because value is known only once a buyer engages. The workable rule is sequencing: preserve complete exports and assess the archive before the old system is switched off, then decide on licensing after real buyer interest appears.
Key takeaways
- Treat possible license income as upside outside the migration budget, never as a funding source the project depends on.
- A migration's cutover date is fixed, while licensing moves at the pace of buyer interest, rights review and preparation.
- The cheapest moment to preserve history is before the old system's subscription or support contract ends.
- Track archive costs separately so a later license can be judged against what preservation actually cost.
Can a data license really fund a migration?#
A data license can contribute to the cost of a system migration, but it should never be the reason the budget closes. There is no price list for operational records; value is known only once a buyer engages with a specific, prepared package, and many archives never draw a buyer at all.
The useful framing for a CFO is optionality. A migration forces decisions about old records anyway: what to convert, what to archive and what to let go. Making those decisions with licensing in mind keeps an option open at little extra cost. Counting on that option to pay for the project does not hold up.
Why the timelines rarely line up#
Migration and licensing timelines rarely line up because a migration runs to a fixed cutover while a license runs on a buyer's schedule. The old ERP or helpdesk contract ends on a known date; a license first needs a fit check, rights review, privacy preparation, supplier approval, a contract and delivery.
Payment terms add their own timing. Licenses may pay on signing, on delivery, on acceptance or in installments, and refresh arrangements may pay over a longer period. None of that maps neatly onto a migration's vendor invoices and implementation milestones.
Accounting treatment is a separate question. Under ASC 606, a license to functional intellectual property is generally a right to use the IP as it exists when granted, with revenue recognized at a point in time, unless the licensor's ongoing activities substantively change it during the term. Whether a one-time dataset delivery or a refresh arrangement fits that pattern depends on the contract, so review the treatment with your accountant before forecasting anything.
The sequencing rule: preserve, assess, then decide#
The sequencing rule is simple: preserve complete history before the old system goes dark, assess it while you still have access and people who understand it, and decide about licensing only when buyer interest is real. Each step is cheap compared with trying to recover records after shutoff.
- Before contract end: confirm what the vendor's standard export includes and what needs a bulk or API export.
- Before cutover: export complete history, including closed records, internal notes, attachments and audit fields.
- Before decommissioning: document the schema, status codes and custom fields while administrators are still available.
- After cutover: store the archive read-only, with access logging and a named owner.
- Then: run a metadata-only fit check on the archive.
- Only after buyer interest: fund rights review and preparation for the record types a buyer wants.
What to preserve before the old system is switched off#
Migrations typically convert open and recent records and leave closed history behind, and closed history is where most licensing interest sits. The table lists what tends to be left out, by system type.
Old history can also be hidden from the tools a migration team uses. Zendesk, for example, automatically archives tickets 120 days after they reach Closed status; archived tickets remain reachable by search, direct link and API but do not appear in views. A migration built from views can miss years of closed tickets, so confirm the export pulls archived records too.
Export paths and fees vary by vendor and plan, so get the export route in writing before signing the new system's contract or sending a termination notice to the old one.
| Old system | What migration often leaves behind | What to export separately |
|---|---|---|
| Helpdesk (Zendesk, Freshdesk and similar) | Closed tickets, internal notes, macros, satisfaction comments | Full ticket threads with comments, tags and linked issues |
| CRM (Salesforce, HubSpot) | Logged emails, activity history, closed-lost opportunities | Activities and notes joined to accounts and opportunities |
| ERP (on-premises or hosted) | Closed orders, credit memos, returns, exception notes | Order history with exception and return records linked |
| Field service (ServiceTitan, FieldEdge) | Technician notes, photos, callbacks, warranty claims | Job histories joined to estimates, invoices and callbacks |
| Project systems (Deltek, Procore) | Closed projects, RFIs, submittals, change orders | Project records with correspondence and approval trails |
How to treat possible license income in the budget#
Possible license income belongs outside the migration budget, in a separate line the board can see but the project does not depend on. That protects the migration from a delayed deal or a buyer that never appears.
Keep a simple ledger of archive costs: export fees, storage, staff time and outside review. If a license follows, the ledger shows the real net. If none does, the spending bought records you may need for other reasons, such as disputes, audits, warranty claims or customer questions.
| Budget approach | When it fits | Main risk |
|---|---|---|
| Ignore licensing entirely | Archive has weak records or heavy restrictions | Losing the option if history is not preserved |
| Preserve as an option | Most companies with years of linked records | Modest export and storage cost with no assured return |
| Fund preparation after buyer interest | A fit check and buyer demand point to specific records | Preparation spending happens before a license is signed |
| Net expected income against migration cost | Rarely appropriate | A budget gap if no license is signed |
Illustrative: a distributor moving to NetSuite#
Illustrative: a fictional industrial distributor was moving from an older on-premises ERP to NetSuite. The project plan converted open orders and the most recent history, and the old server was scheduled for decommissioning soon after cutover.
The CFO asked IT to add one task before decommissioning: a full export of closed orders, returns and the customer service exception log, with a short data dictionary written by the longtime ERP administrator. The export was stored read-only and carried as an archive line outside the migration budget.
After cutover, the company ran a metadata fit check. Buyer interest emerged for exception records linked to orders, and the company funded preparation only for that record family. The migration budget never changed, and the decision to license rested on evidence rather than hope.
How SourceX fits into a migration plan#
SourceX fits into a migration plan at the preserve-and-assess stage: the fit check uses metadata only, so nothing is shared while the project team is busy with cutover. Large archives stay in the seller's own storage or ship on encrypted drives.
The SourceX Enterprise Data Value Framework helps with the CFO's conversation. Drivers such as human-generated signal, scale, recency and rights increase value, while preparation cost and privacy burden reduce net value. Those drivers explain why one archive is worth preparing and another is not, without anyone guessing at a number.
Frequently asked questions
Should we delay cutover to keep licensing options open?
Rarely. A complete export preserves the option at far lower cost than running two systems side by side. The exception is an archive that cannot be read without the old application's logic; then a short read-only extension may be cheaper than rebuilding meaning from raw tables.
Can a buyer cover the cost of exporting or preparing records?
Some licenses address preparation costs, and terms differ by deal, so do not assume it. Plan for the export as a cost of a migration you would run anyway, and treat any preparation funding as something negotiated once a buyer is engaged.
Who owns the decision about licensing migrated records?
The CEO usually decides, with the CFO owning the economics and counsel reviewing rights. IT owns the export and the archive. Keeping licensing as a separate decision from the migration stops it from slowing the cutover.
What if the old vendor charges for a full export?
Bulk or API exports sometimes cost extra or require a higher plan, so check the vendor's documentation and your contract early. Negotiating export terms before renewal or a termination notice is easier than afterward, when the vendor knows you are leaving.
Does licensing old records create tax or accounting work?
It can. License income, preparation costs and any installment or refresh structure may affect how revenue is recognized and taxed. Ask your accountant how a license would be treated before you forecast it, and keep preparation costs documented from the start.
Sources
- Under ASC 606, a license to functional intellectual property is generally a right to use the IP as it exists when granted, with revenue recognized at a point in time, unless its functionality is expected to substantively change during the license period through licensor activities. Source
- Zendesk automatically archives tickets 120 days after they reach Closed status; archived tickets can still be found by search, direct link, user profile and API endpoints, but do not appear in views. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.