TRIRIGA End of Life: Dates and the Maximo Migration

Yes, IBM TRIRIGA is being retired. IBM has announced support lifecycle completion for all versions and releases of IBM TRIRIGA and IBM TRIRIGA Application Suite effective September 30, 2027, and software ordering for those programs concluded on January 28, 2026. The designated upgrade path is IBM Maximo Real Estate and Facilities 9.x, part of IBM Maximo Application Suite 9.x, which IBM describes as "the evolution of IBM TRIRIGA". Nothing switches off on the support end date, but you can no longer buy TRIRIGA, and customers who want dual support have to finish moving by April 2029.

Last updated August 2026. Dates verified against IBM's own support announcement.

The confirmed TRIRIGA end of life dates

These are the dates IBM published, not vendor speculation. Every consulting firm writing about the transition is working from the same announcement, so if you see a different date somewhere, check it against this.

Two details in that table catch people out. The first is that ordering already closed: as of early 2026 you cannot add TRIRIGA seats or start a new TRIRIGA SaaS subscription, so an acquisition or a new division has to land on Maximo. The second is that dual support is conditional. It is not a blanket 19 month cushion for everyone. You get it if you have migrated to MAS parts, and you keep it if the transition is finished by April 2029.

What replaced IBM TRIRIGA?

IBM Maximo Real Estate and Facilities 9.x, delivered as an application inside IBM Maximo Application Suite 9.x. IBM's product page calls it "the evolution of IBM TRIRIGA" and positions it as a single source of truth for real estate and facilities data, listing AI powered lease abstraction, workflow automation, and integrated IoT and data analytics among what is new. The functional areas will look familiar to a TRIRIGA administrator: lease management, space management, capital planning, maintenance and operations, and environmental and energy management.

The shift that matters organizationally is that real estate is now an application in a maintenance and asset management suite rather than a standalone IWMS. If your facilities team already runs Maximo for work orders and assets, that consolidation is the upside of the whole exercise. If real estate was the only reason you had IBM in the building, you are being moved onto a larger platform than the one you bought.

Can you still buy TRIRIGA?

No. Software ordering for IBM TRIRIGA and TRIRIGA Application Suite concluded on January 28, 2026, and TRIRIGA SaaS stopped accepting new orders on the same date. Existing SaaS customers keep access for the duration of their active subscriptions. In practice that means any new capacity, any new entity you acquire, and any greenfield deployment goes to Maximo Real Estate and Facilities.

TRIRIGA vs Maximo: what is the actual difference?

They are no longer two competing products, which is the source of most of the confusion. Maximo has historically been IBM's enterprise asset management platform for maintenance, work orders, and physical assets. TRIRIGA was the integrated workplace management system for real estate, leases, and space. Maximo Real Estate and Facilities folds the TRIRIGA capability set into Maximo Application Suite as an application, so the question is no longer which product to choose but when you move.

For a lease administration or corporate real estate team, the practical differences to plan around are the platform version and entitlement model, the migration of configurations and customizations, and one capability change that directly affects daily work: how lease abstracts get created.

What the migration means for your lease data

This is the part that gets underestimated, and it is where a real estate team feels the project rather than IT. Moving platforms means every lease record travels, and validation exposes whatever was thin in the original data. Three problems surface almost every time.

Amendments that were never abstracted. A lease gets amended, the amendment goes into a document folder, and the record in the system still reflects the original deal. Nobody notices until someone compares the record to the document set.

Critical dates stored as text. Renewal and termination notice windows that were typed into a comment field instead of a date field do not drive notifications, and they do not migrate as dates. Since automated alerts on upcoming lease expirations are one of the main reasons to run the platform at all, this is an expensive gap to carry forward.

Rentable area and entity mismatches. If the square footage or the tenant entity on record disagrees with the lease, every pro rata share, allocation, and recovery calculation downstream inherits the error. Migrating it just moves the error to a newer system.

The only reliable fix is to go back to the source documents and re-abstract, then compare the fresh abstract against the legacy record. Doing that before the cutover is far cheaper than reconciling two systems afterwards, because during the migration you have one authoritative answer to produce rather than two systems to argue between.

Does Maximo Real Estate and Facilities do lease abstraction for you?

Starting in version 9.2, partly. IBM documents that lease abstract records can be created "by using AI, or through manual data entry, Open Standards Consortium for Real Estate (OSCRE) .xml files, or offline forms", and that you can create real estate lease records "by using AI to automatically populate lease abstracts from uploaded documents (starting in Maximo Real Estate and Facilities 9.2)". IBM also documents that asset lease records can be created only through manual data entry.

Read those two sentences together and the timing problem is obvious. The AI abstraction arrives on the platform you have not migrated to yet. During the migration itself, when you most need to re-read a few hundred lease PDFs and check them against legacy records, you are still on TRIRIGA 11.x, where the documented options are manual entry, an OSCRE file somebody else has to produce, or an offline form. A trained analyst needs roughly four to eight hours to abstract a complex commercial lease by hand. At 300 leases that is most of a person year, sitting directly on the critical path of a project with a 2029 deadline.

That is the gap worth closing with something outside the platform. Running the PDFs through AI lease abstraction software produces the structured fields in minutes, each one linked to the page it came from, so a lease administrator reviews rather than reads. The output is a spreadsheet, which is exactly what TRIRIGA data utilities want for a bulk load, and the same file feeds the Maximo side after cutover. We cover the field mapping and the load path in detail on the TRIRIGA lease abstraction page.

Which lease accounting standards carry across?

All of them, and the coverage is unusually broad. IBM states that Maximo Real Estate and Facilities Real Estate Manager lease accounting "includes processes designed to support old lease accounting guidelines (ASC 840 and IAS 17) as well as current accounting standards (ASC 842, IFRS 16, GASB 87 Lessee, GASB 96, and GASB 87 Lessor)". The GASB 87 Lessor and GASB 96 support is rarer than it sounds and is a genuine reason public sector, healthcare, and university real estate teams end up here rather than on a lighter ASC 842 lease accounting platform.

What the accounting engine cannot do is invent the inputs. Classification depends on the term, the renewal and purchase options, the likelihood assessments, and the discount rate, and every one of those starts as a sentence in a lease that somebody had to abstract. Public sector teams building a GASB inventory will find the same requirement laid out in our GASB 87 lease accounting software guide.

What should a real estate team do first?

Start with a data audit, not a software evaluation. The platform decision has effectively been made for you; the work that is genuinely yours is deciding what data deserves to travel. A practical sequence looks like this.

Inventory what you actually hold: every active lease, every amendment, and every document that is filed but never abstracted. Sample twenty records against their source documents and count the discrepancies, which tells you honestly whether this is a light validation or a full re-abstraction. Re-abstract whatever fails the sample, prioritizing leases with option deadlines inside the next 36 months, because those are the ones where a missed notice costs real money during a period when everyone is distracted by a migration. Then load clean data and keep the legacy records for comparison until you have reconciled.

One thing worth flagging while the platform is under review: Maximo Real Estate and Facilities includes environmental and energy management alongside the lease modules, so sustainability reporting tends to arrive on the same project plan. If your organization is also being asked for emissions numbers, the underlying data problem is identical to the lease one, since you cannot build an audit ready emissions footprint out of documents nobody has turned into structured records. Same discipline, different documents.

The short version

TRIRIGA ordering closed on January 28, 2026. Support for all versions completes on September 30, 2027, with Sustained Support available for up to five years after that and Extended Support as a chargeable option for the first twelve months. Maximo Real Estate and Facilities 9.x is the upgrade path, and finishing the move by April 2029 is what keeps dual support in place. The platform work belongs to IT. The lease data work belongs to you, it is the part that determines whether the new system is trustworthy on day one, and it is worth starting before the migration rather than during it. You can abstract a lease free here to see what a source linked abstract looks like against one of your own records.