Fivetran HVR vs Qlik Replicate

Quick verdict

Fivetran HVR (High-Volume Replicator, now HVR 6) is described by Fivetran as "a self-hosted version of Fivetran" for enterprise replication. An HVR Hub Server, with a repository database holding the replication definitions, schedules capture, integrate, refresh and compare jobs; optional HVR Agents on source or target machines connect to the hub over TLS. HVR 6.3 reached general availability on 11 December 2025 with regular support until 31 December 2028. It is sold on one plan, Business Critical, and the hub registers with a Fivetran account for its licence.

Qlik Replicate (formerly Attunity Replicate) is Qlik's client-managed CDC engine. A Replicate server on Windows or Linux runs tasks that perform a full load and then read the source transaction log, forwarding each committed transaction to the target; tasks are designed and monitored in a web console. The May 2026 release adds IMS as a native source and Db2 LUW, Cloudera Iceberg and Oracle ATP targets.

Side by side

Key differences

Hub and agents versus a replication server

HVR is designed around a central hub and distributed agents. Agents can run on the source or target machines (including AIX and Solaris) and connect to the hub over TLS; capture reads the source transaction logs, compresses and optionally encrypts the changes, and routes them through the hub to the integrate side. That suits estates with many sources across data centres or networks, where you want capture close to each database and a single point of control. The hub needs its own repository database and must be registered with a Fivetran account.

Qlik Replicate centres on a Replicate server that connects to source and target endpoints and runs tasks; the web console on the same server is used to design and monitor them. For many servers, Qlik sells Qlik Enterprise Manager separately. The mainframe route is native endpoints for Db2 for z/OS and, from May 2026, IMS, which replaces the legacy Attunity Replicate Connect (ARC) agents. In practice both can cover a multi-site estate; the question is whether you prefer HVR's agent topology or a set of Replicate servers under Enterprise Manager.

Source coverage

Both cover the core enterprise databases: Oracle, SQL Server, Db2 on all three platforms, SAP HANA, PostgreSQL, MySQL, MariaDB and Sybase ASE. The documented differences are at the edges. HVR lists SAP NetWeaver on HANA or Oracle (capture only), Ingres and YugabyteDB, and its agents run on AIX and Solaris. Qlik Replicate lists IMS, Informix, MongoDB and Salesforce as sources and SAP application sources. If any of those is on your list, it may decide the choice before price does.

Applying and verifying changes

Qlik Replicate documents two change processing modes. Transactional apply applies each transaction individually, in commit order, which keeps strict referential integrity; tables without a primary key or unique index always use it. Batch optimized apply groups changes into batches for throughput, which Qlik says may affect transactional integrity, and it is not supported for tables with foreign keys. Choose per task based on whether the target is an operational database or an analytics store.

HVR's documented differentiator here is verification: compare jobs check whether source and target hold the same data, next to refresh jobs that load or reload targets. For regulated or high-value replication, a built-in compare reduces the need for separate reconciliation scripts. A simple manual check of the kind compare automates looks like this:

-- Quick row count and checksum on source and target (SQL Server)
SELECT COUNT(*)                           AS row_count,
       CHECKSUM_AGG(BINARY_CHECKSUM(*))   AS table_checksum
FROM dbo.orders;

Pricing: Monthly Active Rows versus endpoint licences

HVR is sold only on Fivetran's Business Critical plan, which allows on-premises deployment. Fivetran defines MAR for HVR as "the number of distinct primary keys synced or replicated from a source location to a target location" in a calendar month, and says that when one source feeds several destinations, MAR is counted for each destination. Tiers apply per channel, so the cost per MAR falls as a single channel grows. No rate is published; Fivetran points to its estimator. The older Private Deployment plan is deprecated.

Qlik Replicate has no published price: client-managed products are sold through sales, and the endpoints you can use depend on your licence. In our view, MAR billing tracks how much data changes, which favours large but slow-changing tables, while an endpoint licence tracks how many systems you connect, which favours a few very busy sources. Fan-out to several targets raises HVR's MAR and also adds target endpoints to a Replicate licence, so model both.

Pricing and licensing

Fivetran HVR. Per Fivetran's "Pricing for HVR" page, checked 7 November 2026: a single plan, Business Critical, billed by Monthly Active Rows (distinct primary keys replicated from a source location to a target location in a month, counted for each destination) with channel-level usage tiers. The hub's Fivetran registration supplies an automatically refreshing licence key; if registration is removed before the contract ends, access stops after seven days. No per-MAR price is published.

Qlik Replicate. No list price. Qlik's data integration pricing page shows only Qlik Talend Cloud editions with Contact Us and routes client-managed products through sales; Replicate licences are scoped to the endpoints you need.

Pricing checked on the vendors' official pages on 7 November 2026. Prices change; confirm before buying.

Where each one leads

Limitations

When to choose each

When neither is right

• You want vendor-run CDC with in-flight processing: see Qlik Replicate vs Striim.
• Your estate is Oracle-centred and you need active-active with conflict resolution: see Debezium vs Oracle GoldenGate.
• A managed connector service is acceptable: the main Fivetran service or Airbyte vs Fivetran may need less to operate.
• Your sources are mainly Db2 and IMS on IBM platforms: also look at IBM Data Replication.

Final recommendation

Frequently asked questions

Sources

• Fivetran HVR 6 documentation
• HVR 6 architecture
• HVR 6.3.5 capabilities
• HVR release life cycle
• Pricing for HVR
• Qlik Replicate supported source endpoints (May 2026)
• Qlik Replicate change processing tuning
• What's new in Qlik Replicate May 2026
• Qlik data integration pricing

Checked November 2026.

How we research comparisons: our editorial method.