What Credible Reads
Your Sigma data models (Sigma’s first-class semantic layer, which supersedes the older datasets), plus the calculated columns and metrics embedded in workbooks — exportable as code (JSON, or YAML via?format=yaml). The agent works from that export. Connecting Sigma’s MCP server (OAuth, permission-inherited) or REST API is optional: it lets the agent search across data models and workbook elements to find logic that never made it into the central model, and validate the result.
What Comes Across
The everyday modeling carries over. Here’s how the bigger pieces land — and where they get better:The Migration Flow
Credible reads the data model and crawls workbook elements for embedded logic, translates tables to sources and formulas to dimensions/measures, enriches with#(doc)/#(index) tags, and — where you connect it — validates results against Sigma’s query engine.
What Credible Handles
- Workbook-embedded logic is the classic Sigma trap: the true definitions are often spreadsheet formulas duplicated across many workbooks, not the central model. Credible finds them, reconciles the drift, and hoists a single canonical definition into the Malloy source.
- Spreadsheet-formula semantics (Excel-like functions, row-level vs. aggregate context) are re-expressed as Malloy dimensions and measures, preserving whether each ran per-row or grouped.
- External semantic layers — if a workbook reads dbt Semantic Layer metrics or Snowflake semantic views through Sigma, the logic lives upstream; Credible migrates the upstream definitions, not the passthrough.
Before & After
A Sigma data model as code:Sigma’s code representation doesn’t cover every construct (input tables, Python elements, and some data-source-level metrics live outside it), so Credible supplements the model-as-code export with workbook and element inspection to capture the full picture.
Next Steps
Migration Overview
The method behind every migration
Metadata & Discovery
Tune your migrated model for AI retrieval