Conjola turns your SAP extracts into a map of what your system can do and what you actually use — and you talk to that knowledge base in plain language. No workshops, no live access to your production system.
Software, not workshops — built from real system data, not guesswork.
Feature Map, Feature Insights and custom-code analysis add up to a map of your application landscape: what exists, what is used intensively, what lies idle — and where your Z programs overbuild the standard, grouped by topic instead of listed. Down to company-code level.
Ask in plain language — Aurola, the AI assistant inside Conjola, answers from the prepared knowledge base, not from raw tables. And Aurola contributes: the conversation turns into proposals for your functional spec that you accept or discard — anchored to that same data.
Questions about the system are answered from your knowledge base and functional specs — not from production. Conjola works exclusively on extracts: no live access, no way back, a scope defined upfront. Where an answer comes from and what it may see is governed — the AI use case that clears security and Basis.
Feature and transaction usage per company code, the data model and the classification of your custom developments via anchors in the code are derived deterministically from your extracts — traceable, not guessed. That is what the three differentiators rest on.
Every module in detail — Feature Map, custom-code analysis, Feature Insights, knowledge base and functional specs, Process Discovery, Public Cloud Fit, master data quality and MCP access, on a secure, multi-tenant platform. See all modules →
Conjola has an MCP endpoint. Your coding agent — Claude Code, for example — queries your feature map, your custom developments and your knowledge base directly. It no longer has to search, and it no longer has to guess.
> What is attached to the credit limit check in sales?
conjola · search("credit limit check")
Capability Order-to-Cash › Credit management Features 3 — one with custom logic Z objects ZSD_CREDIT_CHECK, ZSD_CREDIT_RELEASE Usage VKM3 — CC 1000, 2 systems Spec “Credit release 2026” (v4)
> Where exactly does ZSD_CREDIT_CHECK check the release limit?
conjola · source_search("release limit", ZSD_CREDIT_CHECK)
2 matches. Source code released by the tenant, access logged.
Instead of reading forty files, the agent asks a question and gets an answer. That is the difference between a context window full of noise and one that hits the point — and it shows up directly in runtime and cost.
The agent reads the state of your latest extract — feature map, custom developments, data model, functional specs — instead of documentation from three years ago. Writing back what it got done is the next step on the roadmap.
The token carries its tenant and landscape fixed and grants read access only. Whether your custom code may leave the platform is the tenant's decision — not the individual developer's.
Standard MCP — with a setup guide for Claude Code; other MCP-capable clients such as Codex CLI or GitHub Copilot connect the same way. How the MCP access works →
Whenever decisions about your SAP landscape are due and you need facts instead of assumptions.
Before you migrate, Conjola shows the real as-is state: which functions are actually used — down to company-code level — and what your custom developments do in business terms.
Hundreds of Z-programs whose purpose is barely documented anymore? The AI analysis describes each custom development, groups them by topic and shows where they overlap functionally.
Instead of weeks of interviews, the documentation comes from the system itself: feature map, usage and custom developments from the extracts — and functional specs written with the AI assistant right alongside.
Consultants get a solid, per-client factual basis, multi-tenant — for proposals, assessments and roadmaps as equals.
An acquired system is to move onto the group template? Conjola prepares both systems the same way and puts them side by side — so you see what the template already covers and what the new business needs on top.
Want to see what Conjola can do for you? First we show you the platform, then your own system in it. Once the extracts are in, your results are ready on the next business day.
In a demo session we present the platform and its automated analyses — compact, in a short time.
You import our ABAP transports into your system. They contain ready-made extraction reports — read-only, without changing your business data.
With the supplied reports you create the extracts yourself at short notice and upload them. No system access for us, no database coupling.
On the next business day after upload, your feature map, usage per company code and the analysis of your custom developments are ready.
You get full access to the platform after signing the contract.
What happens next: the transformation methodology →In a short demo we'll show you how Conjola turns your system data into a basis for decisions.
Book a demo