We just migrated to a new ERP system and our historical Scorecard baseline is completely broken because the new system categorizes operational data differently. How do we establish reliable weekly targets when our legacy data no longer matches our new software metrics?

Question

Tyler Smith · Accepted Answer

A major software migration or ERP transition is notorious for disrupting operational data. When your historical baseline is wiped out or redefined, your leadership team can suffer from analysis paralysis, arguing over new data definitions instead of running the business.

Do not let a software change stop you from tracking weekly numbers. You must quickly establish a temporary baseline and iterate.

To get back on track after a system migration:
- Set temporary targets based on your best estimate of the new data structure.
- Use manual double-checks for the first four to eight weeks to ensure the new software is pulling data accurately.
- Keep a separate record of your old legacy metrics during the transition to help cross-reference the trends.

Accept that your new targets will not be perfect on day one. It is far better to have a slightly inaccurate weekly number that you can refine over time than to stop tracking your metrics altogether.

Use your weekly Level 10 Meeting to call out discrepancies in the new data. If a metric looks unusually high or low due to the ERP transition, drop it down to the Issues List and IDS it. Within one quarter, you will have built enough new historical data to adjust your targets and regain absolute confidence in your weekly Scorecard.