If you’re already investing time, budget, and IT resources in a migration, this may be the best opportunity you’ll have in years to modernize your real estate technology stack.
During a readiness assessment, you’ll get a structured, no-obligation review of your current IBM TRIRIGA environment, priorities, and migration options.
Standard support for IBM TRIRIGA Application Platform v3.9 and older releases officially ended, initiating the countdown for enterprise real estate teams.
Customers who migrate receive Dual Support with MAS for up to 19 months, but must fully cut over to Maximo Real Estate & Facilities by this date.
Customers who migrate receive Dual Support with MAS for up to 19 months, but must fully cut over to Maximo Real Estate & Facilities by this date.
Maximo Real Estate & Facilities is TRIRIGA re-platformed onto the Maximo Application Suite. IBM’s own migration guidance describes work well beyond a version upgrade — which is exactly why this is the moment to evaluate different platforms. With dedicated budget, IT mobilization, integration work, and retraining, the question you should ask is not “how do we upgrade?” — it’s “which platform is the right fit for the next ten years?”
New suite licensing under the AppPoints model
MAS deployment and database preparation
Full database schema rebuild and data transformation
User licence migration and re-provisioning
Retraining of end users on completely new UI paradigms
Mobilization of significant internal IT and budget resources
Scope items above are drawn from IBM’s published TRIRIGA-to-Maximo upgrade and lifecycle documentation. Confirm current details for your version and contract directly with IBM.
Every path requires investment, resources, and planning. Compare options before committing
Follow the default IBM migration path to stay within the product suite.
→What does Sustained Support cover — and what does it cost?
→What security and compliance exposure
builds over time?
→Does delay preserve options, or compress
the eventual migration?
Follow the incumbent path to IBM’s successor platform.
→How much of your environment genuinely carries forward?
→WWhat does AppPoints licensing cost at your usage levels?
→Does the target state fix the problems that matter most to you?
Compare a platform built for your priorities before you commit.
→Does it meet your functional scope for real estate and lease?
→How does migration effort and disruption actually compare?
→Does it deliver stronger ERP alignment, predictability, and adoption?
Use our migration checklist or set an assessment with us. Our experts bring decades of experience helping organizations successfully plan and execute complex transformations.
Independent analyst research consistently points to the same six factors that distinguish the strongest TRIRIGA replacement options. Ask every vendor about all six criteria and evaluate their answers — including those from IBM.
Many organizations have invested years in customizing workflows. Evaluate whether a new platform can support your requirements through configuration or requires continued redevelopment
Ask yourself: Can a new platform adapt without adding technical debt?
Supports IFRS 16, ASC 842, PIPEDA, and localized tax and regulatory updates globally.
Ask yourself: Will the platform fit naturally into your technology ecosystem or create additional complexity and manual workarounds?
Out-of-the-box configuration pathways that reduce implementation timelines by months.
Ask yourself: Can you forecast total cost with confidence, or does the licensing model make future spend hard to predict?
Connecting physical assets, facility conditions, and lease contracts in one operational model.
Ask yourself: Do you need a full IWMS, or finance-led lease management and real estate portfolio depth?
Avoid complex token and AppPoint calculators with transparent SaaS pricing models.
Ask yourself: How much consolidated, executive-level reporting works out of the box — without a second product or module to buy?
Intuitively designed interfaces that reduce training friction and operational errors.
Ask yourself: Will the platform drive user adoption or create extra complexity?
Your ERP strategy, business requirements, and portfolio complexity can have a significant impact on which platform best fits your organization.
Integration with your tech stack affects everything from financial accuracy to operational efficiency. Consider how real estate, lease, and facility data moves across your technology landscape and whether it remains aligned without manual effort.
→Native bidirectional SAP & Oracle integrations — no
middleware to maintain
→Automated postings, cost-center mapping, and
payment schedules stay in sync
→Audit-ready trail across lease events without manual
journal entries
→Built-in ASC 842, IFRS 16, and GASB 87 compliance alongside SAP data
Organizations managing large networks of stores, branches, offices, or facilities often have requirements that generic workflows cannot easily support. Evaluate whether the platform is designed for the realities of your operating model.
→Portfolio-wide visibility across leased, sub-leased,
and owned locations
→For retail: Automated percentage-rent calculations and CAM reconciliation at scale
→Configurable out-of-the-box — no rebuild of store-level workflows
→Out-of-the-box and ad-hoc reporting for renewals, obligations, and optimization
Managing real estate across regions, business units, and currencies introduces complexity that grows over time. Consider whether the platform can support expansion without increasing administrative overhead.
→Multi-region and multi-currency portfolio management
→Cloud-native platform designed for continuous, non-
disruptive upgrades
→Configurable workflows that don’t require third-party
integrators
→Decision-intelligence tooling built for evolving
workplace strategy
Nakisa belongs on your shortlist when you need real estate operations, lease
administration, lease accounting, and finance connected as one operating model —
particularly in complex, multi-entity SAP environments.
Portfolio management, lease administration, and ASC 842 / IFRS 16 / GASB 87 compliance in a single system, not stitched-together point
solutions.
Meet requirements through configurable workflows instead of bespoke code — so you don’t rebuild a decade of customization debt on a new
platform.
Migration scope, professional services, and recurring platform costs priced transparently, so finance can forecast total cost of ownership.
Once we went live and got used to the system, it became very easy to integrate with our two SAPs and do SAP postings. Nakisa is very professional in handling two SAPs at the same time, and it gives us flexibility to change the platform easily.
Nakisa is excellent software allowing us to be more efficient with all our rent payments, to do better follow-ups on our deadlines, renewals, deposits, etc. The software is very user-friendly. In short, it is essential for our real estate department.
Map what actually has to move — and what that reveals about your real options.
→Data, customizations, and workflow dependencies to audit first
→ERP touchpoints most likely to break on re-platforming
→Reporting and controls gaps to close before cutover
→Full-cost comparison worksheet across all three paths
→The questions to put to every vendor — including IBM
Instant access — no sales call required.
Direct answers to what TRIRIGA customers research before choosing a path.
IBM has published an end-of-support date of September 30, 2027 for TRIRIGA and the TRIRIGA
Application Suite, across all versions — no version is exempt. Software sales closed on January
28, 2026. Customers who remain on TRIRIGA after September 2027 can move into IBM Sustained
Support for a period; customers who migrate receive Dual Support with the Maximo Application
Suite for up to 19 months but must fully cut over to Maximo Real Estate & Facilities by April 2029
to retain that overlap. Confirm current lifecycle dates for your version against IBM’s official
support documentation.
Not for most customers. Maximo Real Estate & Facilities is TRIRIGA re-platformed onto the Maximo Application Suite. IBM’s own migration guidance references suite licensing under the AppPoints model, MAS deployment, database preparation, Red Hat OpenShift infrastructure, persistent storage migration, user licence migration, application migration, testing, and workflow review. The underlying database can carry forward, but custom workflows and integrations generally need to be rebuilt. For most organizations this is closer to a re-platforming programme than a version upgrade — which is why it warrants a full evaluation rather than an automatic decision.
Deep customization was one of TRIRIGA’s original selling points, and most long-standing deployments have customized at least one area substantially — organizational structure, roles and task permissions, approval logic, asset libraries, and data tagging or formatting rules are the most common. That customization increases migration complexity regardless of destination, and it cuts both ways: some organizations conclude they don’t want to redo the work, while others recognize they’ll have to redo it anyway and use the moment to reset. Use the transition to classify every customization as migrate, retire, or redesign, then evaluate whether a configuration-first platform can meet the surviving requirements without rebuilding the debt.
Maximo Application Suite is licensed using AppPoints — a pooled entitlement model where points are allocated across applications, rather than a traditional named-user model. Customers have widely described this as harder to forecast than per-user licensing, because consumption across modules affects cost and different departments’ usage interacts. Some organizations report teams becoming hesitant to use the platform fully for fear of unplanned cost. For budgeting and commercial governance, model your expected AppPoints consumption before committing, and compare it against clear, itemized alternatives. Confirm current licensing terms directly with IBM.
A defensible business case covers the full cost and effort of each path — not just licence or subscription fees — the data and customizations to migrate or retire, ERP and SAP integration impact, reporting and controls gaps, implementation and partner risk, user adoption, and expected future value including AI and automation. It should state clearly why the selected platform is the best fit for your future, not simply the most familiar option. The test: does the decision hold up under board, finance, procurement, and audit scrutiny?
Nakisa is worth evaluating when you need real estate operations, lease administration, lease accounting, and finance connected in one operating model — especially in complex, multi-entity, multi-ERP SAP environments. Areas to assess: native bidirectional SAP integration without middleware; combined real estate portfolio management and ASC 842 / IFRS 16 / GASB 87 compliance; a configuration-first approach that reduces customization debt; clear itemized commercial terms; and modern reporting and decision intelligence. The goal isn’t to assume Nakisa is the answer — it’s to compare it fairly against the incumbent path.