Migrate SAP GRC Access Control
SAP GRC transition: move Access Control to Anugal before the end of 2027
Mainstream maintenance for SAP GRC Access Control 12.0 ends at the end of 2027. SAP's published plan for its successor also involves moving to a new platform stack, so make the move to Anugal. We assess your rulesets, mitigating controls, approval paths and emergency access, rebuild what still reflects real risk on Anugal in validated waves, and keep your GRC audit evidence retrievable after Access Control is retired.
What the 2027 Deadline Means for SAP GRC Access Control
Mainstream maintenance for SAP GRC 12.0, which includes Access Control, ends at the end of 2027. Paid extended maintenance is available beyond 2027, but it is a holding position, not a plan.
SAP has announced SAP GRC for SAP HANA as the successor to GRC 12.0. SAP’s published plan, which SAP marks as subject to change, says the new release runs on HANA databases only, on SAP S/4HANA 2025 or SAP S/4HANA Foundation 2025, and that for GRC 12.0 customers on any database a conversion to SAP S/4HANA (on premises or private cloud edition) is required. Teams also choose between hub and embedded deployment.
On SAP’s published plan, the successor path involves a platform move too. If your access-risk controls are moving to a new platform, move them to Anugal.
What Waiting Costs Your Access-Risk Controls
Two versions of the truth
The longer a conversion runs, the more rules and mitigations get edited in two places. Unless one system owns the decision each day, nobody can say which check was live when access was granted.
Shortcuts around the risk check
Deadline pressure produces manual tickets and direct role assignments. Each one skips the access-risk analysis that the approval path was built to run.
Emergency access between owners
DORA's technical standards expect privileged, emergency and administrator access to be granted only on a need-to-use or ad hoc basis. If firefighter assignments move before their review step does, emergency use can go unreviewed.
Risk checks that stop at SAP
Finance, procurement and HR processes span SAP and non-SAP applications. A check that only sees SAP misses the combinations that cross systems.
An identity source that is changing too
SAP IDM mainstream maintenance ends on 31 December 2027. If IDM feeds users into Access Control today, your identity source changes as well. See SAP IDM migration.
The Anugal Difference
Migrate from SAP GRC Access Control to Anugal, Stage by Stage
Anugal is the destination for what SAP GRC Access Control does for you today: access risk analysis, access requests, emergency access and access reviews, on one identity governance platform.
We move the control, not the workaround. We map your rulesets, mitigations, workflows and roles before anything moves, decide with you which rules still reflect a real risk, rebuild those on Anugal, and keep your GRC audit evidence retrievable long after the system is gone.
Typical program: from 6 months, delivered in validated waves- 1
Discover
Map how your SAP GRC Access Control is set up today.
We analyze access risk rulesets, mitigating controls, access request workflows (MSMP/BRF+), firefighter IDs, role definitions and access review cycles, and record which rules still reflect a real control.
You get: discovery report, rule rationalization and scope
- 2
Design
Design risk and access governance on Anugal.
SoD and critical-access risk library, mitigating controls, request and approval routes, emergency access and certification campaigns, designed on Anugal.
You get: target risk and control blueprint
- 3
Migrate
Move rules, roles and controls in waves.
Rulesets, mitigations, role catalog and owner assignments migrate wave by wave with deKorvai, our migration engine. Where needed, GRC and Anugal run side by side, and risk-analysis results are compared before each wave closes.
You get: risk-analysis comparison for every wave
- 4
Verify & go live
Prove your controls still hold.
Risk-analysis parity, workflow and emergency-access testing, UAT and audit-readiness checks with your internal control team, then go-live with hypercare.
You get: control test evidence and go-live sign-off
- 5
ArchiveAUDIT-READY
Keep audit evidence on call.
Firefighter logs, access request history, review results, SoD violations and mitigation history are archived read-only and stay searchable, ready for any audit request.
You get: searchable archive you can retrieve from on demand
- 6
Retire
Retire SAP GRC when it is no longer needed.
Once the archive is verified and you sign off, we decommission GRC components and integrations on your timeline, ending maintenance and running costs.
You get: decommissioning checklist and closure report
Your move to Anugal, stage by stage
Conceptual flowDiscover
Map what the system does
Design
Target model on Anugal
Migrate
Validated waves
Verify & go live
Prove your controls still hold.
Archive
Read-only, searchable history
Retire
SAP GRC Access Control switched off
Running systems
The parallel run is a safety mechanism, never the end state. Stage length and scope vary by estate.
ARCHIVE BEFORE YOU RETIRE
Switch SAP GRC off. Keep the evidence your auditors rely on.
- Firefighter logs, access request history, review results and SoD violation and mitigation history move into a read-only archive.
- Search and retrieve by user, role, risk, system or date, whenever internal or external audit needs it.
- No more licenses, patching or infrastructure kept alive only to answer audit questions.
What You Get on Anugal
Preventive SoD across applications
Requested access is checked against enterprise-wide SoD rules at request time, before anything is provisioned. Conflicts are assessed across applications, roles and business functions, and are blocked, escalated or routed for mitigation. See how the SoD engine works.
Mitigating controls with owners
Compensating controls carry a defined owner, scope and expiry, and justifications are enforced.
Emergency access under control
Access is scoped to specific systems or roles, expires after the approved duration, records sessions and requires a post-use review. Actions can be compared against the approved purpose.
Reviews with context
Access certifications bring entitlement, usage and risk context together, so reviewers can document retain-or-revoke decisions.
Agentic governance, with people in charge
Anugal.AI agents continuously evaluate identity signals, SoD conflicts, usage and peer context, and recommend whether to approve, deny, modify, revoke or escalate, with clear reasoning behind each recommendation. Approvers keep full authority, and no automated decision bypasses governance. With Anugal Co-Pilot, requesters and approvers work in plain language, run risk and SoD checks mid-conversation and track request status without raising tickets.
SoD and provisioning beyond SAP
350+ pre-built integrations, with native API and SCIM support, govern modern, legacy and custom applications. HR, ITSM, ERP and directory events drive governed access changes in both directions, so risk checks and provisioning cover SAP and non-SAP systems on the same rules.
SoD in role design
The Role Build Agent works from business process documentation and applies SoD checks to SAP role designs, with human oversight.
Lifecycle on the same platform
Joiners get the access their role justifies, movers lose obsolete access as new access is assigned, and leavers are deprovisioned across applications and directories with evidence retained.
Non-human access under governance
Service accounts are registered with ownership and purpose, and AI agents are governed for ownership, privileges and access reviews.
One audit record
Decisions, actions, exceptions and outcomes are recorded as append-only audit records.
Why Migrate to Anugal
One platform for access risk and identity lifecycle
SAP's Access Control roadmap includes integration with SAP Cloud Identity Access Governance for additional cloud applications. On Anugal, the access-risk decision and the provisioning that follows it run on one platform.
A migration engine built for the move
Rulesets, mitigations, role catalog and owner assignments move with deKorvai, and risk-analysis results are compared before each wave closes, so you can show your controls still hold.
Legacy systems come along
Systems without modern APIs connect through Anugal Studio.
Your rule investment carries over
The work in your rulesets and role design feeds the discovery and the target design on Anugal.
Evidence that carries through the move
One append-only trail on Anugal, and a searchable archive of your GRC history, helps support audit-ready evidence before, during and after the migration.
For financial entities, DORA's technical standards (Delegated Regulation (EU) 2024/1774) require segregation of duties that prevents combinations of access rights that could circumvent controls. They also require access reviews at least once a year, and at least every six months for ICT systems supporting critical or important functions. NIS2 lists access control policies among required risk-management measures. A platform change doesn't pause any of them.
APRA has flagged privileged access not always approved and granted for a valid business need and a specified time as a common weakness. Where such gaps could materially affect an entity, APRA treats them as a material control weakness notifiable under CPS 234 paragraph 36.
Where Anugal Sits After SAP GRC Access Control
Anugal takes over the access-risk controls that Access Control runs today, alongside:
SAP IDM and your identity source
IDM faces the same 2027 deadline. Anugal is built to cover both lifecycle and access risk, and if IDM feeds users into Access Control today, settle the identity source first. See SAP IDM migration.
SAP Process Control and Risk Management
Not covered here. This page is about Access Control processes.
For SAP partners and GRC advisers
Deliver the assessment and the migration to Anugal for your clients as a fixed-scope service.
Common Questions About SAP GRC Migration
Planning your move off SAP GRC Access Control? Start here.
When does SAP GRC Access Control 12.0 maintenance end?
Mainstream maintenance for SAP GRC 12.0, which includes Access Control, ends at the end of 2027. Paid extended maintenance is available beyond 2027. Check your own SAP contract for the terms that apply to you.
Doesn't SAP have its own successor to GRC Access Control?
Yes. SAP has announced SAP GRC for SAP HANA as the successor to GRC 12.0. SAP's published plan puts it on HANA databases only, on SAP S/4HANA 2025 or the SAP S/4HANA Foundation 2025 stack, and SAP marks that plan as subject to change. SAP's published plan for the successor involves a platform move, so it is the right moment to decide where your access-risk controls should run. Anugal is built to run them.
Can Anugal take over our SoD rulesets and mitigating controls?
Yes. In discovery we review your rulesets and mitigating controls with you, keep the rules that still reflect a real risk, and migrate them to the Anugal risk library with deKorvai. Each mitigation on Anugal carries an owner, a scope and an expiry. Access requests and approvals, emergency access and access reviews are assessed the same way before anything moves.
How long does an SAP GRC migration to Anugal take?
A typical SAP GRC Access Control migration runs from about six months: discovery, data migration and configuration migration, followed by testing and sign-off. Larger estates move in additional waves.
How do we migrate from SAP GRC Access Control to Anugal?
In six stages: discover, design, migrate, verify and go live, archive, and retire. Risk-analysis results are compared before each wave closes, and Access Control is decommissioned only after the archive is verified and you sign off. The readiness assessment is the first step.
Can we still access firefighter logs and GRC history after retirement?
Yes. Before SAP GRC is retired, its history is moved into a read-only, searchable archive, so audit and security teams can retrieve records whenever they need them.
Do we have to switch everything over at once?
No. We migrate wave by wave. Where continuity needs it, SAP GRC and Anugal run in parallel as a safety mechanism, never as the end state.
How do we keep emergency access controlled during cutover?
Give every emergency access assignment one owner and one review route for the whole cutover window. On Anugal, emergency access is time-bound and scoped, sessions are recorded, and a post-use review is mandatory.
Start with an SAP GRC migration readiness assessment
We review your SAP GRC Access Control estate and show you scope, waves and timeline for the move to Anugal.
Migrating from SAP IDM too? See SAP IDM migration.

