Products Solutions Templates Pricing Resources

Migrating to better dashboard tools: planning and execution

Home / Everything About / Everything About Analytics / Migrating to better dashboard tools: planning and execution

Company uses Google Sheets for dashboards. Works fine at five-person startup. Does not scale at fifty-person company.

Migrating from one tool to another is project. Requires planning.

Bad migration: switch all dashboards to new tool immediately. Team is confused. Data is wrong. Productivity drops. Chaos.

Good migration: plan, pilot, execute in waves, validate, sunset old tool. No disruption.

Why migrate

Current tool is slow

Load time is two minutes. Unacceptable.

Current tool does not scale

One hundred dashboards are too many to manage in Google Sheets.

Current tool lacks features

Cannot do real-time updates. Cannot do drill-down.

Current tool is expensive at scale

Seat cost becomes prohibitive at fifty users.

Current tool is not accessible

Mobile dashboards do not work. Team cannot view on phone.

When to migrate

Migrate when pain is unbearable

If current tool is working fine, do not migrate. Migration is disruptive. Cost is high. Stay with working tool unless strong reason to change.

Migrate when you hit tool limits

Google Sheets works for five dashboards. Fifty dashboards is limit. Consider migration at forty dashboards.

Migrate when team requests

If team is requesting migration (spending too much time working around tool limitations), migration is justified.

Migration process

Phase one (planning)

Choose new tool. Test with subset of dashboards. Validate new tool meets requirements. Timeline: one month.

Phase two (pilot)

Migrate five to ten dashboards to new tool. Test in production. Gather feedback. Timeline: one month.

Phase three (full migration)

Migrate remaining dashboards. Build new dashboards in new tool. Deprecate old tool. Timeline: one to three months depending on dashboard count.

Phase four (sunset)

Old tool is archived. Team uses only new tool. Support for old tool ends. Timeline: one month.

Total timeline

Four to six months for full migration.

Real example: Looker migration

Phase one (planning)

Company currently uses Google Sheets for dashboards. Evaluate Looker, Tableau, Mode. Choose Looker. Cost is thirty thousand per year (one hundred fifty per seat times two hundred seats). Benefits: real-time updates, drill-down, mobile support, better performance. Cost is acceptable.

Phase two (pilot)

Migrate five dashboards (executive, sales, marketing, product, operations). Team uses Looker for one month. Feedback: Looker is faster (good), learning curve is steep (expected), queries are complex to set up (one-time cost). Pilot is success. Go to full migration.

Phase three (full migration)

Move remaining forty-five dashboards over six weeks. Create team of three people (one per week) to migrate dashboards. Existing dashboards in Google Sheets are disabled. New dashboards in Looker are enabled. Queries are set up for each metric.

Phase four (sunset)

Google Sheets dashboards are removed. Google Sheets dashboard folder is archived. Team uses only Looker. Support for Google Sheets questions ends.

Result

Migration took five months. Cost was forty thousand dollars (thirty thousand Looker plus ten thousand implementation). Benefit: dashboards are faster, more reliable, more scalable. Payoff in one year.