Data migration

Your history moves with you.

Years of cases sit in your current registry system or with your services vendor. We move them, check them, and run beside your old system until you are satisfied.

Talk about your migration See the steps

What we take

Bring it in whatever form you have it.

Registry data

NAACCR fixed-width, v18 through v25
Exports from legacy registry systems
State registry submission files
Follow-up and recurrence history

Files and extracts

CSV, TSV and fixed-width text
Excel workbooks
XML and JSON
Database extracts and backups

Clinical feeds

HL7 v2 messages
FHIR bundles
Pathology and lab reports
Scanned and PDF documents

Program setup

Facility identifiers and NPIs
Physician and location rosters
State submission configuration
Follow-up and suspense lists

How it runs

A migration you can watch, step by step.

Step 1

Inventory

Every source, format and year accounted for, with record counts agreed before anything moves.

Step 2

Mapping

Fields mapped to the current NAACCR layout, with your registrar reviewing anything ambiguous.

Step 3

Test load

A sample loaded and checked field by field, so problems surface before the full run.

Step 4

Full load and QA

Everything loaded, validated against SEER*Edits, and reconciled back to your counts.

Step 5

Parallel and cutover

Run beside your current system through a submission cycle, then switch when you are ready.

Quality assurance

Checked before you are asked to trust it.

Migration is only finished when the numbers agree. Every load comes with a reconciliation you can hand to your cancer committee.

Record counts reconciled by year, site and class of case.

Field-level validation against the NAACCR layout and allowed values.

SEER*Edits run on migrated cases, with errors listed for review.

Duplicate and conflict detection across overlapping sources.

Registrar spot-check on a sample of cases, yours or ours.

Exception log of everything that did not map cleanly, and what we did about it.