Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
If your agency is still running IBM Planning Analytics 2.0.9, there is a decision to make — but it is not simply a matter of upgrading before a single support deadline.
Standard IBM support for Planning Analytics 2.0.9 ended on 31 October 2025. Extended Support is available separately through to 31 October 2029, although the level of support changes during that period.
At the same time, IBM now has two quite different generations of Planning Analytics in market: Planning Analytics Local 2.1, which remains the direct upgrade path from 2.0, and the newer Planning Analytics 3.1 architecture built around TM1 12.
For agencies planning an upgrade, the first question is therefore not when can we install the next version?
It is which path are we actually taking?
Planning Analytics 2.0.9 moved out of standard support on 31 October 2025.
IBM offers four years of Extended Support through to 31 October 2029. Importantly, that does not mean four more years of standard support. IBM states that Extended Support provides critical fixes for the first year, followed by three years of support for usage and known defects.
For an agency still running 2.0.9, check exactly what support you have purchased and what it covers. Do not assume that because the software is still operating, or because you have an IBM support arrangement, you have the same coverage you had under standard support.
This matters for cyber security, operational risk and audit. It also matters when deciding how urgently an upgrade needs to happen.
For organisations running Planning Analytics on their own infrastructure, Planning Analytics Local 2.1 is the direct successor to 2.0.
IBM describes 2.1 as a direct upgrade from 2.0. Existing TM1 databases, Planning Analytics Workspace content, Planning Analytics for Microsoft Excel reports and Websheets do not need to be rebuilt simply because you move to 2.1.
That makes 2.1 the lower-disruption option for agencies that want to bring an existing Local environment onto the current supported release without changing the underlying architecture at the same time.
As at August 2026, IBM has not announced an end-of-support date for Planning Analytics Local 2.1.
That distinction is important. There is no need to manufacture an artificial deadline for moving beyond 2.1.
The underlying models may carry forward, but some older Planning Analytics tools do not.
Planning Analytics Local 2.1 does not support:
There are also some less visible technical considerations, including unsupported features such as TM1 replication and synchronisation and Java-based TurboIntegrator functions.
If your agency still uses Architect or Perspectives heavily, this can make the upgrade more significant than the server version change suggests.
The work is not rebuilding your budgeting model. It is moving administration, development and some user activity onto current interfaces such as Planning Analytics Workspace and Planning Analytics for Microsoft Excel, and dealing with any technical dependencies on retired functionality.
Find those dependencies before setting the project timeline.
TM1 12 is the database architecture used by the newer generation of Planning Analytics.
This is where upgrade discussions can become confusing, because moving from Planning Analytics 2.0 to 2.1 and moving from TM1 11 to TM1 12 are quite different exercises.
A move to 2.1 is an upgrade.
A move to TM1 12 is a migration.
IBM provides a specific TM1 Database 12 Migration Utility to convert existing TM1 11 databases into the TM1 12 format. There are also architectural and compatibility changes that need to be assessed before migration.
For example, TM1 12 no longer supports the older C, Java and .NET APIs. Java TI is not available. Architect and Perspectives cannot connect to TM1 12. There are also changes to configuration, file handling and administration.
That does not mean existing Planning Analytics investments have to be discarded. It means the move needs to be treated as a platform migration rather than an in-place software upgrade.
For a large government budgeting environment, that distinction matters.
There are currently several ways the newer Planning Analytics 3.1 and TM1 12 architecture appears in IBM's product range.
Planning Analytics as a Service is IBM's managed SaaS offering and uses the TM1 12 architecture.
For agencies considering it, the assessment extends beyond Planning Analytics functionality. Hosting, data residency, security, integration, identity, procurement and whole-of-government cloud requirements all need to be considered.
For some organisations it may be the logical target. For others, the operating model or security requirements may point elsewhere.
IBM also offers Planning Analytics Advanced Certified Containers 3.1 as a supported product.
This provides another route to the Planning Analytics 3.1 and TM1 12 architecture for organisations with an appropriate container platform and operating model.
It is not simply a replacement installer for a traditional Windows or Linux Planning Analytics Local environment. The infrastructure and operational implications need to form part of the decision.
IBM has also released a non-containerised Planning Analytics Local 3.1 Technical Preview, including TM1 12.
As at August 2026, it remains a technical preview without official product support.
That makes it useful for evaluating the direction of the Local product and testing migration, but it should not be confused with a generally supported production release.
For an agency that wants to retain a traditional locally installed Planning Analytics environment today, Planning Analytics Local 2.1 therefore remains the supported path.
For a move from Planning Analytics 2.0 to 2.1, the answer is generally no.
Your TM1 databases and existing Planning Analytics content carry forward. The main areas to investigate are legacy tools and any functionality IBM no longer supports.
For TM1 12, the answer needs more qualification.
Your existing model remains the starting point, but IBM requires the database to be converted using its migration tooling. Integrations, automation, APIs, configuration and operating procedures also need to be checked against the TM1 12 architecture.
The right question is not can our model be moved?
It is what around the model also needs to change?
For mature government Planning Analytics environments, that surrounding layer can include interfaces to financial systems, data warehouse feeds, automated processes, Excel reporting, security integration, deployment procedures, backup and recovery, monitoring and support processes.
That is why an inventory before migration is worth doing.
There is no universal "quiet period" for government finance teams.
Budget preparation, estimates processes, internal budget cycles, year-end, system freezes and agency-specific planning activities all affect when a Planning Analytics change can safely happen.
Start with your own operational calendar.
Identify the periods when the planning system is business-critical and work backwards to find a realistic implementation window. Allow time for:
If legacy interfaces are changing as part of a 2.1 upgrade, include user preparation and training as well.
A technically simple upgrade can still become risky if user acceptance testing is compressed into the week before a major planning cycle.
Do not solve that problem by forcing a production change at the wrong point in the finance calendar.
But equally, do not simply accept an unsupported period without understanding it.
Establish exactly what IBM support remains in place, when the level of that support changes, and what risks remain. If there will be a gap, document it through the agency's normal technology and cyber risk processes and agree the appropriate interim controls.
That may include tighter access, additional monitoring, restrictions on unrelated system changes and a clearly approved remediation date.
The decision is then being made consciously against operational and security risk rather than being driven by an assumed software deadline.
Before choosing a target version or architecture, answer five questions:
Those answers will usually make the immediate path much clearer.
For many existing Local customers, moving to Planning Analytics 2.1 will be the sensible next step. It removes the immediate version issue without forcing a broader architectural decision at the same time.
For others, particularly where infrastructure or cloud strategy is already under review, it may make sense to assess TM1 12 now rather than perform two separate transitions.
Neither choice should be driven simply by a version number.
The objective is to keep a critical budgeting and planning platform supported while making the next change at a time — and on an architecture — that makes sense for the agency.