SAP S/4HANA· Data assessment
OverviewMCP server
Pre-implementation
  1. Implementation plan
  2. Discovery
  3. Data assessment
  4. Solution design
Implementation
  1. Configuration
  2. Data mapping
  3. Data migration
  4. Testing and UAT
  5. Cutover
Post go-live
  1. Hypercare
  2. Handover
Step 3 of 11 · Pre-implementation · Updated October 26, 2026

SAP S/4HANA data assessment

A data assessment tells you what data exists, how much of it there is, and whether it is ready to move to SAP S/4HANA. Problems found here cost hours. The same problems found at cutover cost the go-live date. superglue's agent reads the source system read-only, counts and tests the records that matter, and reports readiness in plain language.

Start an SAP S/4HANA projectTalk to us

How this step works

What the agent does

  • Reads the source system and makes focused read-only queries. Nothing is written.
  • Builds an inventory of entities, record counts, date ranges and relationships.
  • Tests data quality with real counts: duplicates, missing values, orphaned references and inconsistent codes.
  • Reports readiness as ready, ready with caveats, or blocked.

What you decide and approve

  • Which modules and how much history are in scope.
  • Which issues the client fixes in the source and which the mapping handles.
  • When the findings are good enough to start mapping.

What the client gets

  • A data readiness report with counts and examples.
  • A cleanup list for the client team.

What to look for before a SAP S/4HANA migration

  1. 01

    Run SAP Readiness Check on the ECC system

    It shows the Simplification List items, add-on compatibility and custom code impact for that system. Use it on a greenfield project too, to see which functions and data structures change.

  2. 02

    Check customer and vendor data for Business Partner

    Every customer and vendor becomes a Business Partner, through CVI on a conversion or through the load on a new implementation. Duplicates, missing tax numbers and invalid addresses block both.

  3. 03

    Reconcile open items per company code

    Count open AR, AP and GR/IR items and tie them to the G/L balances. Old uncleared GR/IR items often hide years of differences.

  4. 04

    Check fixed assets against the ledger

    The asset subledger must agree with the asset balance sheet accounts in each company code. New Asset Accounting posts to the Universal Journal in real time, so an old difference shows on day one.

Frequently asked questions

What should you check before a SAP S/4HANA migration?

Run SAP Readiness Check on the ECC system; Check customer and vendor data for Business Partner; Reconcile open items per company code; Check fixed assets against the ledger. The agent checks these read-only and reports readiness.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into SAP S/4HANA?

Common sources are SAP ECC, Oracle E-Business Suite, Microsoft Dynamics AX, JD Edwards and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live SAP S/4HANA project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.