Platform Migration Data Load
Facility + Provider Master from the Order Ledger, Registry-Enriched
1,140 providers
Scoped from 18 months of orders and registry-enriched to 99.8% address coverage
Client
Regional Mobile Healthcare Services Provider
Date
May 2026
Service Line
Operational Flow
Context
The company was migrating its field workflow and billing platform to a new vendor that onboards via column-exact bulk-upload templates for facilities and ordering providers. The legacy platform's provider export carried only name and phone — no provider ID, address, credential, or specialty — and the CRM's facility list was mid-cleanup and unreliable. Whatever loaded into the new system would become its system of record.
Impact
Provider fields available
Provider address coverage
Specialty coverage
Facilities + providers scoped
Source data-entry errors
Patient PHI in deliverable
The Pattern
Source for the Linkage, Enrich by Identifier
When a vendor's official export is thin, don't accept its ceiling — find the system's richest export and enrich from a public registry keyed on a stable identifier. The unsolvable-looking provider problem (name and phone only) dissolved once the per-order ledger was used instead: it carried the provider ID, and that ID is the join key into a free national registry that backfilled name, credential, specialty, and address. Two moves made the migration accurate — scope facilities and providers from the order ledger (not the stale CRM relationship list) so the new platform starts clean, and treat a public identifier registry as the enrichment backbone instead of re-keying by hand. The exceptions report is the other half of the deliverable: surfacing the dozen records that need a human decision is what separates a trustworthy load from a confident-looking wrong one.
The same pattern applies to your business