ARGUS Enterprise End of Life: Every Date, and What Each One Actually Means

If you landed here because someone forwarded you a notice about ARGUS Enterprise going away, here is the short version:

ARGUS Enterprise version 13 is removed from ARGUS Cloud on 31 December 2026. From 1 January 2027, access to it on ARGUS Cloud is permanently discontinued.

That is the headline date. But it is not the only one, and the one most likely to catch a team off guard is actually in October. Here is the full schedule Altus has published, followed by what each date changes in practice.

The dates

Date	What happens
15 May 2026	Support ended for ARGUS Enterprise version 13
October 2026	Citrix access ends
31 December 2026	ARGUS Enterprise version 13 is removed from ARGUS Cloud
1 January 2027	All access to ARGUS Enterprise version 13 on ARGUS Cloud is permanently discontinued, and ARGUS Intelligence Platform authentication becomes mandatory to connect to the database

These come from Altus’s own ARGUS Enterprise platform updates page. Dates published by a vendor can move, and your contract may say something different from the general schedule, so treat this as a starting point for a conversation with your account rep rather than the final word.

Before anything else: check which version you are on

This matters more than any of the dates, and it is the step most people skip.

The schedule above is specific to ARGUS Enterprise version 13. If your firm is already on 14.5 or 15.0, you are not facing a December shutdown. You are facing the authentication change in January 2027, which is a different and much smaller problem.

Altus’s guidance is that AE 14.5.0.930 or 15.0.1.1170 needs to be installed on every machine before the January 2027 authentication requirement takes effect. Note the phrasing there: every machine. If you have analysts on laptops, a modeling workstation in the office, and someone who only opens ARGUS twice a quarter for a refinance, that is three upgrades, not one, and the person who only opens it twice a quarter is the one who finds out in February.

So the first thing to do is not evaluate alternatives. It is to find out which version each person at your firm is actually running.

What each date actually changes

15 May 2026 — support ended. This has already passed. In practice, it means version 13 still runs but you are on your own with it. No patches, and a support ticket about it will end in a recommendation to upgrade. Most firms did not notice this one, because software that works keeps working.

October 2026 — Citrix access ends. This is the date worth checking now. If your firm accesses ARGUS through a hosted Citrix environment rather than a local install, this is the one that changes your daily workflow, and it lands two months before the headline December date. Plenty of teams who think they have until December do not.

31 December 2026 — removed from ARGUS Cloud. The product is taken off the cloud platform. If your models and database live there, this is the one that matters.

1 January 2027 — access permanently discontinued, and authentication changes. Two separate things in one date. Access to version 13 on ARGUS Cloud stops. Separately, ARGUS Intelligence Platform authentication becomes mandatory to connect to the database from ARGUS Enterprise at all. That second half applies even to firms who upgraded — your connection path changes, not just your version number.

The part nobody puts in the notice: it is a repricing event

A version migration and a contract renegotiation are not the same thing, and it is worth being clear-eyed that this is both.

On Altus’s Q3 2025 earnings call in November 2025, their CFO said migrations were landing with “about a 16% price increase” on a blended basis. That is the most recent public figure I am aware of rather than a current quote, and your renewal will be your own number, not that one. But it is a reasonable prior to walk in with.

The structural change underneath it matters more than the percentage. Altus’s own product page describes ARGUS Intelligence Platform subscriptions as “tiered, asset-based” with pricing that “scales with your business.” Asset-based pricing means your software cost tracks the size of the portfolio you run through it, rather than the number of people using it.

For a large institution, that is often fine and sometimes better. For a lean shop that grew from six assets to eighteen while keeping the same two analysts, it is a different bill with the same headcount — and the increase arrives in the year you acquired, which is the year you least want a new fixed cost.

None of that is a criticism of the model. Usage-based pricing is normal software economics. It just means the migration is a good moment to actually read what you are signing, rather than treating it as an IT upgrade ticket.

Your options, honestly

Upgrade to 14.5 or 15.0 and migrate to ARGUS Intelligence. This is the default and it is a perfectly reasonable choice, especially if you have an institutional mandate, IFRS 16 or ASC 842 reporting obligations, or counterparties who expect ARGUS files. The work is real but bounded, and you keep a toolchain everyone in your organization already knows.

Move to another platform. The obvious moment to evaluate this is now, and the reason is specific: you are going to re-key and re-verify your models either way. Migrating inside the ARGUS family is not free — you are already paying the switching cost. That is the one point in a contract cycle when comparing alternatives costs you almost nothing extra, because the painful part is already on your calendar.

Rebuild in Excel. More viable than it was two years ago. A capable analyst working with an LLM can stand up credible models across several asset classes in a couple of weeks. What that approach does not give you is a way to check the result — there is no equivalent of a test suite for a spreadsheet, and producing models faster does not make any individual one more verifiable. Fine for a handful of straightforward assets; it gets difficult at portfolio scale and genuinely risky once an equity waterfall is involved, because a promote error pays an investor the wrong amount.

What to do this month

1. Find out which ARGUS Enterprise version each machine at your firm is running.
2. Find out whether anyone accesses it through Citrix, because that clock runs out in October.
3. Ask your account rep for your renewal number in writing, and ask specifically whether you are being moved to asset-based pricing.
4. Read the data-rights language in your agreement — who owns what you put in, whether it can be used, and what you can export if you leave. Those terms usually sit in the MSA rather than the order form, and the two differ.
5. If you are going to look at alternatives at all, do it before you sign, not after.

---

I build Solsten CRE, which is one of the alternatives, so weigh the last section accordingly. The dates above are Altus’s own and are worth confirming against your contract regardless of what you decide. If it is useful, our ARGUS alternative comparison covers six options including the ones that compete with us.