Migrating from Legacy Dashboards

If you have existing Labguru Dashboard reports, they will not carry over to Analytics automatically. The two are built on fundamentally different technology, so each report needs to be rebuilt rather than imported.

The good news is that rebuilding is usually straightforward, and often an improvement — many legacy dashboards were built around workarounds for limitations that Analytics does not have.

What can be reused

• The underlying question each report answers — what it measures, how it is grouped, and which records it covers — carries over directly and is the main thing worth preserving.
• If a legacy dashboard was built on a custom SQL query, that query is a useful reference for what the report is trying to show, even though it cannot be pasted into Analytics as-is.

What needs to be rebuilt

• Chart types, table layouts, and styling are not portable and will need to be recreated using the chart library described in Creating Visualizations.
• Legacy queries were often written directly against Labguru's underlying database, sometimes working around missing fields with custom SQL logic. Analytics queries are built on top of curated topics rather than raw database tables, so a legacy query is a starting point to rebuild from, not something you can copy in directly.

Tip. Rather than migrating every old dashboard, use this as a chance to review what your team actually still relies on. Rebuilding a report from scratch in a workbook, using the topic that best matches it, is usually faster than trying to reverse-engineer an old query.

If you have a legacy dashboard you would like help rebuilding in Analytics, contact Cenevo Support or your account representative.