Engagement · Rebuild (scope-priced)
Migrate Clean
“Move us to Snowflake without carrying the tech debt across.”
Most migrations move the mess. We read the warehouse you have, re-architect it on the way over, and deliver it on Snowflake with the debt named and left behind rather than ported.
In scope:
- Your legacy warehouse read and re-architected, not lifted and shifted
- The result delivered on Snowflake, run against your warehouse before handover
- A written list of what we did not bring across, and why
- Lineage for the rebuilt warehouse
What we need
- The source warehouse as a dbt project, a folder of SQL, or a Glue catalog
- A Snowflake target we can build into
- One named reviewer with a mandate
How long
Out of scope:
- The infrastructure cutover itself
- Dual-running the old and new warehouses
- Re-pointing your BI tools — we deliver the modelling layer
- Decommissioning anything
What we mean when we say tested.
We generate the models, run them against your Snowflake or Athena connection, and check that each one returns rows, that its primary key is unique, that no column comes back completely empty, and that the types are what we said they'd be. On top of that we run dbt's own generic tests — not-null, unique, accepted values, and foreign keys against their parent — and hand you the schema.yml for them, so the tests we ran are tests you keep. Where a test can't be evaluated soundly it comes back marked skipped, never passed. We don't run a full dbt build, and we don't compare your old numbers against the new ones row by row. If a figure has to reconcile exactly, that's a conversation for the call.
On engines
We test against the target, not the source. That is what makes this honest: the tested artifact lands on the Snowflake side. We read the code you hand us whatever engine it was written for — but we do not connect to a Redshift warehouse, so we cannot introspect it, profile its values, or read its query history the way the audit does on Snowflake. Intake for this engagement is your code, not a connection.
Not here yet
Scoped, no date We read and re-architect a Redshift warehouse and deliver it tested on Snowflake — that part works today. A direct Redshift connector is scoped but not built, so intake for this engagement is your code rather than a live connection.
Written in future tense on purpose. Anything on this list is something we intend to ship, not something you would be buying today.
Scope the engagement in thirty minutes.
Bring the domain that causes the most difficulty. If it turns out this is not the right engagement for you, we will say so and point at the one that is.