Support for TRIRIGA ends in September 2027, and new orders have already closed. The data survives the move to Maximo the disruption does not. For most real estate operators and corporate occupiers, that forced disruption is the best moment in a decade to ask a sharper question: is a purpose-built platform like Yardi a better home for your portfolio than an asset-management suite?
Jan 28, 2026
New TRIRIGA orders & SaaS sign-ups closed
Sep 30, 2027
End of support for all TRIRIGA versions
MREF 9.x
IBM's designated upgrade path, inside Maximo
For nearly two decades, IBM TRIRIGA has been a fixture in the corporate real estate world — the system of record that quietly ran the leases, spaces, capital projects, and maintenance programs of some of the largest property portfolios on the planet.
If you lead a real estate, facilities, or workplace function and you run TRIRIGA, it has likely become invisible in the way only deeply embedded software can: unremarkable until something forces you to look at it again.
Something just did. IBM has set a firm end date for TRIRIGA as a standalone product, folding its capabilities into the Maximo Application Suite under a new name.
For most organizations the first reaction is procedural — “we’ll follow the upgrade path and move on.” But treating a forced replatform as a simple version bump is the single most expensive mistake you can make right now.
This article lays out exactly what IBM announced, what the migration genuinely involves, and how to think clearly about your options before the clock runs out.
What is an IWMS?
An IWMS — Integrated Workplace Management System — is enterprise software that unifies five traditionally separate real estate and facilities disciplines on a single platform and database:
- Real estate & lease management — lease administration and lease accounting.
- Capital projects — construction and capital planning, budgets, controls.
- Facilities & maintenance — work orders, preventive maintenance, inspections.
- Space & workplace management — floor plans, occupancy, desk and room booking, moves.
- Energy & sustainability — consumption tracking and ESG reporting.
The value is integration: a single source of truth, so a lease event can trigger a maintenance task and a space change can flow straight into occupancy cost.
The short version
- TRIRIGA isn’t dying — the brand is. The capability continues inside IBM Maximo Real Estate & Facilities.
- The clock is real. Support for TRIRIGA versions ends September 30, 2027; new software orders closed January 28, 2026.
- It is not a destructive data conversion. On IBM’s path your database largely carries forward.
- The disruption is mandatory either way. Which is exactly why standing pat without evaluating alternatives leaves real value on the table.
What IBM actually announced
Let's separate the facts from the noise. IBM has announced the support lifecycle completion for all versions and releases of IBM TRIRIGA and the IBM TRIRIGA Application Suite, effective September 30, 2027.
Alongside that, software ordering for these programs concluded on January 28, 2026, and TRIRIGA SaaS is no longer available for new orders as of that same date.
The designated successor is IBM Maximo Real Estate & Facilities (MREF) 9.x, delivered as an application within Maximo Application Suite (MAS) 9.x.
Is TRIRIGA "dead"? No — but the strategy behind it has changed
It would be inaccurate, and frankly unfair to IBM, to say TRIRIGA is being killed. Lease administration, space and portfolio management, capital project planning, and facilities operations all continue inside Maximo Real Estate & Facilities.
If anything, sitting alongside Maximo's asset-management engine opens genuinely useful adjacencies — condition-based monitoring, mobile inspections, and IoT-driven maintenance that TRIRIGA, on its own, did not natively reach.
But the center of gravity has shifted, and that matters for fit. TRIRIGA was conceived and sold as an Integrated Workplace Management System — a platform built first and foremost around corporate real estate, lease accounting, and the workplace.
Maximo's heritage is enterprise asset management for asset-intensive industries, and IBM now positions the combined portfolio under its sustainability software business.
For an organization whose core need is property and lease management, you are now a real-estate use case inside an asset-management suite, rather than the headline use case of a dedicated workplace platform.
The data survives the migration. The disruption does not — and disruption you have to pay for anyway is the cheapest re-evaluation you will ever get.
Is this a data migration or a full data conversion?
This is the question that quietly terrifies most TRIRIGA owners, and the honest answer is reassuring — with a catch. On IBM's own path, this is not a destructive, from-scratch data conversion. Maximo Real Estate & Facilities is essentially TRIRIGA re-platformed onto Maximo Application Suite rather than rebuilt.
IBM's migration guidance lets you continue using your existing TRIRIGA application database in its current location, or move it to a new database, and a dedicated User Migration Tool moves your users and licenses across — letting you review and update people records before assigning new licenses.
A connector also keeps portfolio data such as people, locations, and assets synchronized between the TRIRIGA and Maximo sides during transition.
So your lease records, your space hierarchy, your portfolio data — those carry forward. The hard part isn't the data. The hard part is everything wrapped around it:
- New infrastructure. Maximo Application Suite runs on Red Hat OpenShift, and adopting MAS means standing up MAS Core and Foundation Services as a new platform layer.
- A new licensing model. TRIRIGA's licensing is replaced by Maximo's role- and usage-based AppPoints, which means right-sizing your license pool becomes a genuine strategic exercise.
- Customizations and integrations. If your TRIRIGA instance is heavily customized, you will need to decide what to rebuild using Maximo's native and low-code tools, and what needs a more involved integration approach.
- A new interface, plus training and change management. A new platform means new admin skills, new user experiences, and the organizational work of bringing people along.
The contrast is important for your decision: staying with IBM preserves your data but still demands a real replatform project. Moving to a different system requires a full data migration and reimplementation. Once you see those two paths side by side, the gap between them narrows far more than the incumbent's gravity suggests.
What the precedent tells us about how this actually goes
TRIRIGA-to-Maximo is new enough that it has a thin track record of its own. Fortunately, it inherits a very well-documented precedent: the broader migration from classic Maximo 7.6.1 to Maximo Application Suite, which uses the same OpenShift platform and the same AppPoints licensing model that MREF now sits on top of.
The signal from that precedent is consistent — this is a substantial undertaking, not a patch.
The clearest tell comes from IBM itself: the sustained support program for legacy Maximo was structured to run for years beyond the official end-of-support date specifically to account for the difficulty and technical lift of migrating.
When a vendor builds a multi-year runway because customers cannot realistically move in time, that is a candid acknowledgment of complexity. Independent commentators in the Maximo ecosystem have been blunter still — describing the move as something that is “not a lift-and-shift”, with the heavy lifting concentrated in OpenShift infrastructure readiness, revalidating or rebuilding customizations and integrations, change management, and licensing strategy.
On timelines, system integrators that do this work typically quote roughly three to six months for a TRIRIGA-to-MREF transition under favorable conditions, with heavily customized environments often extending beyond that range.
The point is not to frighten you; it is to set honest expectations. Any project of this size deserves a deliberate decision, not a reflexive one.
The question the timing hands you: is Maximo still the right fit?
Here's the strategic core of this entire transition. The reason a forced migration is so valuable as a decision point is counterintuitive: the switching cost that normally protects an incumbent has just been removed.
In a normal year, ripping out a system of record is unthinkable — the migration cost, the integration rework, the retraining, the licensing renegotiation all act as a moat that keeps you exactly where you are, regardless of whether the platform still serves you.
But IBM has now scheduled all of that disruption for you anyway. You will be standing up new infrastructure, renegotiating to a new licensing model, rebuilding customizations, redoing integrations, and retraining users no matter which direction you choose.
The moat has been drained — and the incremental cost of evaluating, and potentially moving to, a platform genuinely built for your use case has rarely been lower.
Even IBM's own implementation partners frame the transition this way. The recurring advice across the ecosystem is to treat it as a “reset opportunity” — a moment to streamline processes, retire outdated customizations, and rethink your data strategy rather than faithfully rebuilding what you already had.
One major advisory firm opens its transition guidance by telling clients to first evaluate whether their existing deployment is delivering full value, because the transition “may be an ideal opportunity to move on from a configuration that isn't working.”
If the people paid to migrate you into Maximo are telling you to re-evaluate first, that advice is worth taking seriously.
Why so many TRIRIGA users land on Yardi
When the migration is forced anyway, the natural question is “which platform was actually built for what we do?” For real estate operators and corporate occupiers, the answer is frequently Yardi — not as a like-for-like clone of TRIRIGA, but as a connected, cloud-native platform where centers of gravity in real estate, leasing, and facilities gathering matter.
Importantly, Yardi is delivered as a fully hosted SaaS solution, so there is no Red Hat OpenShift estate to stand up and no AppPoints model to right-size. Yardi paths naturally across the two buyer types TRIRIGA always served:
Yardi Corom
- Centralized lease management with critical-date tracking
- Lease accounting compliance for FASB ASC 842, IFRS 16 and GASB 87
- Occupancy tracking and flexible desk booking
- Transaction management and broker collaboration
- Facility maintenance and construction management
- 100% cloud SaaS — deploy as a single stack or by module
Yardi Facility Manager
- Automated work-order assignment, tracking and completion
- Planned and preventive maintenance with code-compliance checks
- Inspections — manual, regulatory and due-diligence
- Mobile app for technicians with offline support
- Auto-posts purchase orders, payables and charges to your ledger
- Connected to CommercialCafe tenant portal and VendorCafe
The deciding advantage for most real estate organizations is that these aren’t bolt-ons. They sit on the same Yardi platform as your property accounting, management, charge posts straight to the general ledger, leases event flows into occupancy cost, and a tenant request raised in CommercialCafe lands in Facility Manager — the integration that an IWMS promises, delivered natively rather than stitched together.
| TRIRIGA / IWMS capability | Where it fits in Yardi |
|---|---|
| Lease management & lease accounting | Yardi Corom — occupier leases and lease accounting |
| Facilities & maintenance / work orders | Yardi Facility Manager — functions as a CMMS |
| Space, occupancy & workplace management | Corom occupancy & desk hoteling; Floorplan Manager |
| Capital projects & construction | Yardi Construction Manager |
| Energy & sustainability / ESG reporting | Yardi Energy Suite & sustainability reporting |
| Portfolio data & property accounting | Yardi Voyager — the connected core ledger |
| Tenant & vendor engagement | CommercialCafe and VendorCafe |
Which configuration is right depends on whether you sit on the occupier or owner side of the table — and that is exactly the kind of distinction a structured evaluation needs to settle.
Yardi will be the strongest fit for many TRIRIGA users; it will not be the answer for every one, particularly where genuine asset-intensive organizations that lean on Maximo’s industrial maintenance depth. The goal is to choose deliberately, with the mapping above as a starting point rather than a foregone conclusion.
How to run a disciplined evaluation — before you commit
Whatever you choose, the failure mode is the same: choosing a path before you understand where you actually stand today. A credible evaluation doesn’t start with product demos. It starts with an honest inventory of your current reality — and then weighs your options against criteria you set, not the ones a single vendor happens to win on.
1. Map what you really have
Document your modules in active use, the depth and necessity of your customizations, every integration TRIRIGA touches, your data quality, and — critically — which capabilities are load-bearing for the business versus which are legacy habits no one has questioned in years.
2. Define your future-state requirements
Separate what your portfolio needs in the next five years from what your current configuration happens to do. Lease accounting compliance, occupancy and workplace optimization, capital project depth, asset and maintenance intensity, sustainability reporting, mobility — weight them by your strategy, not by feature checklists.
3. Score every option, including staying
Run Maximo, the leading alternatives, and the delay scenario through the same weighted scorecard, including total cost of ownership over a realistic horizon, migration risk, and time-to-value. The discipline of scoring the incumbent on equal footing is what turns a reflex into a decision.
Where Assetsoft fits — and where we're transparent with you
This is the work we do every day. Assetsoft is a multi-platform PropTech consultancy that has been helping real estate owners, occupiers, and operators select, implement, and integrate property and facilities technology since 2012, across North America, the UK, the Middle East, and Asia-Pacific.
We run structured, criteria-based platform evaluations and execute the migrations and integrations that follow.
We will also be straight with you about something most firms gloss over. Assetsoft is a certified implementation partner across several of the platforms you might evaluate — we are a Yardi ICN member and Virtuoso Qualified, MRI Certified, a Procore Partner, UiPath Certified + Fast Track Agent, and a SAP Concur Partner.
That breadth is exactly why we can run a genuinely useful comparison: we have done the migration mechanics on multiple sides of this market, not just sold one product. But because we implement several of the platforms in the field, a disciplined evaluation engagement is structured around your weighted criteria and your data — so the recommendation is defensible whether it lands on "stay on Maximo," "move to Yardi," "move to MRI," or "extend and decide later."
If the honest answer for your portfolio is to follow IBM into Maximo, we will tell you so. The one thing we'd urge you not to do is let the September 2027 clock make the decision for you by default. A forced migration is a rare, paid-for opportunity to get this right. Use it deliberately.
