DE Book a demo
Transformation methodology

Measure first, then decide.

An SAP transformation usually starts with workshops that collect assumptions about the system. With Conjola, the current state is on the table beforehand: what is used, which custom code runs, how orders really move through the system. The workshops then decide on facts.

Book a demo See the product

Whether it is an S/4HANA move, public cloud, an acquisition or a template rollout: this page describes the approach when a transformation is due. Without a project, Conjola stays useful too, as the current state of your system for documentation, questions to the system and your AI agents.

The same workshop, a different basis

The difference lies before the first meeting with the business.

Usual

  1. 1 Workshops with the business
  2. 2 Questionnaires and experience
  3. 3 Fit-to-standard based on assumptions

What is rarely used rarely comes up in the workshop, and gets migrated anyway.

With Conjola

  1. 1 Extract from the system, no live access
  2. 2 Findings per feature, process and object
  3. 3 The workshop decides on the findings

Every decision has a number behind it that anyone can check.

From the system, not from the interview

Conjola reads the current state from the data of your SAP system. That is the basis for every phase that follows.

What really runs?

Usage per feature

Which features, transactions and reports are used, and how often. What nobody uses any more does not need to move.

What have we built?

Custom code

Custom developments grouped by AI and mapped to the features they carry.

How does the process run?

Process Discovery

Process chains from real document flows, including the variants nobody mentions in the workshop.

What is the system wired to?

Interfaces and jobs

Channel, direction and partner of every interface, plus the background jobs.

How clean is the data?

Master data quality

Duplicates among vendors and customers, before they move into the new system.

Does the cloud fit?

Public Cloud Fit

Fit assessment for SAP Public Cloud, decided and justified point by point.

Lean, and included

Project board, knowledge base and, soon, test cases are deliberately lean. For many projects that is enough. If you need more, add your own tool, and the current state stays in Conjola.

Six phases, one fact base

Conjola carries the approach on its own. If you already use SAP Cloud ALM, Signavio or LeanIX, you keep them, and Conjola hands over where it fits.

01

Connect

SAP Activate: Discover / Prepare
02

Capture

SAP Activate: Discover
03

Decide

SAP Activate: Explore
04

Hand over

SAP Activate: Explore → Realize
05

Implement

SAP Activate: Realize / Deploy
06

Re-measure & run

SAP Activate: Run
Conjola Fact base
Import ABAP transports, run reports, upload extracts. Results on the next business day, no live access.
  • Usage per feature and transaction
  • Custom code, grouped by AI
  • Interfaces and jobs
  • Process chains from real document flows
  • Master data duplicates
  • IT systems & contracts
  • Public Cloud Fit with a decision per point
  • Processes as BPMN
  • Every decision backed by a finding
  • Task straight from the finding
  • Project board with sprints
  • Specs in the knowledge base
Test cases from the process model In development
  • New extract after go-live: what is used now, what has dropped away?
  • Knowledge base and documentation of your system, for your team and your AI agents
Aurola AI assistant in Conjola, across every phase
On board from the first extract
Which features does sales really use? Every answer names its source.
Where is table ZSD_PROVISION still used? Plus proposals for the feature map and process model that you accept or reject.
Which custom code belongs to commission settlement? Plus task proposals on the project board.
Which programs call BAPI_SALESORDER_CHANGE? Your coding agent asks the same via MCP.
Which features have not been used since go-live?
SAP Cloud ALM
Best-practice processes as the target reference in fit-to-standard
Requirements and backlog transferred by hand
Tests, transports, cutover
Operations and monitoring
SAP Signavio
Target process models BPMN file, both directions
Process governance
SAP LeanIX
Application portfolio. Conjola adds the depth inside the SAP system. transferred by hand
Target architecture
Application lifecycle
SAP Readiness Check only for an S/4HANA move
Runs alongside the Conjola extract
Set the affected items against actual usage
Development and code tools
Reworking the custom code
Your other tools if you have them
Any BPMN modeller BPMN file
Jira or a spreadsheet, if the board is not enough
Your test tool
  1. 01

    Connect

    SAP Activate: Discover / Prepare
    Conjola
    Import ABAP transports, run reports, upload extracts. Results on the next business day, no live access.
    Aurola
    On board from the first extract
    SAP Readiness Check
    Runs alongside the Conjola extract
  2. 02

    Capture

    SAP Activate: Discover
    Conjola
    • Usage per feature and transaction
    • Custom code, grouped by AI
    • Interfaces and jobs
    • Process chains from real document flows
    • Master data duplicates
    • IT systems & contracts
    Aurola
    Which features does sales really use? Every answer names its source.
    SAP LeanIX
    Application portfolio. Conjola adds the depth inside the SAP system. transferred by hand
  3. 03

    Decide

    SAP Activate: Explore
    Conjola
    • Public Cloud Fit with a decision per point
    • Processes as BPMN
    • Every decision backed by a finding
    Aurola
    Where is table ZSD_PROVISION still used? Plus proposals for the feature map and process model that you accept or reject.
    SAP Cloud ALM
    Best-practice processes as the target reference in fit-to-standard
    SAP Signavio
    Target process models BPMN file, both directions
    SAP LeanIX
    Target architecture
    SAP Readiness Check
    Set the affected items against actual usage
    Your other tools
    Any BPMN modeller BPMN file
  4. 04

    Hand over

    SAP Activate: Explore → Realize
    Conjola
    • Task straight from the finding
    • Project board with sprints
    • Specs in the knowledge base
    Aurola
    Which custom code belongs to commission settlement? Plus task proposals on the project board.
    SAP Cloud ALM
    Requirements and backlog transferred by hand
    SAP Signavio
    Process governance
    Your other tools
    Jira or a spreadsheet, if the board is not enough
  5. 05

    Implement

    SAP Activate: Realize / Deploy
    Conjola
    Test cases from the process model In development
    Aurola
    Which programs call BAPI_SALESORDER_CHANGE? Your coding agent asks the same via MCP.
    SAP Cloud ALM
    Tests, transports, cutover
    Development and code tools
    Reworking the custom code
    Your other tools
    Your test tool
  6. 06

    Re-measure & run

    SAP Activate: Run
    Conjola
    • New extract after go-live: what is used now, what has dropped away?
    • Knowledge base and documentation of your system, for your team and your AI agents
    Aurola
    Which features have not been used since go-live?
    SAP Cloud ALM
    Operations and monitoring
    SAP LeanIX
    Application lifecycle

Handovers run via BPMN file, the read-only MCP access, or by hand.

Every phase runs in Conjola. Where you want to keep a tool of your own, Conjola hands over via BPMN file or the read-only MCP access.

Who does what

The consultant role is taken by your implementation partner or by Conjola Advisory. Conjola itself is the platform.

Phase IT / BasisBusinessConsultantConjola
Connect leads: Transports, reports – contributes: Sets up platform: Reads in the extracts
Capture –– contributes: Reads the results platform: Analyses
Decide contributes: Technical input leads: Decides leads: Moderates platform: Delivers the findings
Hand over – contributes: Reviews specs leads: Writes tasks and specs platform: Board and knowledge base
Implement leads: Builds, transports contributes: Tests leads: Steers –
Re-measure & run leads: New extract contributes: Asks questions contributes: Compares platform: Analyses, documents
leads contributes platform

What Conjola passes on

The fact base does not stay locked inside Conjola.

File

Process models as BPMN

The captured steps become a BPMN model that any modelling tool opens. Uploaded models are checked before they are read in.

Read-only

MCP access for AI agents

Your coding agent queries the fact base directly, for example which objects belong to a feature. The access is read-only.

By hand

Tasks and systems

You transfer requirements to SAP Cloud ALM and systems to SAP LeanIX yourself.

Questions about the approach

Do we need SAP Cloud ALM, Signavio or LeanIX?

No. All six phases run with Conjola alone. If you already have those tools, you keep them, and Conjola supplies them with the current state they do not capture themselves.

Does Conjola replace the SAP Readiness Check?

No. The Readiness Check shows what an S/4HANA move affects. Conjola shows which of it is really used. Together they make the list that needs working through.

Do we need a project to use Conjola?

No. This methodology describes its use in a transformation. Day to day, Conjola keeps the current state of your system up to date: for documentation and specs, for questions to Aurola and for AI agents via the MCP access.

Is this SAP Activate?

No, but the phases map onto it. If you work with SAP Activate, you will find the matching Activate phase under every phase.

What would this look like for your system?

In a short demo we'll show you how Conjola turns your system data into a basis for decisions.

Book a demo