Work across more than one platform
Move a dbt project to a new destination and prove parity before cutover
- When the warehouse is changing and the dbt project has to follow it.
- When a dialect-specific function breaks the moment the project builds against the new destination.
Rebuild a dbt project against a new destination, surface every model that breaks on dialect, and compare each mart to the incumbent's output before any dashboard is repointed. Covers the move and its parity proof, not rewriting the semantics behind a dialect break.
Sample This Recipe has not been materialized in the Cookbook repository yet. Its trigger, description, prompt, agent guidance and acceptance conditions, and the explanation below, are prototype drafts. Its name, job, area and readiness come from the reconciled Cookbook seed snapshot. Readiness is a separate question from this one: it says whether the capability exists, not whether the writing has been reviewed.
Use this Recipe
Use the VibeData Recipe `move-dbt-project-destination` at https://getvibedata.ai/cookbook/move-dbt-project-destination Read the Recipe and execute it in the context of the current Intent.
Recipe id move-dbt-project-destination · Not yet materialized in the Cookbook repository, so the pointer addresses this page.
Verified by
What has to be observably true before this Recipe is finished.
- every model that fails to build on the new destination is listed with the dialect break that caused it
- each consumer-facing mart matches the incumbent's output within the agreed tolerance
- the project builds clean on the new destination in the sandbox before cutover
- no dashboard is repointed before its mart has been compared
Recipe promptThe task specification the agent reads. Reference only — it is not what you copy.
Deliver: Move a dbt project to a new destination and prove parity before cutover. Rebuild a dbt project against a new destination, surface every model that breaks on dialect, and compare each mart to the incumbent's output before any dashboard is repointed. Covers the move and its parity proof, not rewriting the semantics behind a dialect break. Execute inside the current Intent. Its Domain, repository, platform, environment and attached sources are the context for this work — read them rather than asking for them. The work is done when: - every model that fails to build on the new destination is listed with the dialect break that caused it - each consumer-facing mart matches the incumbent's output within the agreed tolerance - the project builds clean on the new destination in the sandbox before cutover - no dashboard is repointed before its mart has been compared Report the evidence for each condition above with the result. A condition you cannot meet is something to say, not something to work around.
Agent guidanceHow the agent approaches the work, and what it will not do.
Establish which platform is authoritative today and what in the project is platform-specific. Build against the target in an isolated copy and reconcile the two runs against each other before anything is cut over.
Composes
- dbt model authoring and layering
- dbt in the project
- isolated-copy execution and gate verification
Asks first
Semantic decisions the Intent cannot supply. Never context Studio already holds.
- which Fabric target this work lands on, when the Domain carries both a Lakehouse and a Warehouse
Guardrails
- Build in an isolated copy. Production is read, never written.
What you need
- Microsoft Fabric Lakehouse, Microsoft Fabric Warehouse, MotherDuck, or DuckDB.
- A dbt project you can build, and read access to the models it starts from.
- dbt in the project, or the intent to add it.
How it goes
- Name both platforms, and which one is authoritative today.
- Let it read what in the project is platform-specific and what is not.
- Review the plan before anything is rebuilt.
- Build and run against the target in an isolated copy.
- Reconcile the two runs against each other, at the grain the consumers read.
- Read the acceptance conditions before you cut over, not after.
What you end up with
The deliverable, in your own repository, as transformation work a reviewer who knows the project reads as native to it. Alongside it, the evidence for every one of the acceptance conditions above — which is the part that is still there in three weeks when somebody asks.