TM1 v12: 37 IT functions removed — here's the map
Open any TM1 codebase that has been in production for a few years and you'll
find the same three things: an ExecuteCommand firing PowerShell to send an
email, a TM1RunTI in Windows Task Scheduler that nobody remembers setting
up, a SaveDataAll in the overnight chore.
None of that runs on v12.
A live client migration is what brought this to the front of my mind. Searching the codebase for the usual suspects is how the real backlog shows up: the functions somebody forgot were still on the schedule.
The v12 engine lost direct access to the operating system because it runs inside containers — no shell, no C API.
- 37 TI functions removed
TM1RunTIout- SFTP out
- TM1Web also gone
Not to mention server lifecycle administration — SaveDataAll,
ServerShutdown, LockOn/LockOff — which now belongs to the container
orchestrator, not to TI.
None of these removals are arbitrary. Without shell, the platform is auditable by default. Without the C API, you can ship monthly patches instead of annual service packs. Without local processes, the same engine runs on on-prem Software Hub, on Planning Analytics as a Service on AWS, or on any hyperscaler with the same API surface.
The conclusion I keep landing on: v12 is a genuinely better engine. The price is that a lot of what you wrote for TM1 wasn't written for v12.
I organised what came out into 7 groups, each with its replacement pattern. It's in the carousel:
Download the map as a PDF (9 slides) —
OS interaction, server lifecycle, batch update, Data Reservation (CDR), CAM
security, logging/TM1RunTI, and the rest (SFTP, TM1Web, CLI utilities).
I'm not writing this to alarm anyone. If you're on PA Local 2.x, that code still works — and will for a while. But if v12 is on the roadmap, the real question isn't "what breaks". It's what the old code was actually doing.
On this migration, the gap is the same one I've seen before. Budgets get priced against what people remember writing. Cost gets pulled by what was still running at 2am.
When you scope the upgrade, are you counting the functions on the checklist — or the ones still on the scheduler?
Situation as of Aug/2026. Sources: our own experience enriched by IBM Docs Planning Analytics 3.1, CogKnowHow, ACGI, QueBIT. Confirm the current list before finalising the scope of a real migration.
For the wider picture of the migration (architecture, business case, and what almost never makes it into the numbers), see also Planning Analytics v12 migration: the real benefits.
We run TM1 migrations without stopping the planning cycle — see our IBM Planning Analytics practice or get in touch.