You name up to three of the metrics a leader asks about by name. Each one gets pinned to exactly how your own ERP calculated it before the migration, then checked against how it calculates now, after an Epicor on-prem → Kinetic move.
What comes back is a written opinion: what each number means, whether it held, and where it moved. Independent, because it was checked by someone with no stake in the migration looking clean. Documented, so it stands up when someone asks how you know.
That opinion answers the questions a COO actually has. Can I trust today’s inventory on hand. Can I quote this unit cost and stand behind it. Can I promise the ship date this schedule implies. Are the production numbers on this report the production that actually happened. You get the answer as evidence, not as reassurance.
A metric is a definition computed over data, and that computation lives inside the system. Move the system and you have quietly moved the computation. The single-number measures usually survive. The fragile ones are the ratios: OEE, on-time %, scrap rate, utilization. Each depends on how both halves are derived, and that derivation is exactly what changes underneath.
The drift hides behind numbers that still look plausible, so nobody catches it until it is wrong in front of leadership. Independence is the structural thing an in-house analyst cannot provide about their own migration, and it is the whole point of bringing in an outside check.
- Pin the definition. Establish exactly how each chosen metric was defined in your own system before the move, every term in the numerator and denominator, so the comparison is against your own history, not an outside framework.
- Compute on both sides. Run the same definition against the on-prem source and the Kinetic target while both are still available to compare, so the result is a real comparison and not a reconstruction.
- Document the difference. Where a number held, say so. Where it drifted, show by how much and why: which table, which logic, which assumption moved.
- Hand you something defensible. A written record showing what held and what didn’t, checked by someone outside your team, that you can put in front of leadership and stand behind.
Synthetic data below, built to illustrate the mechanism, not a real customer engagement. Three metrics, checked against the same shop’s own pre-migration numbers.
The row counts matched on every metric. Same records in, same records out. The OEE gap traced to the availability denominator: the on-prem calculation excluded scheduled maintenance windows, the Kinetic default doesn’t. Same metric name, same rows, different math. That’s the kind of drift Verify is built to catch.
Verify checks the numbers you already suspect. It is narrow on purpose. It does not walk every operational field to catch the thing you didn’t think to name, and it is a reading from one day, not a watch over time.
When you want the whole move checked while both systems are still up, that is OIM Validate. When you want the numbers watched so drift gets caught before it becomes a dispute, that is OIM Vigil. What you spend on Verify carries forward to Validate.
My First Migration
A period of operational distress exposed a leadership reporting tool held together by macros. I said I’d figure it out. Eight weeks later I had a working replatform. It took months more to earn the trust that made it real.
Read the Fieldbook →