We are migrating our core operations to a new software platform next month and our team warns that our historical scorecard data will be temporarily broken or unavailable. How do we maintain our weekly scorecard discipline during a major systems transition?

Question

Tyler Smith · Accepted Answer

A major systems migration is a common excuse for teams to abandon their weekly scorecard discipline. They claim that because the old data is locked away and the new system is not fully calibrated, tracking numbers is impossible. This is a dangerous mistake that can blind your leadership team during a high-risk transition.

During any software migration, you must maintain your weekly scorecard, even if you have to gather the data manually. If your automated dashboards are offline, the metric owners on your Accountability Chart must physically count and verify their weekly numbers.

If certain advanced metrics are truly impossible to pull, you must temporarily swap them for simpler, activity-based proxies. For example, if you cannot pull your exact pipeline value from your new CRM, track the raw number of sales meetings held or proposals sent.

The goal of the scorecard is to maintain a continuous pulse on the business. If you stop tracking your numbers for a month, you lose your ability to spot issues early, precisely when system glitches are most likely to disrupt your customer service and billing.

Keep the targets realistic but do not stop measuring. Once the new system is fully operational, you can transition back to your automated data sources. Maintaining this discipline ensures your team remains accountable and your operations do not slip into chaos during the technology change.