Three assessment agents to get your SAP estate ready
Each one is an agent, not a questionnaire. A supervisor routes specialist agents across the estate read-only, a human validates the flags, and a scoring agent hands you a costed, prioritized roadmap. They share one knowledge graph and the same governance with the agents that run your support, so an assessment flows straight into the work it recommends. Whether you run SAP support or buy it from a partner, this is the read-only way to see exactly where your estate stands.
The first assessment is no-cost. It runs read-only, needs no production access, and your business data and PII never go to a model or leave your tenant. You keep the numbers.
ECC to S/4HANA readiness
An agent that scores custom-code health, table complexity, configuration footprint and integration risk across the estate. Its upgrade analyzer turns every gap into a fix and recommends the path: greenfield, brownfield, Bluefield or technical upgrade, with a costed roadmap.
Benefit: a de-risked, smaller-scope migration.
Details →What to automate next
An agent that mines live ticket history for recurring issues, ranks them by volume and resolution time, and proposes the candidate agents and prevention plays with the highest return.
Benefit: a measurably lower cost to serve.
See how it works →Lakehouse & AI feasibility
An agent that scores data quality, master data, lineage and governance, then rates readiness to feed Datasphere, Business Data Cloud or Databricks and to deploy AI safely.
Benefit: a trustworthy, governed data foundation.
Details →ECC to S/4HANA, scored and costed
A supervisor routes specialist agents over the estate, a human validates the flags, and a scoring agent turns four weighted dimensions into a 0 to 100 readiness score and a phased, costed roadmap. The biggest lever: 40 to 60% of custom code is typically unused and can be decommissioned, not migrated.
Custom-code health
Z-objects, modifications and deprecated APIs scanned via ATC and the Simplification database, scoped by real usage.
Table complexity
Volumes, growth and archiving candidates that drive the data-migration effort.
Integration risk
Interface count, adapter types and external connections, the main technical risk.
Configuration footprint
Customizing scope, which sets process and testing complexity.
A roadmap, not a backlog
Code scanners stop at the ABAP layer. This agent orchestrates code, data, configuration and integration into one weighted, costed, board-ready roadmap.
Delete, don't migrate
It proves which custom code is actually unused, so you retire it instead of paying to remediate and carry it forward.
Grounded in real usage
The assessment reads the same production telemetry our run-agents collect, and the agents that assess hand straight off to the agents that support you after cutover.
Metadata only
Claude reasons over code structure and catalogs; your business data and PII never leave the tenant. Scoring runs in your environment.
Every gap, mapped to a fix
The upgrade analyzer reads the ATC and Simplification Database findings, classifies each object by real production usage, and turns a raw issue list into typed, costed remediation. Every gap gets an action, not just a flag.
Decommission
The 40 to 60% of custom code that is never executed in production, proven unused and retired instead of migrated (custom-code decommissioning, CCLM).
Functional redesign
Objects that collide with simplified S/4HANA processes, routed to an application expert with the change scoped.
Technical adaptation
Deprecated APIs and changed table access, split into quick-fix-automatable and manual.
S/4HANA compatibility scope
Eligible technical objects routed through S/4HANA compatibility views so they keep running through cutover, then redesigned on your schedule, not the project's.
The path that fits your estate
The score and the gap map point to one of four paths, with the rationale and the cost of each, so the choice is evidence-led, not a default.
Greenfield
A new build with processes re-engineered to clean core. Best when the configuration footprint is heavy and you want a fresh start.
Brownfield
A system conversion that preserves configuration and history. Best when the estate is healthy and continuity matters most.
Bluefield · selective data transition
Move selected data by time-slice or company code and leave obsolete data behind. A clean target without starting over.
Technical upgrade
The smallest technical step onto S/4HANA, processes untouched, with technical objects parked in compatibility scope to redesign later.
Pick the path (greenfield, brownfield, Bluefield or technical upgrade), sign off the dead-code decommission list and the compatibility-scope carry-forwards, and fund a phased program, with the run-agents staged to execute and support it.
A de-risked, smaller-scope migration: less code to carry, a defensible cost and timeline, and continuity into AMS once live.
Output: readiness score, decommission list with savings, remediation backlog split functional-redesign vs technical-adaptation vs compatibility-scope carry-forward, path recommendation across greenfield, brownfield, Bluefield and technical upgrade, costed phased roadmap, risk register. Figures are modeled and illustrative, validated per engagement.
What to automate next, ranked by return
This agent already runs in the product. It reads the live ticket history read-only, clusters recurring issues into signatures, ranks them by volume and resolution time, and proposes the candidate agent for each plus the prevention plays that stop tickets before they open, laid out as a phased rollout.
Recurring signatures
Cluster the queue into the issues that actually repeat.
By volume and MTTR
Surface where automation returns the most, fastest.
Candidate agents
The agent and prevention play to deploy for each signature.
A phased rollout
Quick wins, then approved agents, then prevention.
Approve which candidate agents to deploy and in what order, set the autonomy and approval thresholds, and turn on the first prevention plays.
A measurably lower cost to serve: fewer repeat tickets, faster resolution, and engineer time redirected from firefighting to higher-value work.
Ready for the lakehouse, ready for AI
SAP's data future is Business Data Cloud (built with Databricks) and Datasphere, with BW/4HANA maintenance ending in the same window. This agent scores whether the data is clean, governed and traceable enough to feed a lakehouse and to deploy AI safely. Governance and lineage are first-class, not a footnote.
Quality & master data
Completeness, duplicates and validity by domain; MDG hygiene across vendor, customer, material and finance; BW debt to retire or carry forward.
Traceable end to end
Lineage via the Datasphere Catalog (source to BW to views to consumption, with impact analysis), MDG, Information Steward, Data Access Controls plus S/4 authorizations, ILM retention, and the Unity Catalog hand-off into Business Data Cloud / Databricks.
Use cases worth doing
Each candidate scored on value vs data-readiness, including Joule and custom-agent fit, with the PII boundary made explicit.
Scores readiness for: SAP Datasphere · SAP Business Data Cloud · Databricks · Snowflake · Microsoft Fabric · Joule & custom agents
Profile, trace, score
Specialist agents profile data, trace lineage and score AI use cases under one supervisor with human approval, not a one-off snapshot.
Source to consumption
Governed and traceable from the SAP source through to where AI consumes it, so you can trust what you feed a model.
We build it, not just report it
Backed by NuStudio's background in data and analytics, the same team designs the lakehouse and the models the assessment recommends.
Metadata only
Claude reasons over schemas and profiling statistics; business data and PII never leave the tenant. Profiling and scoring ML run in your environment.
Fix the top master-data and lineage gaps, pick the lakehouse target and the first AI use cases to fund, and get a governed extraction plan, with the remediation and build executed for you.
A trustworthy, governed, traceable data foundation: AI and Joule deployed safely and sooner, with the PII boundary proven, not assumed.
Trust boundary: Claude reasons over metadata only (schemas, profiling statistics, lineage, catalogs). Business data and PII never leave the tenant; profiling and scoring run in the client environment. Targets and figures are illustrative.
See what your SAP estate is ready for.
A fixed-scope, fixed-fee read of the estate, scored and costed, with a roadmap you can fund. The findings flow straight into the agents that do the work.