A Government Department Walks Away From SAP
Australia's Department of Infrastructure, Transport, Regional Development, Communications, Sport and the Arts has hired Accenture to replace its SAP environment entirely, rather than migrate it, choosing Workday and ServiceNow as the two vendors that will carry finance, human resources, and payroll into a cloud-based future. The deal, reported at 38.8 million dollars over three years, runs through mid-2029 with an option to extend to mid-2032, and Accenture will act as both systems integrator and software reseller. This is a government agency choosing to abandon a vendor relationship most private enterprises treat as semi-permanent, and doing so in favor of two vendors instead of one.
The department's current system runs on SAP ECC6, which reaches official end-of-life at the end of 2027, with maintenance extensions available for organizations willing to pay for them. Rather than take the well-worn path of migrating to S/4HANA on the existing vendor relationship, the department decided the deadline was an opportunity to re-examine the entire ERP architecture, and concluded that no single remaining vendor, including SAP's own cloud successor, was the obvious default choice.
The Math Behind a Two-Vendor Bet
Splitting a core ERP function between Workday and ServiceNow is a meaningfully different bet than migrating to any single large vendor's latest cloud offering. A department spokesperson described the plan as delivering a cloud-based ERP solution centred on Workday for finance, human resources and payroll functions, with ServiceNow presumably covering workflow, case management, or IT service functions adjacent to the financial core. That split requires the department and Accenture to build and maintain integration between two vendors' data models and release cycles, work that a single-vendor migration would have avoided entirely.
The spokesperson's framing, that Workday and ServiceNow include a range of modern capabilities the department will assess over time in line with business requirements, signals an agency keeping options open rather than committing to a fixed target architecture on day one. That is a defensible posture for a public sector buyer with a multi-year runway and extension options built into the contract, but it is also a meaningfully higher integration and governance burden than the single-throat-to-choke model the department is walking away from.
Betting Against the Single-Vendor Playbook
Most large enterprises facing an SAP end-of-life deadline default to migrating within the SAP ecosystem, in large part because the switching costs of leaving, retraining staff, rebuilding integrations, re-certifying compliance controls, are so high that incumbency usually wins by default. SEIDOR's 2026 survey of 360 CIOs running SAP found that 94 percent of customers plan to modernize their existing SAP environment rather than replace it outright, which makes the Australian department's decision to leave SAP altogether a genuine outlier rather than a typical response to the same deadline pressure.
That outlier status is worth taking seriously rather than dismissing as a public-sector quirk. Government agencies often face procurement rules that require genuine multi-vendor competition rather than incumbent renewal, which removes some of the switching-cost inertia that keeps private enterprises inside their existing vendor's ecosystem. A CIO evaluating the same SAP deadline inside a private company, without a procurement mandate forcing a fresh look, should ask whether incumbency is actually the best answer or simply the path of least internal resistance.
The Deadline That Started the Clock
The program will be delivered in two phases, with Accenture and the department's own internal staff running it jointly rather than Accenture operating as a pure external contractor. That joint delivery model matters because it keeps institutional knowledge of the department's own processes inside the organization during the transition, rather than outsourcing that knowledge entirely to the systems integrator, a structural choice that reduces the risk of the department becoming dependent on Accenture for basic operational understanding of its own new systems.
With the engagement running to mid-2029 and an extension option to mid-2032, the department has built in roughly five to six years of runway from contract signing to full operational maturity, well beyond the 18 to 36 month timeline that typical cloud ERP migrations require. That extended timeline signals how seriously the department is treating the dual-vendor integration challenge: this is being sold internally as a multi-year program with real architectural risk built into the plan from the start.
What a Multi-Vendor Core Actually Requires
Running finance and HR on Workday while routing adjacent processes through ServiceNow only works if governance, data ownership, and integration responsibilities are assigned clearly and early, because the two systems will inevitably disagree at the edges about which one owns a given record or workflow step. Enterprises that have tried similar multi-vendor cores without that discipline typically end up rebuilding, in custom integration code, the same kind of unified data model a single-vendor ERP would have provided natively, which erodes much of the architectural benefit the split was meant to deliver.
The department's decision to keep an internal team embedded alongside Accenture throughout delivery is the clearest evidence that it understands this risk. Governance of a two-vendor ERP core cannot be fully delegated to a systems integrator, however capable, because the integrator's incentive is to deliver the contracted scope on schedule, not to resolve every future ambiguity about which system owns which piece of institutional data. That ownership question needs to be answered by the department itself, continuously, for as long as the two systems coexist.
What This Means for Your Own ERP Decision
The Australian department's choice works best as a stress test rather than a template, useful for anyone assuming a single-vendor migration is the only reasonable response to an SAP or Dynamics end-of-life deadline. The real question is whether the functions currently bundled inside your ERP actually belong together in one system, or whether some of them would be better served by a specialized vendor, provided you are willing to own the integration and governance cost that split creates.
For most private enterprises, that cost will tip the decision back toward a single vendor, exactly why SEIDOR found 94 percent of SAP customers choosing modernization over replacement. The department's bet is still a reminder that incumbency is a choice, not a default, and that the deadline forcing your hand on architecture is also an opening to ask honestly whether the current bundle of ERP functions reflects what your business actually needs or simply what one vendor's suite happened to include a decade ago.
