Skip to main content

Product Transitions — Jet Analytics 20.10, Jet Analytics Data Integration, and Jet Analytics Classic

Originally published March 2025. This article describes the product transition from Jet Analytics 20.10 to Jet Analytics Data Integration and Jet Analytics Classic, and provides guidance for current 20.10 users on how to proceed.

Jet Analytics Classic — a focused solution for on-premises data warehousing

Jet Analytics Classic (released March 2026) is the successor to Jet Analytics 20.10, focused on on-premises and Azure SQL Database environments. It provides ongoing support and feature improvements for organisations that prioritise traditional, SQL-based data warehousing.

Note:

The Operational Data Exchange (ODX) has been deprecated in Jet Analytics Classic. Classic is designed for simplified on-premises environments that do not require cloud connectivity for the data ingestion layer.

Data source providers — CData and Jet Analytics Enhanced

Jet Analytics has developed a broad range of first-party Enhanced data source providers as a flexible and reliable alternative to CData providers. All Jet Analytics Enhanced providers developed for Jet Analytics Data Integration are also available in Jet Analytics 20.10 (from version 20.10.58) and Jet Analytics Classic.

Jet Analytics Data Integration — the cloud-first platform

Jet Analytics Data Integration is the primary platform for cloud-based architectures, supporting data warehouses, data lakes, and lakehouses with flexible storage options (including Microsoft Fabric, Azure Data Lake, and Snowflake) and scalable delivery endpoints.

While Jet Analytics Classic receives ongoing support and occasional updates, primary innovation is directed at Jet Analytics Data Integration.

Note:

The Power BI Premium XMLA endpoint is available in Jet Analytics Data Integration. It is not confirmed for Jet Analytics Classic. If Power BI Premium endpoint support is a requirement, migrate to Jet Analytics Data Integration.

Decision guide for Jet Analytics 20.10 users

ODX cloud functionality will stop working after February 2027Jet Analytics. All users who currently use ODX Server must plan their migration before this date — either to Jet Analytics Data Integration (for cloud-based architectures) or to Jet Analytics Classic Business Units (for on-premises SQL Server environments).

Option A: moving to the cloud (migrate to Jet Analytics Data Integration)

Choose this path if you want to use cloud storage, modern data lake or lakehouse architectures, or flexible delivery endpoints including Power BI Premium.

  1. If you are using CData data sources: Begin migrating to the corresponding Jet Analytics Enhanced providers to avoid the CData usage fee. In a Business Unit, Enhanced providers are available under Enhanced Data Sources. In an ODX, they are available under Data Sources > Manage Data Source Providers > Add.
  2. If you are using ODX Server: Migrate to Jet Analytics Data Integration using the Migration Tool. CData data sources are migrated as part of this process and can then be converted to Jet Analytics Enhanced providers.

Option B: staying on-premises (migrate to Jet Analytics Classic)

Choose this path if you want to remain on a SQL-based, on-premises or Azure SQL data warehouse without cloud infrastructure.

  1. If you are using CData data sources: Migrate to Jet Analytics Enhanced providers. New CData data sources cannot be added in Jet Analytics Classic.
  2. If you are using ODX Server: Migrate from ODX to Business Units before February 2027, then upgrade to Jet Analytics Classic. You do not need to move back to Business Units if you are planning to migrate to Jet Analytics Data Integration instead.

If you are already using Jet Analytics Data Integration

  • New CData data sources cannot be added (effective January 2025). Existing CData data sources can continue to be used on a paid basis.

Getting help

  • Contact your Jet Analytics partner for transition planning and guidance.
  • Contact Jet Analytics support for urgent concerns or troubleshooting.

Was this article helpful?

We're sorry to hear that.