The starting point is always messier than expected
Most teams don't migrate from zero. They migrate from an accumulation of spreadsheets, dashboard notes, and tribal knowledge that's grown organically for years. Before building anything new, accept the first honest step: it isn't designing the perfect dictionary. It's inventorying the mess you already have, so nothing important gets lost in the shuffle.
Step 1: Collect every existing definition, even the bad ones
Pull every spreadsheet, dashboard, and doc that defines a metric your team reports on. Don't filter or clean up yet. Just collect. You're looking for every place a metric's been defined, including the ones that disagree with each other. Those disagreements are exactly what the migration needs to surface and resolve — not paper over.
Step 2: Merge duplicates and resolve conflicts explicitly
Where two sources define the same metric differently, don't silently pick one. Bring both to whoever owns the decision, note why the chosen version won, and write it down — a one-line rationale is enough. This is the step that stops the same fight from happening again in six months when someone rediscovers the version that lost.
Step 3: Assign an owner to every metric
A definition with no owner drifts the first time someone needs to change it under time pressure. Every metric in the new dictionary needs exactly one person or team responsible for it — not necessarily whoever calculates it day to day, but whoever approves changes to how it's calculated.
Step 4: Actually retire the old spreadsheets
The migration isn't done when the new dictionary exists. It's done when the old spreadsheets stop being a live reference. Link to the new dictionary from wherever the old ones lived, archive them clearly as historical, and treat any dashboard still pulling from a pre-migration definition as a bug. Not a legacy exception you just tolerate forever.
A realistic timeline
For a team with a dozen or so metrics scattered across three or four sources, collecting and resolving conflicts usually takes a focused afternoon. Not a project. Assigning owners is quick once definitions are settled. The step that actually takes longer than expected is retiring the old spreadsheets — not because it's technically hard, but because someone always has one old tab bookmarked, and it takes a few weeks of gentle redirecting before the new dictionary's genuinely the only place people look.
That tail is normal. The goal isn't a clean cutover in one day. It's making sure the new dictionary is unambiguously the more convenient place to look, so old habits fade out on their own instead of needing to be enforced.
Managing this across multiple clients instead of one internal function? Same playbook, per client — and the payoff compounds. A consistent migration process is itself a service you can point to when a client asks how their reporting actually gets maintained.
Worth running the same four steps again a year later, too. Even a dictionary that was clean at launch picks up its own small inconsistencies over time, and this playbook works just as well as a periodic tune-up as it does for a first cleanup.
How KPI Compass helps
This is the exact workflow KPI Compass is built around — so the migration doesn't live in a spreadsheet you have to hold together by hand. It ships with a built-in library of defined KPIs you adopt from, so you're editing a solid starting point instead of writing every definition from scratch. Your team's adopted set lives in one place, and each metric carries its owner, its certification status, and the data sources and dashboards it feeds.

Steps 2 and 3 of the playbook — resolving conflicts and assigning owners — stop being a document you maintain by hand. Every KPI gets a single accountable owner and a certification status on a review cadence, so "is this number right, and who signed off on it?" has a clear answer. When a metric goes stale, it flags itself as review due instead of quietly drifting.

And because the dictionary connects to your real data and BI dashboards, Step 4 — retiring the old spreadsheets — actually sticks: the governed definition becomes the more convenient place to look, not just the more correct one. You can start with a 30-day trial and adopt your first certified KPIs in an afternoon.
About the author
Zach Edelstein
Founder, KPI Compass
Zach has spent the last decade in data analytics, working both inside large media agencies and in-house at enterprise companies. He built KPI Compass because he kept hitting the same walls every BI team eventually hits — messy definitions, benchmarks nobody can verify, dashboards that quietly drift from reality. He's especially into where AI actually helps with this work, and he's still actively evolving KPI Compass to keep up with how fast the data landscape moves.
KPI Compass on LinkedIn