Cloud Migration

Migration assessments are often spreadsheets built by hand. Configuration without a cloud counterpart, obsolete transactions and custom functionality that duplicates standard scope are found too late, when the target system is already being built.

• ECC2Cloud Navigator

  Custom code remediation & obsolete transaction migration roadmap

  ECC2CLOUD_NAVIGATOR

• SPRO2Cloud

  On-premise IMG/SPRO configuration to Cloud CBC mapping

  SPRO2CLOUD

• SAP Gap Radar

  Fit-to-standard vs custom delta analyzer with Clean Core recommendations

  SAP_GAP_RADAR

• Migration Template Intelligence

  Migration Cockpit load files (templates) validated against their declared schema: mandatory fields, lengths, types, keys, hierarchy

  MIGRATION_TEMPLATE_INTELLIGENCE

• IMG/SPRO activities without a counterpart in Central Business Configuration
• Transactions and interfaces that are obsolete or redesigned in the cloud target
• Custom functionality overlapping with standard scope items
• A remediation roadmap for custom code, IDocs, BAPIs and obsolete transactions

• Clean core extensibility explained: tiers, released APIs and classic modifications

  A practical overview of how SAP classifies extensions by their upgrade stability, from ABAP Cloud on released APIs to classic modifications, and how to assess existing custom code.

• From SPRO IMG customizing to SSCUIs and Central Business Configuration (CBC)

  How classic SPRO IMG customizing tables map to Self-Service Configuration UIs (SSCUIs) and Central Business Configuration in SAP S/4HANA Cloud, and how to spot unsupported table settings early.

Which engines does the Cloud Migration preflight run?

Cloud Migration runs 4 deterministic engines: ECC2Cloud Navigator, SPRO2Cloud, SAP Gap Radar, and Migration Template Intelligence. Each engine documents its rules and input contract in the engine catalog.

Which files do I need for Cloud Migration?

The engines in this area accept these file formats: CSV, JSON, TEXT, XLSX, XML, and ZIP. You create the exports in SAP and upload them; no direct connection to your SAP system is needed. The outbound-only local agent is optional.

Are the findings produced by AI?

No. Findings come from deterministic rules: identical exports produce identical findings. Where AI helps with explanations, the confidence of that content is capped at INFERRED and marked as such.

How is each finding backed?

Findings reference evidence in the uploaded file: its path, the line and column where the format has them, a redacted snippet and the SHA-256 hash of the file. Each finding carries a confidence class (VERIFIED, RULE_DERIVED, INFERRED or UNKNOWN); findings without verifiable evidence are demoted to UNKNOWN.