When a spirometer or body plethysmograph reaches end-of-life, the clinical data it holds does not retire with it. Legacy pulmonary function test (PFT) records represent years of longitudinal patient history, and losing access to that data creates real clinical risk. The good news: migrating legacy PFT data from discontinued or unsupported equipment is a solved problem, provided you understand the landscape and choose the right approach.

TL;DR

• Legacy PFT data from discontinued equipment is recoverable and migratable with the right tools and planning.

• The "Messy Middle" of data migration is the evaluation and decision phase where most labs stall, not the technical transfer itself.

• Vendor-neutral, cloud-based platforms eliminate the single biggest barrier: proprietary format lock-in.

• A structured import workflow, combined with clear data validation steps, makes migration far less disruptive than most labs expect.

• Rezibase's Magic Import feature is purpose-built to extract discrete PFT data, including flow-volume loops, directly from device reports regardless of manufacturer.

What Is the "Messy Middle" in Legacy Data Migration?

The "Messy Middle" is a concept originally mapped by Google's consumer research to describe the confusing space between an initial trigger and a final decision. As explained by HT&T Consulting, it is the exploration and evaluation phase where people loop between gathering information and assessing options before committing. SEOZoom describes it as the crucial decision space between stimulus and purchase, where brands must actively guide consumers rather than waiting passively.

In the context of a respiratory lab, the "trigger" is usually a vendor announcing end-of-life for your testing equipment or software. The "purchase" is a new reporting system. Everything in between, including evaluating options, worrying about data loss, and stalling on a decision, is your Messy Middle.

The labs that navigate it well share one trait: they treat data migration as a workflow problem, not a technical crisis.

Why Do Labs Get Stuck in the Messy Middle?

Most respiratory labs do not stall because migration is technically impossible. They stall because of three compounding fears:

• Fear of data loss: Will historical flow-volume loops, raw measurements, and longitudinal trends survive the transfer?

• Fear of format incompatibility: Proprietary file formats from discontinued manufacturers feel like a dead end.

• Fear of disruption: Labs worry that migration will interrupt patient reporting during the transition window.

These fears are understandable but largely overstated when the right platform is in place. According to Think with Google AUNZ, omnichannel shoppers caught in this evaluation loop respond strongly to reassurance and clear, accessible information. The same psychology applies to clinical lab managers weighing a system change: clarity and confidence in the process are what move decisions forward.

What Are the Practical Steps for Migrating Legacy PFT Data?

A structured approach removes ambiguity and reduces risk. Here is a proven framework:

Step 1: Audit Your Existing Data

Before any migration begins, understand what you have:

• Identify all equipment models and their associated software versions.

• Catalogue the file formats in use (PDF reports, proprietary database exports, DICOM, HL7, raw device files).

• Flag which records are still actively referenced for longitudinal comparisons.

• Determine the volume of records requiring migration versus archival.

Step 2: Classify Data by Priority

Not all legacy data carries equal clinical weight:

Step 3: Choose a Vendor-Neutral Platform

This is the most consequential decision. A platform tied to a single manufacturer will recreate the same lock-in problem you are trying to escape. The key capability to look for is the ability to ingest data from any device, in any format, without requiring proprietary middleware.

Step 4: Run a Pilot Migration

Before committing the full dataset, migrate a representative sample:

• Select records spanning multiple equipment types and date ranges.

• Validate that discrete data fields (FEV1, FVC, TLC, DLCO) are correctly extracted.

• Confirm that flow-volume loops render accurately in the new system.

• Have a respiratory scientist, not just an IT administrator, sign off on data fidelity.

Step 5: Validate Against Original Reports

Every migrated record should be spot-checked against its source document. Automated extraction tools are highly accurate, but clinical data demands a human verification layer before the legacy system is decommissioned.

Step 6: Decommission With a Clear Cutover Plan

Set a defined cutover date, communicate it to all clinical and administrative staff, and ensure read-only access to the legacy system is available for a defined period post-migration as a safety net.

What File Formats and Compatibility Issues Should Labs Expect?

Legacy PFT equipment typically produces data in one or more of the following formats:

• Proprietary database formats (specific to manufacturers like Jaeger, SensorMedics, ndd, or older CareFusion systems)

• PDF or printed reports (common in older installations with no digital export capability)

• DICOM (increasingly common in newer legacy equipment)

• HL7 messages (where hospital integration existed)

• CSV or flat-file exports (available from some systems with data export utilities)

The practical challenge is that many discontinued systems have no supported export utility. In these cases, the most reliable approach is report-level extraction: ingesting the PDF or printed report and using intelligent parsing to extract discrete data fields. This is exactly the workflow that tools like Rezibase's Magic Import are designed to handle, pulling structured data including flow-volume loops directly from device-generated reports, regardless of the originating manufacturer.

How Do You Maintain Data Integrity During Migration?

Data integrity in PFT migration comes down to four principles:

1. Traceability: Every migrated record must retain its original test date, performing scientist, and equipment identifier.

2. Completeness: Partial migration is often worse than no migration. Define minimum acceptable data fields before the project begins.

3. Accuracy: Automated extraction should be validated against source documents by a qualified respiratory scientist.

4. Auditability: The migration process itself should be documented, including what was migrated, when, by whom, and what validation was performed.

Frequently Asked Questions

Can flow-volume loops be migrated from discontinued equipment?
Yes, provided the original report (PDF or digital) is available. Intelligent import tools can extract and render flow-volume loop data from device-generated reports without requiring access to the original proprietary software.

How long does a typical PFT data migration take?
Timeline varies by volume and format complexity. A well-prepared migration of several thousand records can typically be completed within a few weeks, with the bulk of time spent on audit and validation rather than technical transfer.

Do we need to keep the old system running during migration?
Ideally, yes, in read-only mode. Maintaining access to the source system during validation allows discrepancies to be investigated against the original data before decommissioning.

What happens to data from manufacturers that no longer exist?
If the software is defunct but reports (PDFs or printouts) still exist, those reports can be ingested and parsed. This is the most common scenario for truly discontinued equipment.

Is cloud storage safe for sensitive PFT data?
Yes, when the platform is compliant with relevant health data regulations. Enterprise-grade cloud platforms with appropriate access controls and audit logs meet or exceed the security standards of on-premise legacy systems.

What if our lab has data across five different equipment types?
A vendor-neutral platform handles this by design. The goal is a single unified record per patient, regardless of which device generated each individual test.

Do we need IT involvement for the full migration?
IT involvement is important for integration and access configuration, but the clinical validation steps must be led by respiratory scientists who can assess data fidelity in context.

About Rezibase

Rezibase is Australia's most advanced cloud-based respiratory and sleep reporting platform, built by respiratory scientists for respiratory scientists. Trusted by over 35 sites including NHS UK and NSW Health, Rezibase is manufacturer-agnostic, covers both respiratory and sleep, and has been supporting clinical labs for 37 years. The platform's Magic Import feature makes legacy data migration straightforward, extracting discrete PFT data and flow-volume loops directly from device reports across any equipment brand.

Ready to move your legacy PFT data to a modern, vendor-neutral platform without the headaches? Visit rezibase.com to learn more or start your 30-day free trial.

References

• Think with Google AUNZ. Buyer Behaviour in the Messy Middle. https://business.google.com/en-all/think/consumer-insights/messy-middle-2023/

• SEOZoom. Understanding the messy middle in the consumer funnel. https://www.seozoom.com/understanding-the-messy-middle-in-the-consumer-funnel/

• HT&T Consulting. The "Messy Middle" in Purchasing Behavior. https://www.htt.it/en/the-messy-middle-in-purchasing-behavior/