Public Cloud Fit

Cloud fit, before the project starts

Public Cloud Fit matches your really-used processes and features against the scope item catalog of SAP S/4HANA Cloud Public Edition. So you see early what fits, where gaps are and where it gets critical — not halfway through the migration project.

How the assessment works

Four steps from a used feature to a defensible fit statement.

01

Capture usage

From Process Discovery and Feature Map comes what you actually use — standard and custom functionality alike.

02

Match against scope

Each used feature is checked against the current Public Cloud scope item catalog.

03

Rate the fit

Per feature you get a traffic light: fits, has a gap, or is critical for clean core.

04

Compile the result

The individual ratings condense into a fit picture across the whole landscape.

Fit categories

Every feature lands in one of three traffic lights.

Fits

Directly covered

The feature maps to a standard scope item. Adopt without change — clean core stays intact.

Gap

Adjustment needed

Partially covered: a side-by-side extension, process change or best-practice variant closes the gap.

Critical

No standard path

Deep custom development with no cloud equivalent. Needs a decision: retire, rethink or keep in scope.

What you get as a result

A basis for decisions, not a gut call.

Fit rate across the landscape

A clear percentage, e.g. “78 % directly covered” — broken down per business area, not a blanket figure.

Prioritized gap list

Every gap with category, affected org units and volume — sorted by effort and impact.

Ready to understand your SAP landscape?

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

Book a demo