06-reference/research

mainframe snowflake cdc partner motion

2026-10-07·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
mainframe-modernizationsnowflake-partner-ecosystemchange-data-capturephdata-pipelinevendor-landscape

Mainframe-to-Snowflake CDC: The Tooling Lane Exists, the Snowflake Partner Motion Does Not

The question

"What is the current tooling landscape for mainframe-to-Snowflake CDC, and does Snowflake have a named partner motion here (Precisely, Qlik, Informatica, Fivetran HVR)?"

Derivative of [[2026-07-26-cobol-mainframe-ai-migration-phdata-pipeline]], whose recommendation was coexistence (offload mainframe transaction data into a governed cloud fabric rather than attempt a z/OS exit). This brief tests whether that recommendation is deliverable through tooling that already exists, and whether it is routable through a lane Snowflake itself publishes.

What we already know (from the vault)

What the web says

On tooling (priority 1):

On a named Snowflake partner motion (priority 2 - the half the question turns on):

On the practical shape (priority 3):

Convergences and contradictions

Synthesis for RDCO

Verdict: PARTIALLY. A delivery lane exists; a Snowflake-named partner lane does not. Split the two, because the parent brief's recommendation depends on them differently.

On deliverability, the parent brief's coexistence recommendation gets stronger. The hard part of mainframe-to-Snowflake CDC is a bought capability, not a built one: Precisely Connect and Qlik Replicate are mature, enterprise-procurable products that read DB2 for z/OS, IMS and VSAM and land to cloud targets, tcVISION covers the widest source list including Adabas and IDMS, and the Snowflake-side landing is now Snowflake's own product (Openflow, or Snowpipe Streaming behind Kafka). What remains for a data-and-AI SI is precisely the work phData already does: copybook-to-relational modeling, EBCDIC and packed-decimal handling, semantic layer, governance, and the analytics and agent workloads on top. The offload phase is not a mainframe-skills engagement wearing a data-engineering costume; it is a data-engineering engagement with one bought connector at the edge.

On routability, the recommendation gets weaker, and this is the finding worth carrying. There is no Snowflake mainframe program to attach a deal to. Snowflake's named motions - LiftOff, Migration Accelerated Partners, SnowConvert - are shaped for warehouse and Hadoop migrations, and their account-mapping, funding and co-sell mechanics are built around that shape. A mainframe-source opportunity has to be re-framed into one of those existing containers to get Snowflake-side attention, or routed through the ISV's own partner organization (Precisely and Qlik both run their own SI channels), which is a different and slower motion. The honest version of the parent brief's claim is therefore: coexistence is a deliverable engagement that currently has to be sold as a generic migration, not as a named mainframe play. That is a meaningful downgrade from "routable deal path" to "deliverable but unlabeled."

The competitive read is the part that should change behavior. IBM owns the mainframe, owns IBM InfoSphere Data Replication, describes mainframe application modernization on its own Snowflake partner profile, and - per [[2026-09-07-midmarket-snowflake-si-competitor-set]] - owns Hakkoda, which just won an AMER Snowflake Services award. If Snowflake ever does name a mainframe motion, IBM is the overwhelmingly likely anchor partner, and the lane arrives pre-occupied. Combine that with Slalom's "Zero Legacy" flag from [[2026-06-28-snowflake-si-cortex-positioning-caf-gap]] and the strategic conclusion is: this is a capability to be quietly competent at when an account surfaces it, not a category to claim. That also fits the founder's actual role constraint - a DSA pointing an existing account at a known-good tool chain is exactly the right size of move; building a named mainframe offering is not his job and would collide with the no-clients, no-selling-services rule.

What a DSA can actually use from this, as a one-screen routing note: if a Snowflake account names a mainframe source, the tool conversation is Precisely Connect or Qlik Replicate for DB2 z/OS, IMS and VSAM (tcVISION if Adabas, IDMS or Datacom appear), the landing is Openflow or Snowpipe Streaming behind Kafka, the first technical question is "do you have current copybooks," the first commercial question is "who owns the mainframe MIPS budget," and the first program question is "which Snowflake migration motion can this be framed into," because there is no mainframe one. phData's own Snowflake partner standing on mainframe or on any of these ISVs is [UNKNOWN] - nothing in Snowflake's public directory or phData's public material establishes a mainframe specialization or a named Precisely/Qlik alliance, and it should not be asserted. Confirming it is an internal action, not a research question.

Why this is in the vault

It resolves the fifth open follow-up of [[2026-07-26-cobol-mainframe-ai-migration-phdata-pipeline]] with a split answer that changes that brief's confidence in opposite directions: it upgrades the coexistence recommendation's delivery feasibility (the CDC capability is buyable, from named and dated products) and downgrades its go-to-market claim (there is no Snowflake-named mainframe lane, so the parent brief's hoped-for "routable deal path" does not exist as such). It also supplies the three stale-name hazards that would cost credibility in an account conversation - Attunity, Ironstream-as-CDC, and Db2-for-i mistaken for Db2-for-z/OS.

Open follow-ups

Related

Sources

Vault

Web - primary-fetched 2026-10-07

Web - search-result level, not primary-fetched (treat as leads)

Not consulted