# LIMS replacement archive context checklist | SourceX

Canonical: https://refer.sourcex.si/resources/laboratory-system-replacement-archive-context-checklist
Last updated: 2026-11-04

Work through three milestones in order: before the replacement is announced, before cutover to the new LIMS, and before the legacy system is switched off. At each one, confirm whether initial results, authorized corrections and released versions stay identifiable and linked, name the person who owns each answer, and note what is lost if the item is skipped. Every date on the timeline comes from the lab's own validated plan, not from an assumption.

This checklist is part of the [laboratory system replacement guide](/guides/moment-laboratory-system-replacement-lims-consultants), which explains why corrected-result provenance matters. This page is the follow-through: a dated record of who confirmed what, kept current until the old server is gone.

## Setting the clock before you tick anything

A countdown is only useful if its end point is real. Write down the three milestone dates as the lab has documented them, and who owns each, before any item gets a tick.

| Milestone | Where the date normally comes from | If there is no date yet |
|---|---|---|
| Announcement | The project charter, the vendor contract or the lab director's notice to staff | The checklist is early; work through milestone one without pressure |
| Cutover | The validation plan and go-live schedule for the new platform | Record who owns the go-live decision |
| Legacy shutdown | A server retirement ticket, a license end date or the IT decommissioning plan | Leave it blank; the item becomes "find out who decides" |

Give each item one of three marks. **Confirmed** means a person with authority said so. **Open** means nobody knows yet, with a named person to find out. **At risk** means the current plan loses it. A screenshot of a configuration screen is not confirmation; a quality manager's answer is.

Keep the sheet yourself, one row per item, and share it only with the people who answered. It records configuration and ownership, never content: no sample IDs, values, client names or report copies.

## Milestone one: before the replacement is announced

This is the cheapest moment to ask. Nothing has been decided about legacy history, and nobody is yet defending a migration scope.

| Confirm | Owner | If skipped |
|---|---|---|
| The legacy system records a first-entered value with timestamp and analyst for each result | System administrator | Later nobody can say whether first entries were ever kept |
| Corrections carry a reason, the person who changed it and the approver | Quality manager | The history shows that values changed but not why |
| Which regulatory regimes apply, and which only need accreditation rules | Quality manager | The archive is sized to the wrong retention period |
| Who owns results versus methods, specifications and review notes | Lab director, with counsel | Rights questions surface only after an introduction |

The regimes matter because they shape what already exists. FDA's electronic records rule (section 11.10(e)) requires secure, computer-generated audit trails in which a change leaves the earlier entry readable. The nonclinical lab rule (section 58.130(e)) adds a stated reason and a date for each change. A lab working under either regime usually has the linked history; the question is whether the migration will keep it.

## Milestone two: before cutover to the new platform

Once the field mapping is signed off, the legacy audit trail starts to look like a problem for later. These items protect the link between versions, not just their existence.

| Confirm | Owner | If skipped |
|---|---|---|
| The migration scope says whether audit trails move, are archived or are dropped | Project lead | Only current values load, and nobody notices for months |
| Migration validation checks meaning as well as value | Validation lead | A clean final number hides that it was ever corrected |
| Amended reports stay linked to the originals they replaced | System administrator | Released versions can no longer be traced to their corrections |
| An audit-trail export keeps sample and result IDs, not just a PDF per batch | System administrator | The export exists but cannot be joined back to results |

EU GMP Annex 11, where it applies, expects migration validation to confirm that data are not altered in value or meaning. That is the most useful sentence to quote in a scope meeting. Ask the validation lead whether their test scripts look at correction history at all, or only compare final values.

### A three-row check worth running once

Illustrative. A 310-person environmental testing lab plans to load each result's current value into a hosted platform. Before cutover, its system administrator follows one lead result on a drinking water sample through the migration plan:

| Version | What the plan does with it | Mark |
|---|---|---|
| First entry, 18 ppb, from the instrument run | Left in the legacy database, which is scheduled for deletion | At risk |
| Approved change to 12 ppb after a dilution factor was corrected, signed by the section supervisor | Exported as a batch audit report without result IDs | At risk |
| Reported value, 12 ppb, on the issued report | Loaded to the hosted platform | Confirmed |

Two at-risk marks on one trace tell the lab exactly what to fix while it still can. They also tell you that the history is real, linked today and worth a conversation.

## Milestone three: before the legacy system is switched off

Shutdown is final. Items still open here are usually lost for good, so this milestone is about access and authority rather than mapping.

| Confirm | Owner | If skipped |
|---|---|---|
| Where the archived audit trail will live: read-only database, export or vendor archive | IT manager | The history exists but nobody can open it |
| The archive stays readable for the full retention period | Quality manager | Files survive in a format no one can read |
| Retention covers corrected reports for at least the CLIA minimum, where CLIA applies | Quality manager | Corrected reports are deleted with the server |
| Who can authorize a licensing discussion about the archive | Owner, CEO or designated executive | An interested lab has nobody able to say yes |

The clinical lab retention rule (section 493.1105) names final, preliminary and corrected reports among records a lab must keep or be able to retrieve for at least two years. Annex 11 also expects access to be ensured throughout the retention period. An [archive is not a backup](/compare/data-archiving-vs-backup), so ask which one the plan describes. Labs moving off a home-built database face the same choice; the [legacy Access database page](/systems/migrate-microsoft-access-database-legacy) covers that case, and the [ERP replacement handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) shows the equivalent for finance systems.

## Reading the finished timeline

When all three milestones are marked, read the sheet back to the owner as one sentence per version: initial results, corrections and released versions, each confirmed, open or at risk, plus the earliest year in the legacy system. That summary is a complete metadata-level description. It answers the core question without a single result leaving the lab.

If the owner wants to explore licensing, three things follow.

**Disclose.** Tell the owner you are a SourceX referral partner and may receive a reward if a qualifying license completes. SourceX funds it separately and never deducts it from the lab's payout. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout.

**Check fit.** The lab needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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. Client-owned results usually need client consent, so the lab's own methods and correction workflow are the likelier starting point. Buyer need, the rights review and any offer stay unknown until SourceX reviews the application.

**Introduce.** Sign the Channel Partner Agreement first, then use the [annotated introduction email for lab directors](/resources/laboratory-system-replacement-introduction-email). The first valid introduction within the 90-day window is credited when the company submits a verified application. Illustrative only: a $250,000 qualifying payout to the lab would mean a $62,500 default reward. The [rewards page](/rewards) lists every condition, the [testing laboratory fit page](/industries/testing-laboratory-data-licensing) covers which lab records are strongest, and [what data provenance means](/proof/what-is-data-provenance) explains why linked versions matter.

## 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 timeline shows the lab's correction history survives shutdown and the owner wants to talk, [register as a partner](/register), confirm [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce anyone.

## 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
