Item Master Readiness and ERP Migration in Healthcare
ERP migrations succeed or fail on data. Technology gets attention, but incomplete, inconsistent, or poorly structured item master data slows projects, inflates cost, and frustrates users after go-live. If you move a messy item master into a new ERP, you carry every problem forward and waste the best chance to fix it at scale.
The failure rate for migration projects makes the risk concrete. Gartner research shows that 83% of data migration projects either fail outright or exceed their planned budgets and schedules. In healthcare, where item master records number in the tens of thousands and touch receiving, scanning, billing, and clinical workflows simultaneously, the cost of carrying bad data into a new system is higher than in almost any other industry. The 2025 KLAS Digital Health Most Wired report identified ERP systems as one of the two primary areas of platform consolidation across healthcare organizations, with finance and HR leaders accelerating cloud ERP adoption to gain unified visibility into costs, supply chains, and workforce management. Most hospitals are either mid-migration or approaching one, which means the window to reset product data standards is now, before go-live, not after.
Why ERP Migrations Expose Item Master Problems
Many legacy ERPs tolerate sloppy item data. You can have duplicate items, vague descriptions, partial packaging, and missing codes and still process orders. New cloud ERPs are less forgiving and expect clear identities, standardized descriptions, structured attributes, and complete categories for every item record.
During migration, long-standing issues surface at once: duplicates violate uniqueness rules, missing or inconsistent units of measure and packaging collide with configuration, and identifiers such as manufacturer, catalog number, GTIN, UNSPSC, HCPCS, and implant flags turn out to be incomplete. The volume of hospitals navigating this challenge right now is substantial. According to the KLAS 2025 Acute Care EHR Market Share Report, 272 U.S. hospitals were impacted by an EHR or system purchase decision, including migrations, in 2024 alone, following 319 hospitals the year prior. Every one of those migrations carries item master risk. When data problems are not resolved before go-live, they do not stay contained to IT: incomplete packaging hierarchies cause scan failures at the point of use, missing HCPCS codes create billing gaps, and unresolved duplicates break workflows that clinical and supply staff depend on from day one. As Becker's Hospital Review has noted in its analysis of ERP standardization in healthcare, an ERP is only as good as the data that resides in it. Addressing these issues before build and testing begins is the only way to use the migration as an opportunity to reset standards rather than carry every existing problem into a system that will make them harder to fix.
Define The Target Data Model First
Before cleansing, you need a clear view of what the new ERP and related systems expect from each item record. A target model defines the minimum safe data set for day-one operations and keeps the project focused on what matters for go-live.
For a cloud ERP and point-of-use implementation, a practical model includes:
Unique standardized descriptions that support search and preference cards
Validated manufacturer names and catalog numbers
Correct units of measure with complete packaging hierarchies
GTINs for scanning and UDI compliance
UNSPSC codes for spend categorization
HCPCS and billing attributes for separately billable supplies and implants
Clinical flags including sterile, implantable, latex, bone or tissue, and sharps safety
Defining this target model early determines which fields must be ready for migration and which can be backfilled post go-live, keeping cleansing effort aligned with ERP and point-of-use requirements rather than spreading across low-value fields. Grant Thornton's analysis of cloud healthcare ERP adoptions identifies consistent, rich, and contextual data in a unified platform as the foundational requirement for the analytics, automation, and cross-functional decision-making that health systems expect from cloud ERP investments.
Resolve Duplicates And Standardize Descriptions
Cloud ERPs typically require unique item names and discourage multiple records for the same product. That forces decisions on duplicates and inconsistent descriptions that legacy systems allowed for years.
Preparation work should identify and resolve item-level duplicates where the same product appears under multiple item numbers, address description duplicates where different items share the same vague label, and apply controlled naming conventions so descriptions are consistent and informative across categories. In one academic health system engagement, Symmetric resolved 2,747 duplicate items and updated 40,918 unique descriptions as part of item master preparation for a cloud ERP and point-of-use implementation, eliminating conflicts with ERP uniqueness rules and improving findability for clinicians and supply staff. The data quality work done before migration is what prevents the rework and extended timelines that, according to Gartner, cause the majority of the 83% of migration projects that fail or exceed budget.
Fix Packaging And Units Of Measure Before You Move
Once items have transactions in a new ERP, many systems lock packaging levels and units of measure or require complex workarounds to change them. That makes pre-migration the best moment to correct packaging errors and incomplete hierarchies.
Key steps include completing packaging hierarchies from each to case with accurate counts, aligning units of measure with how products are ordered, received, and used at the point of care, and adding GTINs at each relevant packaging level to support scanning and point-of-use capture. In the academic health system engagement, Symmetric cleansed and standardized 98,085 GTIN and packaging records in 60 days so the hospital could implement both a cloud ERP and a point-of-use system without being constrained by bad packaging data. Clean packaging records at go-live directly reduce receiving errors, scan failures, and inventory discrepancies that otherwise require manual correction after cutover. INTEGRIS Health, Oklahoma's largest not-for-profit health system, reported measurable increases in inventory costing accuracy after migrating to Oracle Cloud ERP, with PwC citing the accuracy of data conversion and process standardization as central to the implementation's success.
Enrich With Codes And Clinical Attributes
Modern ERPs and EMRs rely on structured codes and attributes to drive workflows, analytics, and billing. If your item master lacks these fields, you lose functionality and create manual maintenance work during and after migration.
As part of ERP readiness, hospitals should enrich items with UNSPSC for category structure and reporting, HCPCS for billable items such as implants and outpatient supplies, GMDN and other clinical descriptors for comparability and documentation, and flags for implantable, sterile, latex, bone or tissue, sharps safety, and similar clinical properties. In the academic health system engagement, Symmetric added or updated:
15,721 UNSPSC codes
60,751 HCPCS codes
70,210 GMDN terms
Thousands of clinical flags for implant, sterile, latex, bone or tissue, and sharps safety status
The business case for getting these codes right before migration is significant. The HFMA has estimated hospitals can lose 1 to 5% of net revenue due to incorrect or incomplete coding, meaning a system billing $500 million annually stands to lose $5 to $25 million from coding errors that structured pre-migration enrichment is designed to prevent. Enriching before go-live means the new ERP and point-of-use systems work from richer data on day one rather than requiring months of post-launch cleanup.
Validate Changes And Involve Stakeholders
Data cleansing for an ERP migration cannot happen in isolation. Supply chain, clinical, finance, and IT stakeholders need to see and validate proposed changes before they load into the new system.
A structured validation process imports the hospital's item master into an enrichment platform, matches it against a large product database, and generates reports on barcode quality, UNSPSC, HCPCS, duplicates, and other issues so teams see the full problem set clearly. Core enrichment fields are defined with the hospital's team, a full report of proposed changes is prepared for review and approval, and only after validation does the hospital receive a final enriched file for batch updates into the new ERP. This approach reduces surprises and builds confidence among end users before they ever log into the new system. Healthcare organizations that underestimate data migration complexity consistently see their implementations slow or fail during testing, not because the software does not work, but because bad data surfaces at the worst possible moment in the project timeline.
Plan For Go-Live And Ongoing Maintenance
Preparing for migration is only part of the work. New ERPs and EMRs will receive new products, packaging changes, and regulatory updates over time, and without an ongoing maintenance plan, data quality will decay and erode the gains made during migration preparation.
Long-term integrity depends on ongoing enrichment feeds that keep item masters synchronized with real-world product changes, tools that allow supply chain teams to look up item data and review maintenance reports, and API integrations with cloud ERPs that keep product data aligned across systems as catalogs evolve. In the academic health system engagement, Symmetric onboarded an eight-person team onto its platform after the initial cleanse so they could keep the item master prepared as both the ERP and point-of-use implementations progressed.
How Symmetric Health Solutions Accelerates ERP Migrations
Symmetric Health Solutions is built to make ERP and EMR migrations safer and faster by focusing on product data readiness. Its ERP and EMR transformation capabilities combine a large healthcare product database, proprietary matching technology, and healthcare-specific cleansing logic to deliver migration-ready item masters. Across projects, Symmetric has:
Cleansed and standardized tens of thousands of GTIN and packaging records in weeks
Resolved thousands of duplicate items and updated tens of thousands of descriptions to meet ERP standards
Enriched item masters with UNSPSC, HCPCS, GMDN, and critical clinical flags for new workflows
Integrated enriched data with cloud ERPs through pre-built APIs that reduce manual loading and mapping
Symmetric also supports master data management after go-live, providing ongoing enrichment feeds and integration tooling so the item master remains accurate as products, packaging, and regulatory standards change. The combination of pre-migration readiness work and post-launch maintenance is what separates health systems that realize the value of their ERP investment from those that spend months after cutover correcting data problems that could have been resolved before the system ever went live.
