How MSPs for manufacturers can read legacy ERP servers as a licensing signal

Why the reference server is the signal

Most manufacturers do not delete their old ERP after a migration. They keep it on a virtual machine, read-only, because customer service needs old order history, quality needs lot genealogy for a warranty claim, and engineering wants to see why a routing changed years ago. As their MSP, you patch it, back it up and field the yearly question of whether it can finally be switched off.

That server is a strong hint that the company holds what AI labs and data buyers look for: years of connected operational records with outcomes. Quotes that became jobs, routings with their actual run times, nonconformance reports with root cause and corrective action, engineering change orders with the reason for each change. Researchers at Epoch AI have projected that, if current trends continue, language models will fully use the stock of public human-written text sometime between 2026 and 2032. The forecast carries wide uncertainty, but it explains why permissioned, non-public records like these draw interest.

SourceX manages the license end to end. Your role is to notice the signal, raise it with the owner before decommissioning, and make the introduction. The MSP partner page explains the program in general terms.

What sits on a manufacturer's legacy servers

Each retired system holds a different slice of the plant's history. Ask one question per system before it goes.

The more of these that share part numbers, job numbers or customer IDs, the more valuable the whole set becomes, because records can be followed from quote to shipment to complaint.

Which manufacturing clients fit

The baseline is the same for every company SourceX reviews, but it reads a little differently on a plant floor.

• Size: 50+ full-time employees at peak (contractors excluded). Agency temps on the line do not count; full-time hourly and salaried staff do.
• History: several years of documented operations, ideally with an archived system or two from before the current ERP.
• Breadth: records across ERP, quality, engineering, maintenance, email and chat rather than in one spreadsheet. Strong companies run 10-15+ systems.
• Rights: the company created the records and its customer and supplier agreements allow licensing them.
• Sponsor: an owner, CEO, CFO or authorized representative who can decide.

Job shops, contract machining and fabrication, electronics assembly, plastics, and the office operations of process plants all appear in MSP books. Distributors fit too, with long order, pricing-exception and returns histories. The who qualifies page sets out the full criteria.

The decommission gate

Add four questions to your server decommissioning checklist. Nothing is wiped until each has an answer from the client.

• Retention: has the company kept a complete, restorable export, including database and attachments, under its own control?
• Ownership: which records did the company create, and which belong to customers, such as build-to-print drawings, specifications and customer-owned tooling data?
• Sponsor: who at the company decides what happens to the history?
• Question asked: has that person been told the archive may have licensing value, and decided whether to review it?

The gate protects the client whatever it decides. A retained export keeps traceability and warranty lookups working, and it keeps the licensing option open. The company fit checker gives the owner a preliminary, non-binding read in a few minutes.

When to raise it with the owner

These are the moments when an MSP is already in the room talking about old systems.

Customer, export-control and people limits

Manufacturing records carry more third-party rights than most. Keep these out, or flag them for the company's own review:

• Customer drawings, specifications and quality agreements under build-to-print or confidentiality terms.
• Export-controlled technical data and controlled unclassified information from defense or aerospace work; the CMMC MSP guide covers how those enclaves are scoped.
• Supplier pricing and customer price lists.
• Personal data: operator names on labor tickets, HR and payroll records, badge and camera data. Operational records are de-identified under rules agreed with SourceX before any work begins.

Cost and quote histories are a strong asset when they are clean; the guide for fractional CFOs in manufacturing shows how costing projects surface them, and the PLM migration guide covers ECO and BOM histories before cutover.

How the introduction works, with no data leaving the plant

The referral is a conversation, not a data transfer.

1. Register as a partner and give the owner your referral link, or use the referral form with fit facts only: approximate peak headcount, years in operation, the systems you support and who would sponsor the review.
2. SourceX talks to the sponsor to check size, history, breadth and rights.
3. The company lists its systems, years covered and exportable records in a data inventory.
4. Price and terms are agreed between the company and SourceX, including exclusions for customer and export-controlled material.
5. AI labs and data buyers review the opportunity; nothing binds the company until it signs.
6. After an executed agreement and the company's authorization, records are prepared under the agreed redaction rules and delivered, and the company receives a one-time payment.

Keep the referral and your service work separate. The referral never involves you exporting, sampling or describing records, and anything the company later asks of its IT provider is the company's own decision under its own agreements.

What to say at the QBR

How rewards work for a manufacturing MSP

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed.

Your reward is a share of SourceX's fee and is not taken from the manufacturer's payment. Disclose it to the client, and check your service agreement for any conflict terms before you register.

When not to bother

• The plant is below 50 full-time employees at peak, or relies mostly on agency labor.
• The legacy server was already wiped and no export survived.
• Most work is build-to-print for a few customers whose agreements claim the records.
• The majority of records sit inside a defense enclave.
• The owner will not consider an exclusive license for an agreed term.

Companies that fail today can qualify later; a decommission gate that preserves the export is what keeps that door open. Lean and continuous improvement records are another strong signal at the same clients, covered in the guide for lean manufacturing consultants.

Next step

List every legacy ERP, MES and QMS instance across your manufacturing clients and add the decommission gate to each retirement ticket. For the first owner who says yes, register as a partner and make the introduction, or have the company apply directly at sourcex.si/apply with your referral link.