# Mainframe Modernization Firms: A Fee on Client Code Deals

> For mainframe modernization firms and legacy consultants: when a client licenses COBOL, JCL and change history to AI companies, you can earn a fee.

Canonical: https://origindatapartners.com/refer/mainframe-modernization-firms
By: Origin Data Partners
Updated: 2026-11-20

To join, enter your name and email under [Get my link](https://origindatapartners.com/refer#get-link): your personal partner link appears there, with no account needed.

## Short answer

Yes: mainframe modernization firms can earn a fee for introducing a client that licenses its own COBOL, JCL and copybooks, with their change history, to AI companies. The client owns its code, and your firm never offers it. You receive 50% of what Origin earns on the deal for a company you introduced, up to $100,000 per company. Your share is paid within 30 days after the deal completes, and an introduction is credited to the first partner who registers it, for 12 months from the date it is registered.

## Why raise it before decommissioning, not after?

Because the change history is often the first thing lost. Moving elements without history, consolidating levels or switching off the library leaves only the final source, and the record of how decades of fixes were made is gone. Raise it at assessment, before anything moves.

Library tools say so plainly. One source manager's documentation lists "three methods to consolidate delta levels: Automated Element Level Versioning; Auto Consolidation; and Aged Delta Retention" ([Endevor documentation](https://ftpdocs.broadcom.com/cadocs/0/CA%20Endevor%20Software%20Change%20Manager%2016%200%20PUBLIC%20ACCESS%20%20LIMITED%20%20Bookshelf-ENU/Bookshelf_Files/HTML/EndevorSCM_Admin_ENU/delta_level_management.html)), and its support note on a move without history reads: "Once the element is moved, the individual levels are consolidated into a single VVLL Delta. There is no way to get the individual levels back." ([Broadcom knowledge base](https://knowledge.broadcom.com/external/article/138129/can-an-endevor-move-be-reversed-to-recov.html)).

## What do mainframe modernization firms' clients hold that AI companies license?

COBOL programs, copybooks, JCL and PROCs, Fortran where it survives, test data and the change history that links each change to a request or defect. Twenty years of one insurer's or bank's batch system is the typical fit. For what that code looks like, read [COBOL and JCL code explained](https://origindatapartners.com/guides/cobol-jcl-legacy-code).

- Source with history from Endevor, ChangeMan, CA Panvalet or a git migration.
- Copybooks and the record layouts they define, with sample data de-identified.
- JCL, PROCs and scheduler definitions that show how jobs run together.
- Change requests, defect tickets and test cases tied to each change.
- Not a fit: vendor packages the client licenses, and code your firm wrote with its own tools.

## Who owns the code: the client, your firm or the software vendor?

The client owns what its staff wrote, and usually what contractors wrote for it under a signed assignment. Software vendors own their packages. Your firm owns its converters, accelerators and methods unless the contract says otherwise. Only the client's own code can be licensed.

Code written by employees is a work made for hire: "a work prepared by an employee within the scope of his or her employment" ([17 U.S.C. 101](https://www.law.cornell.edu/uscode/text/17/101)), and "the employer or other person for whom the work was prepared is considered the author for purposes of this title" ([17 U.S.C. 201](https://www.law.cornell.edu/uscode/text/17/201)). Code from outside contractors moves only in writing: "A transfer of copyright ownership, other than by operation of law, is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed" ([17 U.S.C. 204](https://www.law.cornell.edu/uscode/text/17/204)).

## What does your modernization contract say about client code?

That you use it only to do the work. Confidentiality and code-ownership clauses keep the client's source with the client, and nothing in an introduction changes that. You raise the option; the client licenses from its own copy.

Bank clients write this in. Federal banking guidance treats access to source code as a contract matter, noting "it is important to consider a provision to establish escrow agreements to provide for the banking organization's access to source code and programs under certain conditions" ([Interagency third-party guidance](https://www.federalregister.gov/documents/2023/06/09/2023-12340/interagency-guidance-on-third-party-relationships-risk-management)). Treat a client's code with the same care: no copies, no samples, no examples in a pitch deck.

Your care also protects the client's rights. Code stays a trade secret only if "the owner thereof has taken reasonable measures to keep such information secret" ([18 U.S.C. 1839](https://www.law.cornell.edu/uscode/text/18/1839)), and a vendor that leaks it weakens that claim.

## Do you have to disclose the fee to a mainframe client?

Yes, in writing, before the introduction, and in the statement of work if you are already engaged. A client paying for a migration should never learn later that its vendor was paid for something else in the same project.

The FTC's test for a material connection is a fair guide: a connection "that might materially affect the weight or credibility" of what you say gets disclosed ([16 CFR 255.5](https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5)). One line works: "We may receive a fee from Origin Data Partners if you license your legacy code. It does not change your payment."

## How do you raise it without slowing the migration?

Keep it off the critical path. An assessment already inventories programs, copybooks and job streams; add one question about history and one about retention. The license, if any, runs on its own track with the client.

- Assessment: record how many years of change history each library holds.
- Before any move: suggest the client exports libraries with full history to storage it controls.
- At cutover: nothing changes in your plan. The old system is switched off on schedule.
- When the CIO agrees: give the client your partner link, or introduce it by email.

## What mainframe modernization firms do, and do not do

You notice which clients have decades of code with history, raise licensing with the executive who owns it, and make the introduction. You do not extract, sample or describe client code, and you never delay a decommissioning to keep a library alive.

If your firm also migrates ERP or help-desk systems, read the page for [software implementers and MSPs](https://origindatapartners.com/refer/software-implementers-and-msps); this page is only about mainframe and legacy code.

Joining takes about a minute: [get your partner link](#get-link). It costs nothing, and you can decline the fee on any introduction. Origin Data Partners is an independent data partner that helps business owners value and license their company records: the company pays Origin nothing, and a buyer may pay Origin when a deal completes.

## How we checked this

We read every source on this page on 20 November 2026, at the primary source: the copyright statute on works made for hire, authorship and transfers (17 U.S.C. 101, 201 and 204), the federal banking agencies' 2023 third-party guidance in the Federal Register, the FTC rule on material connections, and Broadcom's own Endevor documentation and knowledge base.

What we could not verify: modernization contracts are private, so we cannot say what a given client agreed about its code. Other source managers handle history differently, and we read only one vendor's documentation. No buyer has published a price for COBOL with change history.

## What you earn

You receive 50% of what Origin earns on the deal for a company you introduced, up to $100,000 per company, paid after the deal completes.

- Example: A 60-person manufacturer licenses its quality and CAD records. Example figure: Origin earns $100,000 on the deal. $100,000 x 50% = you receive $50,000.
- Example: An 80-person contractor licenses its closed project records. Example figure: Origin earns $40,000 on the deal. $40,000 x 50% = you receive $20,000.
- Example: A large company that closed outside bankruptcy or an assignment sells its records. Example figure: Origin earns $225,000 on the deal. $225,000 x 50% = you receive $100,000. Half of $225,000 is $112,500, so the $100,000 cap applies.

Examples, not offers. The figures are illustrative: what Origin earns depends on the buyer, the records and the deal, and a buyer may decline a company it already knows. Your share is half of what Origin actually earns on the deal for that company, confirmed in writing before the company signs.

## Which clients qualify

| Client | Records buyers ask for | Size signal | Published buyer range |
| --- | --- | --- | --- |
| Lender or investment firm | Loan and credit files with outcomes | 5–200 staff | Published buyer range: $50K–$800K (investment firm) |
| Software company | Private code and its history, tickets | 15–500 staff | Published buyer range: $50K–$500K |
| Company closing down (not in bankruptcy) | Everything still retained | Peak headcount counts | Some buyers publish a separate track for closed companies |

Ranges are what AI data buyers publish they pay companies of each type, read 13 November 2026; the figures and their sources are in [AI training data buyers by data type](https://origindatapartners.com/guides/ai-training-data-buyers-by-data-type). They are not offers.

## Licensed professionals

- **CPAs.** The AICPA Code's Commissions and Referral Fees Rule (1.520.001) says a member in public practice "shall not for a commission recommend or refer to a client any product or service" while the member or firm performs for that client an audit or review of a financial statement, certain compilations, or an examination of prospective financial information, whoever pays the commission, and for the periods those services cover. A permitted commission or referral fee must be disclosed to the client. State boards of accountancy can be stricter. Source: [AICPA Code of Professional Conduct, 1.520.001 Commissions and Referral Fees Rule (PDF)](https://pub.aicpa.org/codeofconduct/ethicsresources/et-cod.pdf).
- **Attorneys.** A fee for recommending a client to a third party can be a personal-interest conflict (ABA Model Rule 1.7(a)(2)); where it is, the client's informed consent, confirmed in writing, is required. States adopt their own versions, and some restrict such fees further. Check your state bar's rules. Source: [ABA Model Rules of Professional Conduct, Rule 1.7 (conflict of interest: current clients)](https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_1_7_conflict_of_interest_current_clients/).
- **Registered representatives.** FINRA Rule 3270 requires prior written notice to your member firm before you are compensated for a business activity outside that relationship; the firm may limit or prohibit it. Source: [FINRA Rule 3270: Outside Business Activities of Registered Persons](https://www.finra.org/rules-guidance/rulebooks/finra-rules/3270).
- **Registered investment advisers.** As a fiduciary under the Advisers Act you must make full and fair disclosure of this conflict so the client can give informed consent (SEC Release IA-5248, 2019). Your firm may also require it in Form ADV Part 2A (for example Item 14, Client Referrals and Other Compensation) and may restrict it. Follow your compliance policies. Source: [SEC Release IA-5248 (2019): Commission Interpretation Regarding Standard of Conduct for Investment Advisers (PDF)](https://www.sec.gov/files/rules/interp/2019/ia-5248.pdf).
- **Fractional CFOs, consultants, MSPs, software implementers, business brokers.** Usually free to accept a fee with disclosure to the client, unless you hold one of the registrations above. Check your client agreement.
- **Bankruptcy trustees, debtors in possession, assignees, receivers, examiners and professionals employed by an estate.** No fee, ever, for any estate they serve. Knowingly and fraudulently giving, offering or receiving a reward for acting or forbearing to act in a bankruptcy case is a federal crime (18 U.S.C. 152(6)); a debtor in possession has a trustee's duties (11 U.S.C. 1107(a)); professionals an estate employs need court approval (11 U.S.C. 327(a)) and are paid only as the court awards (11 U.S.C. 330). Assignees and receivers are state-law fiduciaries with the same duty to the creditors. The benefit goes to the estate. Source: [18 U.S.C. 152 (concealment of assets; false oaths and claims; bribery)](https://www.law.cornell.edu/uscode/text/18/152).

You are responsible for your own compliance and for telling your client about the fee. Information, not legal advice; check your own rules. If you cannot or prefer not to accept a fee, introduce the company anyway and tell us you decline the fee: the company gets the same work and the same terms.

## Questions

### I'm a mainframe modernization consultant. My clients have decades of COBOL and JCL code. Can I earn a referral fee when one of them licenses that code?

Yes, for the introduction, with the fee disclosed in writing. The client licenses its own code from its own copy and signs the agreement. Your contract keeps you from using the code for anything else, and nothing in the introduction changes that.

### I'm an IBM business partner. Which companies pay partners a referral fee when their enterprise clients license legacy code for AI training?

This page covers Origin's terms only: a fee for introducing the client, due after a licensing deal completes. We do not describe other companies' terms. Check your own partner agreement for any rule on outside fees before you register an introduction.

### Can an IT or ERP consultant earn money helping clients license their old system data to AI companies?

Yes, by introducing the client rather than handling its data. The client decides, licenses from its own systems and signs. You register the introduction, disclose the fee, and a fee is due only if a licensing deal completes under the partner terms.

### How much is a finder's fee for introducing a legacy code client?

No law or public benchmark sets one for data introductions. Origin's terms are stated on this page and do not change by client. What protects you is the same everywhere: the client knows about the fee in writing and its own payment is not reduced.

### Which of my clients' records would AI companies license: COBOL, Fortran and JCL with change history, copybooks, test cases?

All of them, together. Source with its change history shows how real systems were fixed and extended; copybooks and JCL show how data and jobs fit; test cases show what correct looks like. Vendor packages and your firm's own tools stay out.

### Does my mainframe client pay anything if the deal goes ahead?

No. The mainframe client pays Origin nothing. A buyer may pay Origin when a deal completes, and your fee is paid out of that, so the client's own license payment stays whole and its source libraries never leave its control.

### How do I bring up data licensing with a mainframe client without it looking like a sales pitch?

Ask about history during the assessment: how many years each library holds and what happens to it after cutover. If the client asks why, explain that the history itself can be licensed. If it is not interested, the migration goes on unchanged.

### How long is my credit for introducing a mainframe client?

Twelve months from registration, to the first partner who registers that client. Register once the executive who owns the code agrees, and keep that written agreement with the statement of work for the migration.

Full partner terms: https://origindatapartners.com/refer ([Markdown](https://origindatapartners.com/refer.md)).
