# LIMS replacement and corrected results | SourceX

Canonical: https://refer.sourcex.si/guides/moment-laboratory-system-replacement-lims-consultants
Last updated: 2026-11-04

During a laboratory system replacement, ask the lab owner or quality lead one metadata question: after cutover, will each result still show its initial value, every authorized correction with reason and approver, and the version that was released? If all three remain identifiable and linked, the lab holds a review history worth assessing, and you can offer to introduce its decision-maker. If the migration plan loads only the current value, that history may be lost when the old system is switched off.

## Are initial results, authorized corrections and released versions all identifiable?

That is the whole question, and it covers the lab's corrected-result provenance: the record of what was first measured, who changed it, why, and what went out on the report. A replacement project is the one time an outsider sees exactly where that record lives and whether it will survive.

The question has three parts, and each can fail on its own:

1. **Initial result.** The value as first entered or captured from the instrument, with its timestamp and analyst.
2. **Authorized correction.** Each change, with the reason, the person who made it and the person who approved it. For records under FDA's electronic records rule, 21 CFR 11.10(e) requires secure, computer-generated, time-stamped audit trails of entries and actions that create, modify or delete records, and says changes shall not obscure previously recorded information. Where GLP rules apply, 21 CFR 58.130(e) also requires the change to state its reason and be dated, and for automated entries to identify the individual responsible.
3. **Released version.** Which value went out on the report, and whether a corrected report followed. CLIA's retention rule (42 CFR 493.1105) names final, preliminary and corrected reports as records a lab must keep or be able to retrieve for at least two years.

Labs under other regimes follow their own accreditation and retention rules, so ask the quality manager which apply. You do not need to see any of the records. You need the owner's yes, partly or no for each part, and the system names.

### Evidence asset: the three-version trace for one sample

Illustrative: a fictional 240-person food and ingredient testing lab is replacing a 12-year-old on-premises LIMS with a cloud system. The field mapping sends each result's current value and release date to the new platform; the audit trail is scheduled for a PDF export before the old server is retired. The consultant asks the quality manager to trace one moisture result on an ingredient lot.

| Version | Value | Who | Reason kept? | Identifiable after migration? |
|---|---|---|---|---|
| Initial result | 4.8% | Analyst | Not applicable | Only if the audit trail migrates or is archived |
| Authorized correction | 3.9% | Supervisor approves the change | Yes: balance calibration error found | Only if the audit trail migrates or is archived |
| Released version | 3.9% on the certificate of analysis | Reviewer releases | Yes: release record | Yes, in the migration scope |

If only the last row moves, the new system shows a clean 3.9% and no sign that anything was ever corrected. Run the same trace on two or three result types the lab reports most often, and record a single word for each: yes, partly or no. That word, the earliest year in the current system and whether the lab or its clients own the results are all you need to note.

What makes a lab like this a candidate is not the size of the archive. It is that initial values, corrections and released versions still exist as linked records, so each correction can be read as a decision: a value, a reason to doubt it, an approved change and an outcome.

## Why is corrected-result provenance easy to overlook?

Nothing breaks when it goes. Migration scopes usually prioritize the current value of each result, since that is what the new system needs to run. The audit trail, the earlier versions and the free-text reason for a change are often handled as an archive problem for later, or exported as a static report detached from the sample IDs.

EU GMP Annex 11, where it applies, expects migration validation to check that data are not altered "in value and/or meaning", and expects stored data to stay accessible, readable and accurate throughout the retention period. A result that keeps its final number but loses its correction history has kept its value and lost part of its meaning. A LIMS consultant sees that gap first, at the mapping table, months before anyone in the business notices.

This is why the trigger differs from an ERP move, which mostly carries finance and procurement histories (see [ERP replacement introductions](/guides/an-erp-replacement) and the [advisor plan for an ERP replacement](/guides/a-practical-introduction-plan-for-advisors-supporting-an-erp-replacement)). In a lab, the valuable part is the review step between capture and release, and [correction histories before a LIMS replacement](/guides/workflow-lab-result-correction-histories) maps that record chain in more detail.

## Four metadata questions to put to the owner

Keep the conversation at the level of what exists, not what it says.

- **What:** Which record classes carry correction history today: results, specifications, sample login, instrument runs?
- **How long:** How many years of history sit in the legacy system, and does the history cross any earlier migrations?
- **Which system:** What is the legacy LIMS, what replaces it, and where would an audit-trail export or read-only archive live? An [archive is not the same as a backup](/compare/data-archiving-vs-backup), so ask which one the plan means.
- **Who owns it:** Who decides retention for laboratory records, who owns the results versus the methods and review notes, and who could authorize a licensing discussion?

Never ask for counts of corrections, example reports, screenshots or exports. A partner never handles laboratory records. If the migration has already happened, ask whether the legacy database, an audit-trail export or a read-only archive still exists and who holds it; a decommissioned system with nothing kept usually ends the conversation.

## How do you disclose the reward and get the owner's permission?

Ask permission before you mention SourceX or share the company's name, and disclose your interest at the same time: you may receive a referral reward from SourceX if a licensing transaction completes, paid by SourceX separately and never out of the lab's compensation.

If the owner wants to hear more, explain that SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Client-owned results would usually need the clients' consent, and the lab's own methods, review notes and correction workflow are the more likely starting point. If the owner says no, the replacement carries on and your role is unchanged.

Keep the reward description exact. The default is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap. Illustrative only: a $250,000 payout to the lab would mean a $62,500 reward. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/terms) set out.

## Who can authorize the discussion, and what stays unknown?

The quality manager or lab director knows where the history lives. The person who can authorize a licensing discussion is usually the owner, CEO or a designated executive, because the decision involves contracts with clients and accreditation bodies as well as records.

| Question | Usually answered by | Settled before the introduction? |
|---|---|---|
| Does linked correction history exist? | Quality manager or LIMS administrator | Yes, as a yes or no |
| How many years, which systems? | LIMS administrator | Yes, approximately |
| Who owns the results versus the methods and review notes? | Lab director with counsel | Partly; SourceX confirms |
| Can any of it be licensed, and in what form? | SourceX with the company | No |
| Is there buyer interest in this record type? | SourceX | No |

The company also needs to meet the baseline: 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 70% of the data is in English. The [testing laboratory fit page](/industries/testing-laboratory-data-licensing) covers which lab records tend to be strongest, and [what data provenance means](/proof/what-is-data-provenance) explains why the linked versions matter to a buyer.

Sign the Channel Partner Agreement before you submit an introduction. The first valid introduction within the 90-day window is credited when the company submits a verified application. The [network opportunity finder](/tools/network-opportunity-finder) helps sort the rest of your client list, and other trigger moments are collected on the [partner pages by role](/for).

## Go deeper on laboratory system replacement records

- [Laboratory system replacement archive context checklist](/resources/laboratory-system-replacement-archive-context-checklist): a checkpoint-by-checkpoint checklist for confirming the audit trail is scoped, mapped, validated and readable after shutdown.
- [Laboratory system replacement introduction email](/resources/laboratory-system-replacement-introduction-email): a ready-to-adapt email for introducing an opted-in lab director to SourceX.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the quality manager can say yes to all three versions and the director opts in before the old system is retired, [register as a partner](/register), check the lab against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you make the introduction.

## Sources

- https://health.ec.europa.eu/system/files/2016-11/annex11_01-2011_en_0.pdf
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11/subpart-B/section-11.10
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-58/subpart-G/section-58.130
- https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-G/part-493/subpart-J/section-493.1105
- https://refer.sourcex.si/terms
