Unclear migration scope
Which functions, transactions and company codes are really in production? Without a data basis, scope stays a guess — and guesses get expensive.
Solution · S/4HANA migration
Know what you migrate — before you migrate
Brownfield or greenfield: the biggest cost driver of any S/4HANA migration is uncertainty about the as-is state. From your system's extracts, Conjola shows what is actually used, what each custom development stands for and how everything connects — and makes the migration scope tangible.
The challenge
Classic migration projects start from a blurry picture.
Custom code as a black box
Custom developments and modifications grow over years. What does each object stand for, what belongs together, what do you just carry along? Whoever wrote the code has often long since left.
Carrying dead weight
What is never questioned gets migrated anyway. Unused transactions, functions and custom developments add effort, test load and risk with no return.
How Conjola helps
Your system's data becomes a defensible basis for decisions — not workshops.
Know the real usage
Feature Insights and transaction usage from ST03N show, per company code and system, what is active and what lies idle. Separate the migration core from ballast.
Understand custom code
The AI describes every Z object by purpose, anchors it in the feature map via tables, transactions and function modules, and groups the rest by topic. You see where developments overlap functionally — and, with every new import, the delta.
Map & functional specs
The feature map structures your landscape across four levels and separates standard from custom. Alongside it, versioned functional specs grow in the knowledge base — the AI assistant proposes, you accept or discard.
Step by step
Create the extracts
You import the Conjola transports, run the reports and upload the extracts: custom developments, usage, data dictionary, org structure. Business data is only read; we never access your system.
Assess usage
Transaction usage and Feature Insights per company code and system reveal which features are genuinely used in production — and which are not.
Derive scope
The active core is separated from ballast, custom developments are described and assigned to features. What is to be retired, you note right on the object — migration scope becomes concrete and justifiable.
Document & carry forward
Functional specs live in the knowledge base, linked to features and code. Every further extract shows the delta: changes are flagged, assignments and comments are kept.
Ready to understand your SAP landscape?
In a short demo we'll show you how Conjola turns your system data into a basis for decisions.
Book a demo