LunaLabs

Data infrastructure · 2025

Workbook Conversion

A migration guide, generated from the workbook itself.

Platform migration is usually quoted from a guess. This tool replaces the guess with an extraction: everything in the workbook is enumerated into a single structured document, calculated fields are translated into the target formula language, chart types are mapped to their nearest equivalents, and the residue — the things with no clean translation — is listed explicitly rather than discovered halfway through.

Status
Shipped
Domain
Migration tooling
Role
Author
Year
2025

Stack

  • Python
  • Document API
  • Formula translation
  • Desktop GUI

A tool that extracts the complete contents of an analytics workbook — sources, fields, calculations, worksheets, dashboards, parameters — and generates a step-by-step migration guide to a competing platform, including formula translation.

01

Complete extraction, one document

Metadata, connection details, custom queries, relationships, every field with its datatype and role, calculation dependencies, worksheet encodings and filters, dashboard layouts and actions, parameters with their allowed ranges — all consolidated into one structured output rather than scattered across reports.

One file means one thing to diff when the workbook changes.

02

Complexity assessed, not asserted

Calculation dependency depth and encoding complexity are scored to produce a migration difficulty estimate.

The output includes what cannot be translated automatically, which is the part of a migration estimate that is normally missing and always expensive.

03

The residue is the estimate

Ninety percent of a workbook translates mechanically and contributes almost nothing to the cost of a migration.

The estimate is set entirely by the remainder — the platform-specific calculations, the layout behaviours with no equivalent, the data-source features that do not exist on the other side. Listing that residue explicitly, up front, is the difference between a quote and a discovery.

04

Built for the person doing the migration

The operator is usually an analyst rather than an engineer, so the tool ships as a desktop interface producing a readable guide rather than as a library producing a data structure.

That constraint shapes the output: step ordering, connection setup written out in full, and a difficulty rating that a project manager can act on without reading the workbook themselves.

Pipeline

Extraction to estimate

Stage Can reject

  1. 01

    Workbook

    Source file

  2. 02

    Enumerate

    Every field and view

  3. 03

    Dependency graph

    Calculation order

  4. 04

    Translate

    Target formulas

  5. 05

    Residue

    Untranslatable list

    This sets the estimate

  6. 06

    Guide

    Step-by-step migration

Skills exercised

What the build
actually demanded.

Against the corpus · 15 systems

  • Stack breadth 4
  • Design decisions 4
  • Pipeline stages 6
  • Decision gates 1

This system Corpus median

Translation

  • Source-to-target formula language conversion
  • Chart-type and encoding equivalence mapping
  • Dependency graph construction across calculated fields
  • Explicit identification of untranslatable constructs

Tooling

  • Complete workbook enumeration into one document
  • Complexity scoring for effort estimation
  • Connection and credential setup generation
  • Desktop interface for non-technical operators

What it establishes

  • Single consolidated output

    Everything in one structured document

  • Formula translation

    Calculated fields converted to the target language

  • Explicit residue

    Untranslatable items listed up front

  • Analyst-operable

    A desktop tool producing a readable guide