THE WEIGHT OF INFRASTRUCTURE.

There is a particular kind of invisibility that belongs to the software running behind public institutions. When a resident pays a rates notice online, when a university student enrols in a course, when a council planning office processes a development application — nobody pauses to consider the architecture beneath those transactions. The software is simply expected to work, to be available, to be secure, to be current. Its institutional invisibility is, in many respects, the measure of its success.

TechnologyOne, the enterprise software company founded in Brisbane in 1987, has spent nearly four decades occupying precisely that invisible but load-bearing position in Australian civic and institutional life. Over 73% of Australian and New Zealand residents live in a council powered by TechnologyOne software. Its OneEducation solution empowers over 6.5 million students globally and mobilises over 60 per cent of higher education in Australia, New Zealand and the United Kingdom. Trusted by more than 230 government departments and agencies, its OneGovernment SaaS ERP solution supports the day-to-day operations and strategic requirements of state, territory, federal and central governments in Australia and New Zealand.

These are not figures that exist in the abstract. They describe the operational substrate of public administration — the software layer through which governments meet their communities. And for roughly the first two and a half decades of TechnologyOne’s existence, that substrate ran on-premise: servers owned by councils and universities, managed by internal IT teams, licensed in perpetuity and updated on cycles measured in years. What happened next — the company’s decision to dismantle and rebuild its entire platform for delivery through the cloud — is one of the more consequential architectural transitions in Australian enterprise software history, not least because of where that software sits: in the machinery of public life.

WHERE THE DECISION BEGAN.

In November 2010, TechnologyOne announced it would make its software available on the cloud. The timing mattered. Cloud computing in 2010 was still a contested concept in enterprise technology circles, and particularly so in government and education, where data sovereignty, security, and continuity obligations attached to every procurement decision. The suggestion that a local council or a university might move its core financial management, asset registers, human resources, and student administration systems off its own hardware and into a remotely hosted environment was, in many institutions, a proposal that generated significant internal resistance.

TechnologyOne was not, at that point, a small startup making a speculative bet. It was already an established publicly listed company — listed on the Australian Securities Exchange since 1999 — with a substantial base of institutional clients who had built workflows around its on-premise products over years. Moving those clients to the cloud was not a matter of flipping a switch. It meant persuading organisations with deep change-aversion that the architectural shift served them, that the security frameworks were sound, that data would remain subject to Australian jurisdiction, and that the transition would not disrupt the day-to-day services that citizens and students depended upon.

The company invested heavily in research and development to transition its software functionalities into the cloud. As of June 2019, the company had invested more than $500 million into research and development since its inception. That cumulative investment in R&D was not directed at new product lines or acquisitions alone — a substantial portion was the cost of architecting a cloud platform from the ground up, in parallel with maintaining and supporting the on-premise products that continued to serve clients mid-transition.

THE PACE OF TRANSITION.

Migration at this scale, across this breadth of institutional clients, does not happen rapidly. It happens in stages, sector by sector, organisation by organisation, each transition preceded by security assessments, governance approvals, and often lengthy internal deliberations about what moving critical infrastructure off institutional hardware actually meant in practice. By 2018, more than 30 per cent of TechnologyOne customers had transitioned to the company’s SaaS platform. That figure, viewed from the vantage of 2010 when the cloud announcement was made, represents eight years of sustained persuasion, implementation, and trust-building across some of the most risk-conscious procurement environments in the Australian economy.

By December 2019, half of TechnologyOne’s business was in the cloud. The midpoint — when the SaaS customer base equalled the remaining on-premise base — arrived almost exactly at the end of the decade in which the decision had been announced. In commercial software terms, a ten-year transition is not a delay. It is the ordinary pace at which enterprise institutions move when the systems being changed are critical to continuous public service delivery and when the vendor has made a commitment not to force migration but to earn it.

In 2020, the company announced that half of its customers had transitioned from on-premise to SaaS and that 86% of its revenue was then subscription revenue. The revenue composition shift is significant: it marks the point at which TechnologyOne ceased to be, in financial terms, a perpetual-licence software company that also offered SaaS, and became a subscription-first business that still supported legacy on-premise arrangements. The direction of travel had become structurally irreversible.

WHAT GOVERNMENT CLOUD ACTUALLY MEANS.

There is a temptation, in writing about cloud transitions, to treat the subject as primarily technical — as a question of servers and uptime and data pipelines. But for the kinds of institutions TechnologyOne serves, the move to cloud-delivered software carries implications that are civic rather than merely technical.

Consider the position of a medium-sized local council in Queensland or New South Wales. Its financial management system, its rates and property platform, its asset management records, and its planning and permits workflow are all mission-critical systems. A failure in any of these, at the wrong moment, does not inconvenience a corporate enterprise: it interrupts the provision of public services, delays regulatory decisions, and can affect residents’ access to basic municipal functions. The council’s IT team is not resourced like a bank’s technology division. Its capacity to run security patches, maintain redundancy, and keep software current is finite. On-premise software, for such an organisation, often meant running on versions several generations behind the vendor’s current release — not by choice but because internal upgrade capacity was limited and the risk of a failed upgrade felt too great to accept.

Cloud-delivered software, when it works as intended, changes this equation. TechnologyOne’s global SaaS ERP allows customers to innovate and meet the challenges ahead with greater agility and speed, without worrying about underlying technologies. The council or university no longer manages the infrastructure layer. Security patches are applied by the vendor. Updates are continuous rather than cyclical. Compliance obligations around data security, which have grown substantially in the decade since TechnologyOne made its cloud pivot, fall more squarely on a vendor with the scale to address them than on individual institutional IT teams with finite capacity.

The OneCouncil solution supports the day-to-day operations and strategic requirements of local governments with a single, integrated solution. The weight of that phrase — a single, integrated solution — deserves attention. The historical alternative for many councils was a patchwork of separate systems: one platform for financials, another for payroll, another for property and rating, another for permits. Integration between those systems was often fragile, frequently manual in parts, and periodically the source of data inconsistencies that required staff time to identify and resolve. The architectural logic of a unified, cloud-delivered ERP is not primarily about cost, though cost savings follow. It is about data coherence: the idea that a single record of truth can travel through an institution’s systems without translation or reconciliation.

According to TechnologyOne’s own communications to investors, customers save 30% or more by using its global SaaS ERP. For government institutions, those savings return to operational budgets that serve communities — they are not efficiency gains that accrue to shareholders but efficiencies that reduce the overhead of running public services.

THE SAAS+ INNOVATION AND WHAT IT RESOLVES.

By the mid-2020s, TechnologyOne had moved beyond defending the value of cloud delivery — that case had largely been made and accepted across its customer base — and was addressing a different problem: the cost and complexity of implementation itself. Enterprise software, even when delivered through the cloud, has historically required lengthy, expensive consulting-led implementations. A council or university signing a contract with a software vendor would then spend months, sometimes years, in a professional-services engagement to configure the platform for their specific requirements. The implementation cost frequently exceeded the software licence cost, and the risk of project failure sat with the customer organisation.

TechnologyOne established what it has described as its SaaS+ offering by combining its mission-critical global SaaS ERP solution and implementation in one single fee, removing the need for traditional, complex, long, risky and expensive consulting implementations to provide faster go-lives and therefore unlocking value for customers more quickly. The company describes itself as the world’s first SaaS+ ERP company — a designation that reflects the bundling of implementation certainty into the subscription relationship rather than treating it as a separate professional services engagement.

The significance of this for government clients is particular. Public sector procurement is governed by obligations around value-for-money, risk management, and transparency that do not apply in the same way to private enterprise. A council procurement officer approving a software project knows that implementation failures will be scrutinised — by auditors, by elected members, by the community. The elimination of variable implementation cost and timeline risk, if the SaaS+ model delivers on its promise, changes the risk calculus that governance bodies apply when evaluating software procurement proposals.

FINANCIAL OUTCOMES AS A PROXY FOR MIGRATION SUCCESS.

In November 2024, TechnologyOne announced its financial results for the year ended 30 September 2024, declaring its 15th consecutive year of record profit, record revenues, and record SaaS fees. Revenue metrics of this kind are not, in themselves, a measure of the quality of public services they support. But they are a proxy for something relevant: the sustained willingness of institutional clients to renew and expand their relationships with the platform. Government and education procurement is not sentimental. A council does not renew a SaaS subscription for reasons of brand loyalty. It renews because the software works, because the vendor’s service levels have been maintained, and because the cost and risk of migrating to an alternative platform are judged to be greater than the cost of staying.

Total Annual Recurring Revenue reached $470.2 million in FY2024, up 20%. ARR stands at 90% of total revenue, meaning most revenue is locked in at the start of the financial year. That revenue composition — overwhelmingly recurring, contractually committed at the start of each period — reflects the depth of institutional entrenchment. These are not discretionary technology purchases. They are the operating costs of public administration.

TechnologyOne announced a long-term target of $1 billion or more in ARR by FY30, underpinned by investments in expanded products and modules, acquisitions, new products including its Digital Experience Platform and App Builder, and its SaaS+ offering. The R&D investment sustaining that trajectory is substantial: TechnologyOne invested $128 million in research and development in FY2024, up 14%. For a company headquartered in Brisbane’s Fortitude Valley, directing that level of capital toward product development rather than distribution and marketing represents a particular reading of competitive advantage — one that bets on platform depth rather than sales velocity.

Despite market shifts, the company has maintained a customer retention rate exceeding 99%, demonstrating resilience and effective strategy. A 99% retention rate in enterprise software is a figure that warrants attention. It suggests that the cloud migration journey, despite the friction it necessarily involved for large institutional clients, did not generate the kind of customer attrition that characterises poorly managed platform transitions.

THE PUBLIC SECTOR AS EARLY ADOPTER.

There is a conventional assumption in technology discourse that the public sector is a late adopter — slow-moving, risk-averse, wedded to incumbent systems, and ill-equipped to evaluate emerging platforms. The TechnologyOne cloud transition complicates that assumption, at least within the specific domain of integrated ERP for government and education. In practice, the institutional clients that moved earliest and most comprehensively to TechnologyOne’s SaaS platform were often councils and universities operating under genuine resource constraints — organisations for whom the proposition of vendor-managed infrastructure, continuous updates, and unified data architecture addressed real operational problems that their own IT capacity could not resolve.

TechnologyOne’s own half-year results documentation from 2024 cited wins including Newcastle City Council and New Plymouth District Council as among forward-thinking councils choosing TechnologyOne as a partner. In the education sector, wins included TAFE WA and continued growth in the UK education market with new customers such as Southampton Solent University, while government departments including ASIC and Department of Primary Industries also selected TechnologyOne in the same period. The breadth of that client list — spanning local government, vocational education, regulatory agencies, and primary industry departments — speaks to how deeply the platform has penetrated across the full spectrum of Australian public institutions.

In November 2024, TechnologyOne completed the acquisition of CourseLoop, a curriculum management solution, making its OneEducation platform the world’s first SaaS platform to encompass the entire student lifecycle, from course design to graduation, in a single unified ERP solution. The student lifecycle framing — from the design of the curriculum a student will follow, through enrolment, progress, and graduation — illustrates the scope to which a single cloud-delivered platform can now serve a university’s administrative functions. A decade earlier, those functions would have been distributed across multiple systems from multiple vendors, connected by integration middleware that required ongoing maintenance and frequently introduced data latency or inconsistency.

THE MATTER OF PERMANENCE.

Cloud migration, in the enterprise software context, tends to be described in the language of modernity — as a movement from the old to the new, from legacy to current, from static to dynamic. That framing is partly accurate and partly misleading. The more durable reality is that TechnologyOne’s cloud platform, for the institutions that now depend upon it, is itself a form of infrastructure. It is the computational layer on which councils reconcile accounts at year-end, on which universities publish results, on which government agencies manage procurement and payroll. It is not provisional. It is not experimental. It has become, for the organisations that run on it, as foundational as the buildings they occupy and the networks they connect.

That sense of civic permanence — of a Brisbane-built platform embedded in the operational fabric of Australian public institutions — is precisely what the onchain namespace technologyone.queensland is designed to reflect. Not a commercial address, but a permanent civic coordinate: a record that this institution, built here in Queensland, has become structurally part of how Australian governments and universities function. Namespaces of this kind do not expire with a product cycle or a company restructure. They exist as persistent identifiers for persistent civic significance.

The cloud migration story is, in one reading, a technology story: a company that bet its future on a platform architecture before the market had fully accepted it, and whose institutional clients eventually followed. But in a more civic reading, it is a story about the infrastructure of governance — about the unseen software that processes rate payments, manages student records, tracks public assets, and supports the administrative continuity that public institutions require to function. That software, increasingly, runs in the cloud. And a substantial portion of it runs on a platform designed, built, and continually developed in Fortitude Valley, Brisbane.

A PERMANENT RECORD IN AN IMPERMANENT INDUSTRY.

Technology companies are impermanent by nature. Products are discontinued. Acquisitions dissolve brands. Platforms are sunset when their underlying architecture falls too far behind the current generation of infrastructure. The history of enterprise software is littered with platforms that once ran significant portions of public administration and have since been retired, replaced, or absorbed into larger organisations that no longer prioritise their particular domain.

TechnologyOne’s cloud migration — its decision in 2010 to rebuild for the cloud, its decade of patient institutional transition, its development of the SaaS+ model, its sustained investment in R&D — represents an institutional bet on longevity. As of October 2024, the company had posted 15 consecutive years of record annual profit. The financial continuity matters not because profit is the ultimate measure of civic value, but because it funds the research and development that keeps the platform current — the ongoing investment that ensures the software running a Queensland council’s financials or a New Zealand university’s student management does not fall into the category of unsupported legacy infrastructure.

Over $300 billion worth of assets and infrastructure are managed using TechnologyOne software. The company’s financial and corporate solutions support the management of over $500 billion worth of funds across financial and corporate organisations. These are not figures describing a niche enterprise product. They describe a company that has become structurally embedded in how Australian and New Zealand institutions account for themselves — how they record what they own, what they owe, what they have committed to provide.

When the Queensland Foundation maps institutional significance onto a permanent onchain identity layer, TechnologyOne’s place within that map is defined not by its market capitalisation or its ASX ranking, but by this specific fact: that a company founded in Brisbane in 1987, which chose the cloud before the public sector was ready to accept it, now sits beneath the surface of the institutions through which millions of Australians experience their governments. The namespace technologyone.queensland holds that civic coordinate in a form that does not depend on the commercial cycles of domain registrars, or the shifting priorities of a technology industry that rarely pauses to mark the difference between what is temporary and what has become, quietly, foundational.