IBM has merged TRIRIGA into the Maximo Application Suite, rebranded as Maximo Real Estate and Facilities. For the hundreds of corporate real estate organizations that have built operations around TRIRIGA over the past decade, this raises an immediate and practical question: what do we do now?
The answer depends entirely on your situation. And the biggest risk most organizations face is not choosing the wrong path — it is choosing any path before fully understanding where they stand today.
What Actually Changed
TRIRIGA as a standalone product is being absorbed into IBM's broader Maximo ecosystem. The core functionality is not disappearing — lease administration, space management, capital planning, and facilities operations will continue to exist within the Maximo suite. But the platform architecture, licensing model, deployment requirements, and upgrade path are all changing.
For organizations running TRIRIGA today, this means a migration is coming whether they initiate one or not. The question is not if, but when and to what.
The Options on the Table
Most organizations evaluating their TRIRIGA future will consider some version of these paths:
Follow IBM's roadmap. Migrate from TRIRIGA to Maximo Real Estate and Facilities within the Maximo Application Suite. This preserves continuity with IBM, retains existing configurations and data structures, and keeps the organization within a known vendor ecosystem. It also means adopting MAS Core and Foundation Services as new infrastructure requirements, regardless of whether the organization needs other Maximo capabilities.
Move to another IWMS. Platforms like Archibus, Planon, Nuvolo, and others offer comparable functionality. This path makes sense for organizations that were already considering a change or that have outgrown what TRIRIGA provides. It also means a full implementation — data migration, process redesign, user training, and integration rebuilds.
Rethink the approach entirely. Some organizations will use this moment to ask whether a single consolidated platform is still the right model. Many CRE teams already operate across multiple systems — lease tools, project management platforms, FM service provider tools, ERP systems — and the TRIRIGA transition may be an opportunity to connect what exists rather than consolidate again.
Each of these paths has tradeoffs. None of them is universally right or wrong.
The Real Risk
The risk is not making the wrong choice. It is making the choice without a clear understanding of how TRIRIGA is actually being used today.
In most organizations, TRIRIGA usage has evolved significantly since the original implementation. Modules that were deployed may no longer be actively used. Workarounds and manual processes have grown around the system. Integrations may be outdated, fragile, or undocumented. Data quality varies by module. And the people who understood the original design decisions may no longer be with the organization.
Any transition plan built on assumptions about current usage rather than verified facts carries significant risk — regardless of the destination platform.
What to Understand Before Making a Decision
Before committing to a direction, organizations need clear answers to a set of foundational questions:
How is TRIRIGA actually being used? Not how it was designed to be used, but what modules, workflows, and reports are actively in use today. Which teams depend on it daily and which have moved to other tools or spreadsheets?
What data lives in TRIRIGA and what is its quality? Lease records, space data, capital project history, maintenance logs — what is current and reliable, and what is stale or incomplete? Data migration decisions depend on knowing what is worth migrating.
What integrations exist? TRIRIGA rarely operates in isolation. Understanding the connections to ERP systems, financial platforms, HR systems, building automation systems, and service provider tools is essential. Some of these integrations may be the most complex part of any transition.
Who are the stakeholders? Real estate, facilities, finance, IT, and service providers may all interact with TRIRIGA in different ways. Their requirements, timelines, and tolerance for disruption will shape what is realistic.
What does the business need going forward? The transition is an opportunity to ask whether the current technology model still serves the business. Requirements from five or ten years ago may not reflect how the organization operates today or where it is heading.
The Cost of Assumptions
Organizations that skip this assessment and move directly to vendor selection or migration planning often discover problems late — after contracts are signed, timelines are set, and expectations are locked in.
Common examples include discovering that data quality issues make migration far more complex than estimated, finding that integrations assumed to be straightforward require significant rework, learning that users have built critical processes outside the system that need to be accounted for, and realizing that the modules being replaced were not the modules being used.
These surprises add cost, extend timelines, and erode stakeholder confidence. They are avoidable with upfront assessment work that is typically measured in weeks, not months.
A Practical Starting Point
The most productive first step is a lightweight, targeted assessment that establishes the facts. Map current usage. Document integrations. Evaluate data quality. Talk to the people who use the system and the people who depend on its outputs.
This gives leadership a clear, data-driven basis for making the transition decision — whether that decision is to follow IBM to Maximo, move to another platform, rethink the approach, or some combination.
The Window to Act
TRIRIGA is not disappearing overnight. But the organizations that start assessing now will have the clearest picture of their options and the most time to execute a thoughtful transition. Those that wait until deadlines are close will have fewer choices and more pressure.
This is a decision that deserves a clear-eyed evaluation, not a rushed one.