Skip to main content
Cube and Credible share a worldview: a governed layer of measures, dimensions, and joins over your warehouse, queried by intent rather than raw SQL. That makes migration clean — Credible reads your Cube data model and rebuilds it as Malloy, keeping the semantics and shedding the engine-specific tuning.

What Credible Reads

Your Cube data model — cubes and views authored in YAML or JavaScript. Point the agent at those files and it has everything it needs to translate. Connecting Cube’s MCP server (hosted per tenant over OAuth) or its SQL/REST/GraphQL APIs is optional: it lets the agent read the governed catalog directly and validate results against the live model.

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 model, translates cubes to base sources and views to curated sources, enriches each field with #(doc)/#(index) tags, and — where you connect it — validates row-by-row against Cube’s SQL API.

What Credible Handles

  • Pre-aggregations accelerate the engine but carry no semantics — Malloy queries the warehouse live, so rollup caches are dropped. Parity is checked against raw data (a stale pre-agg can differ from the source of truth).
  • JavaScript-defined models — dynamic cubes and templated generation are read through Cube’s SQL/REST metadata rather than static file parsing.
  • Data access policies (member-level security, queryRewrite) map to Malloy access control rather than a 1:1 mechanism.

Before & After

More than a reformat. The model queries live data (no pre-aggregation staleness), is AI-discoverable through the Context Engine, and serves agents, apps, and BI — not just Cube’s APIs. See what you gain →

Next Steps

Migration Overview

The method behind every migration

Publishing

Package and publish your migrated model