Anugal, the agentic identity governance platform from Chennai-based Business Core Solutions, has set out a three-path approach for enterprises modernising their identity and access management, identity governance (IGA) and SAP GRC environments: replace existing platforms, migrate in controlled phases, or extend current investments with an agentic AI layer. The pitch rests on a hard deadline that many SAP customers are only now confronting.
That deadline is real and documented. SAP has confirmed that mainstream maintenance for SAP Identity Management 8.0 ends on 31 December 2027, with extended maintenance available to 2030, and that SAP GRC Access Control, Process Control and Risk Management 12.0 reach the same mainstream-maintenance end on the same date. For identity governance, the twin dates force a decision that will not wait.
The deadline behind the announcement
Two features of that deadline make it consequential. First, there is no direct successor to SAP Identity Management 8.0. SAP steers customers toward its Cloud Identity services and Cloud Identity Access Governance, but partners and competitors note that this cloud portfolio is not a full replacement for a central identity management system that also covers non-SAP applications. Second, the GRC successor — the HANA-based SAP GRC 2026 release — requires a HANA database and an S/4HANA foundation, which means customers on other databases face a database migration before they can even upgrade.
The result is a migration wave. SailPoint, Saviynt and Microsoft have each published paths for organisations leaving SAP Identity Management, and independent market research places SailPoint clearly ahead in identity governance, with Saviynt and Oracle next.
Anugal’s three paths
Anugal’s answer is to offer customers a choice rather than a single route. Under “replace,” it unifies identity lifecycle management, access requests, provisioning, certifications, segregation-of-duties checks and audit evidence in one platform. Under “migrate,” it runs a five-stage method — assess identities, roles, connectors and policies; design the target governance model; migrate in validated phases; verify access and audit readiness; then retire legacy components after sign-off — with parallel operation to preserve continuity. And, under “extend,” it adds an agentic AI layer that analyses identity signals, flags risk and recommends actions for approvals and role optimisation, while keeping policy enforcement, human approval and audit trails in place. A low-code studio connects legacy and custom applications, including those without modern APIs.
The framing is non-disruptive: Anugal presents itself as an orchestration layer that coexists with SAP GRC, cloud identity providers and existing IAM systems rather than replacing them. Its agentic architecture operates in advisory, assisted or controlled-automation modes, with final authority reserved to human approvers.
The field it is entering
Anugal is a small entrant in a market with entrenched leaders. Independent research places SailPoint at the front of identity governance, with Saviynt and Oracle behind it, and both publish SAP IDM migration offerings with public references — Saviynt has documented a migration at an engineering group with more than 46,000 employees. SAP itself offers a native path, and Microsoft documents one through Entra ID Governance.
Against that, Anugal’s claims — core modules live in six to eight weeks, more than a hundred pre-built connectors and up to 50% lower three-year total cost of ownership — are its own, with no named customers or benchmarks attached. The company launched the platform in 2024 from a Chennai base with roots in SAP BASIS services, and its selling point is simplicity: faster implementation and lower operating effort than legacy platforms.
What to watch
Three signals will show whether Anugal converts positioning into traction. First, whether it publishes named customer references, since the migration wave rewards proof over promises. Second, whether its agentic AI layer holds up under the audit scrutiny that identity governance invites, given that every automated recommendation must remain explainable and defensible. Third, whether the deadline drives SAP customers toward SAP’s own successors, toward the established third-party platforms, or toward coexistence layers like Anugal’s.
What the announcement does and doesn’t establish
It establishes a three-path modernisation strategy, a five-stage migration method, an agentic AI layer with human approval preserved, and a low-code integration studio. It does not establish any customer win, any pricing, any independent performance benchmark, or any verified outcome for the TCO and timeline figures the company publishes.
The honest summary is that the interesting part of this announcement is not the vendor but the deadline it points to: a large installed base of SAP identity and GRC customers must move by the end of 2027, and the successor paths each carry conditions. Anugal is one of several companies competing to help them, and it is a small one in a field led by much larger players. Its strategy is coherent and its claims are plausible, but until it publishes customers and evidence, the case rests on the deadline rather than on demonstrated delivery.
Editor’s Note: This article draws on the Anugal release and the company’s published materials, SAP‘s own maintenance announcements and community guidance, and independent identity governance market research. The SAP maintenance deadlines are from SAP sources; Anugal’s TCO, timeline and connector figures are as published by the company and are not independently verified. No interview was conducted.