BLOG — LOSS PREVENTION    ·    11 min read ERP Transitions and Shrink: What Happens in the First 90 Days and How to Control It The window between system cutover and stable inventory data is when the most preventable losses occur. Here is what actually happens — and how to manage it.

By Mitchell Hamm  |  Founder & Principal Advisor, Ironside Risk Advisors  |  Dallas, TX

I have been through a full ERP system transition at scale. Not as a consultant who reviewed the process documentation. As the person responsible for maintaining 0.419% inventory shrink across more than 150 retail and distribution locations while the business moved from one enterprise resource planning system to another.

I can tell you from direct experience that an ERP transition is one of the highest-risk operational events a multi-location retailer can go through from an inventory integrity standpoint. Not because the transition is inherently flawed. But because the window between when the old system goes offline and when the new system is producing reliable, reconciled inventory data is precisely when shrink accumulates invisibly — and when the controls that would normally catch it are temporarily degraded or absent.

This post is about what actually happens during that window, why it matters disproportionately in a PE context, and what the Loss Prevention program needs to do to manage it.

Why ERP Transitions Are a Shrink Event

Data Migration Errors Create Phantom Inventory

Every ERP migration involves moving inventory records from the old system to the new one. In theory, the opening balances in the new system should match the closing balances in the old system exactly. In practice, data migration introduces errors. Units of measure mismatches. SKU mapping failures. Duplicate records. Products that exist in the old system that were not cleanly migrated to the new one.

The result is phantom inventory — quantities in the system that do not exist on the shelf, and sometimes quantities on the shelf that are not in the system. Some of these errors are caught immediately during the parallel run phase. Many are not discovered until the first cycle count or physical inventory under the new system, at which point the variance is indistinguishable from actual loss.

Receiving Procedures Break Down

The receiving module is almost always one of the most disruptive components of an ERP transition. Receiving staff who have spent years in the old system’s workflow are suddenly operating in a new interface with different screens, different procedures, and different error messages. The institutional knowledge that lived in ‘how we’ve always done it’ does not transfer automatically.

In this disruption window, receiving accuracy degrades. Items get received at the wrong quantities. Purchase orders get closed with variances that would have been caught in the old system. Products arrive and are stocked without being received in the new system at all. Every one of these errors creates an inventory discrepancy that will show up as shrink when the first count happens.

Reporting Goes Dark

Every business has reports it relies on to monitor inventory health — variance reports, receiving discrepancy reports, negative inventory alerts, and shrink reports. In the old system, these reports existed, even if they were imperfect. In the new system, they need to be rebuilt. Until they are, the visibility that existed — however imperfect — is gone.

During an ERP transition, there is frequently a period of weeks to months where the reporting infrastructure is not fully functional. No one is watching the numbers. Variances accumulate undetected. Internal theft that would normally trigger an exception report goes unnoticed because the exception report does not exist yet.

The ERP transition creates a window where receiving errors are invisible, reporting is dark, and the normal controls are degraded. That is the window when shrink accumulates.

What the Loss Prevention Program Needs to Do

Before Cutover

The most important Loss Prevention action before a system cutover is a full physical inventory count conducted in the old system immediately before migration. This creates a clean, documented baseline that can be compared against the opening balances in the new system — and any discrepancy between the two becomes a data migration error to investigate rather than shrink to write off.

Document this count obsessively. Date, location, counter identity, methodology. If a discrepancy surfaces six months later between what was on the shelf at cutover and what the new system shows, the pre-migration count is your reference point.

During the Transition Window

Increase cycle count frequency during the transition window. Double the standard cadence for high-value and high-theft categories. The receiving module is degraded, reporting is limited, and the normal Loss Prevention controls are stretched — which means the cycle count is the primary remaining mechanism for identifying losses in real time.

Increase receiving oversight. Loss Prevention or management should be physically present at receiving docks during the first 30 days after cutover. Not because the staff cannot be trusted, but because the process is unfamiliar and errors are inevitable. Catching a receiving error the day it happens is exponentially easier than reconstructing it six weeks later.

Implement manual receiving logs as a backup. Until you have confidence that the new system is capturing receiving transactions accurately, maintain a paper or spreadsheet log of every inbound shipment — vendor, quantity, receiver, date. This creates an independent record that can be reconciled against the system when discrepancies surface.

After Cutover — The First 90 Days

The first 90 days in the new system are the diagnostic period. Every variance that surfaces during this period has three possible explanations: it is a data migration error, it is a receiving error caused by the transition, or it is actual loss. The Loss Prevention program’s job is to distinguish between these categories — because writing off data migration errors as shrink overstates the loss, and closing them without investigation misses actual theft patterns that may be exploiting the transition window.

• Run the first full cycle count in the new system within 30 days of cutover. Compare results against the pre-migration baseline. Document every variance and assign it a root cause category.
• Rebuild all Loss Prevention-relevant reports in the new system as the first configuration priority — before marketing reports, before financial reports, before operational analytics. The exception reports and variance alerts are not optional.
• Conduct a reconciliation review of the receiving module within 60 days. Pull a sample of 50 receiving transactions from the first 30 days post-cutover and verify them against vendor invoices, physical delivery records, and system entries. Quantify the error rate.
• Brief the LP team and location managers on the elevated risk environment. The transition window is when opportunistic theft is most likely to go undetected. Staff awareness that LP oversight is heightened — even if the systems are temporarily degraded — is a deterrent in itself.

The PE-Specific Risk

ERP transitions in PE-backed businesses carry an additional layer of risk: they frequently happen in the first 18 months post-acquisition, when the PE firm is also integrating the business into its reporting structure, changing management, and implementing operational improvements across multiple functions simultaneously. The Loss Prevention program is usually not the top priority in this environment.

The consequence is that the transition window — already the highest-risk period from an inventory integrity standpoint — occurs when Loss Prevention bandwidth is at its lowest. The result is often the inventory variance discovery that happens 18 months post-close. The fund’s operating partner asks how this was missed. The honest answer is that it happened during the ERP transition, when the controls were down and nobody was watching.

Preventing this requires explicitly resourcing the Loss Prevention function during the transition period — not pulling Loss Prevention staff to support the migration project, maintaining or increasing cycle count cadence, and treating the transition window as an elevated-risk period rather than a normal one.

A Note on What Worked

In the transition I managed across 150+ locations, the combination of a pre-migration physical count, doubled cycle count cadence during the 90-day transition window, manual receiving logs at every dock, and daily Loss Prevention presence at the highest-volume receiving locations held shrink at 0.419% through the migration — essentially flat with the pre-migration rate. Not because the transition was smooth. It was not. Because we treated it as an Loss Prevention event, not just a technology event.

The transition will introduce errors. The data migration will produce discrepancies. Receiving staff will make mistakes in an unfamiliar system. The question is whether those errors surface in real time, when they can be investigated and corrected, or six months later, when they have compounded into a variance report that looks like a theft problem but is actually a process problem from the first two weeks of the new system.

That distinction — real-time visibility versus lagging discovery — is what the Loss Prevention program is for. Make sure it is resourced to do its job during the period when the risk is highest.

IRONSIDE NOTE

ERP migration Loss Prevention planning is a standard component of Ironside’s Post-Acquisition Loss Prevention Buildout engagement. If your portfolio company has a system migration planned in the next 12 months, contact Ironside before the migration timeline is set — not after the cutover.

About Ironside Risk Advisors Ironside Risk Advisors provides fractional loss prevention and cargo security advisory to private equity firms with retail and supply chain portfolio companies. Founded by Mitchell Hamm — 10+ years across a PE-backed multi-site retail operator and corporate security — the firm specializes in pre-acquisition risk assessment, post-close Loss Prevention buildout, and ongoing fractional Loss Prevention leadership. mitch@ironsideriskadvisors.com  ·  (502) 608-7389  ·  ironsideriskadvisors.com  ·  Dallas, TX