Jet Analytics Classic is staying. The new cloud platform lands in Fabric. Five questions that tell an existing Jet customer whether to move, and when.
The short answer
You do not have to move. insightsoftware launched the new cloud-managed Jet Analytics on 1 June 2026 and said in the same breath that Jet Analytics Classic stays available for SQL-centric, on-premises and air-gapped deployments. No end date has been announced. So the question is not whether you are allowed to stay but whether moving buys you anything. For most existing customers the answer depends on five things: your Fabric roadmap, the SQL Server under your warehouse, the sources you want to add, any ERP migration already in flight, and how much of your model is custom. Hopton is a Jet Analytics partner for the UK and Ireland and we help Jet customers work through exactly this.
What you have today
Jet Analytics Classic is a SQL Server data warehouse in your own environment, loaded and managed through the Jet Data Manager. Pre-built Dynamics data models cover the usual areas, your consultant or team has extended them, Jet Reports and Power BI read from the result, and upgrades happen when you schedule them. It is a well-understood product. Plenty of UK finance teams have run month end on it for years and have no complaint.
What the new platform changes
The new Jet Analytics is cloud-managed and continuously updated. Transformations are designed visually and generated as PySpark. The governed model lands natively in Microsoft Fabric, Azure Data Lake or Snowflake, with Power BI on top. insightsoftware describes a zero-access security model in which your data stays in your own tenant, Instance Blueprints that cut environment setup from days to hours, and pre-built Dynamics data entities with a consistent semantic layer. We set it out in full in what is the new Jet Analytics. The thing to notice is that the destination has changed. Classic lands in SQL Server. The new platform lands in a lakehouse.
Five questions that decide it
Is Fabric on your roadmap?
If your wider estate is moving to Microsoft Fabric, or you want Business Central data beside your CRM, HR and operational data in OneLake, a warehouse that lands there natively saves you building a bridge later. If you have no Fabric plans, this reason falls away. What is Microsoft Fabric if you are weighing that up.
What is the SQL Server under your warehouse doing?
If it is a healthy VM with years left, keep it. If it is due for replacement, out of support, or the only SQL Server you still run, the cost of keeping Classic alive is rising and the cloud platform removes it.
What else do you want in the model?
Classic can take other sources, but each one is engineering. If the next twelve months include adding Dataverse, a web shop, payroll or a second ERP, a platform designed around many sources and a Spark engine is the easier place to do it.
Is an ERP migration already forcing a rebuild?
A NAV or GP to Business Central move changes the source schema, which means your Classic model is being reworked anyway. If you are paying for a rebuild, do it once, on the platform you want to be on in five years, and load the NAV or GP history into it so trend reporting survives.
How custom is your model?
A mostly standard model, pre-built entities with a handful of extra measures, moves quickly. A heavily customised one with years of bespoke logic is a project. Neither is a reason not to move, but the second one needs proper scoping before a date goes in anyone's diary.
How a sensible migration runs
Stand up the new platform beside Classic, not instead of it. Load the same sources. Rebuild custom logic, and use the exercise to retire measures nobody uses. Reconcile the two models for at least a full month end, ideally a quarter end, with finance signing off the differences. Repoint Jet Reports and Power BI at the new model only when it reconciles. Then switch Classic off. The side-by-side period is the whole risk control, and it is what we refuse to compress.
If you do nothing
Nothing bad happens. Classic keeps running, insightsoftware keeps supporting it, and your month end carries on. The only cost of waiting is that the decision gets made for you later, usually by a SQL Server going out of support or an ERP migration arriving, at which point you are deciding under time pressure. Deciding now, even if the decision is "not yet, revisit in 2027", is cheaper.
Working with Hopton
We map existing Jet Analytics Classic models against the new platform, scope the rebuild properly, and run the side-by-side reconciliation, as part of a view of your whole data estate rather than a lift of one warehouse. A free audit of your current Jet estate is the starting point. Details on our Jet Analytics partner page, or get in touch.
Related reading
Jet Analytics vs Jet Reports: which do you need, and when do you need both?
Business Central reporting options explained: Native, Power BI direct, Jet, Cosmos and Fabric
Business Central to Fabric in zero ETL steps: what the new mirroring preview means
Simon Devine
Managing Director
Part of the Hopton Analytics team, delivering governed analytics programmes for UK mid-market organisations.