# SAP S/4HANA Pre-Conversion Technical Checklist

> Source: https://netray.co/tools/sap-s4hana-pre-conversion-technical-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A checklist of the technical preparation items to close before running SUM on a system conversion from ECC to S/4HANA.

## Category

sap

## Erp

SAP S/4HANA

## Audience

- SAP Basis administrator
- SAP program manager
- SAP ABAP developer

## Tool

**Kind:** checklist

**Groups:**

#### Scope and governance

**Items:**

**Text:** Conversion approach confirmed: system conversion, new implementation or selective data transition

**Critical:** true

**Text:** Target S/4HANA release and feature pack or stack chosen

**Critical:** true

SAP Readiness Check run and results reviewed with owners

**Text:** Simplification Item Check run in the system and findings logged

**Critical:** true

**Text:** Add-ons and partner products checked for S/4HANA compatibility

**Critical:** true

Sandbox, development, quality and production conversion sequence agreed

#### Basis and infrastructure

**Items:**

**Text:** System is Unicode or Unicode conversion is planned

**Critical:** true

**Text:** Source system on a supported release and support package level for the conversion

**Critical:** true

**Text:** Maintenance Planner run and stack file generated

**Critical:** true

SUM and DMO versions downloaded and approved

HANA hardware or cloud sizing confirmed with the sizing report

Backup and restore tested on the target database

Interfaces, RFC destinations and printers inventoried for re-pointing

**Text:** Dry run on a production copy completed with downtime measured

**Critical:** true

#### Master data and finance

**Items:**

**Text:** Customer and vendor CVI synchronization complete with zero blocking errors

**Critical:** true

Duplicate and obsolete business partners cleansed

**Text:** Classic asset accounting converted to New Asset Accounting where required

**Critical:** true

**Text:** New G/L active if the system still runs classic G/L

**Critical:** true

**Text:** FI and CO reconciliation clean before conversion

**Critical:** true

Material Ledger plan prepared and open period posting reviewed

Open items and open documents reduced before cutover

#### Custom code and interfaces

**Items:**

**Text:** SCMON collected over a full business cycle in production

**Critical:** true

Custom code inventory built and unused objects marked for retirement

**Text:** ATC S/4HANA readiness checks run on in-scope code

**Critical:** true

Code touching MKPF, MSEG, KONV and finance tables reviewed

Interfaces checked for material number length and Business Partner changes

Third party and non-SAP integrations tested against the target API set

#### Data volume and testing

**Items:**

**Text:** Largest tables identified and archiving jobs run

**Critical:** true

Retention rules agreed with finance and legal before deleting data

Authorization roles and Fiori catalogs designed for the target

**Text:** Regression test scope defined for finance, logistics and interfaces

**Critical:** true

Key user training plan and test scripts updated for BP and MIGO

Go and no-go criteria for each dry run documented

**Scoring Note:** Close every critical item before the first production dry run. Open critical items normally become cutover risks.

## Content

**Intro:** Most delays in a system conversion come from preparation items found late. This checklist groups the technical work to finish before you run SUM, with the blocking items marked critical.

**Sections:**

#### How to use this checklist

**Body:** Assign each group to an owner: program management for governance, Basis for infrastructure, finance leads for master data and ledger items, development for custom code, and test leads for data volume and testing. Review the list at each steering meeting and use the critical flags to decide whether a dry run can start. Export the checked state to PDF or Excel to keep a record of readiness evidence for audit and sponsors.

**Bullets:**

- Review weekly during preparation
- Treat critical items as gates, not suggestions
- Keep evidence links for each closed item

#### The gates that stop a conversion

**Body:** Four items most often stop a technical conversion outright: CVI synchronization errors, missing Unicode, add-ons without S/4HANA support, and unresolved errors from the Simplification Item Check. Finance consistency matters just as much, because reconciliation breaks found during conversion are far more expensive to fix than in advance. Resolve these first, then spend remaining time on custom code and data volume.

#### Dry runs and common mistakes

**Body:** At least one full dry run on a recent production copy should measure real downtime and expose data issues that sandboxes with sample data hide. Common mistakes are skipping dry runs, converting a sandbox with unrepresentative data, and treating the Readiness Check as a one-time report. Also keep a rollback plan and backup validated before every production attempt.

**Cta:** If you want a second reviewer on readiness evidence before your first dry run, Netray can look at it with you.

**Faq:**

#### Is this checklist only for system conversions?

**Answer:** It is written for system conversion from ECC. For new implementations many Basis items do not apply, but master data, finance, custom code review and testing items still help.

#### How many dry runs are enough?

**Answer:** Many programs plan at least two or three on production copies. The right number depends on downtime targets, data volume and the number of defects found in earlier runs.

#### Who should own the critical items?

**Answer:** Give each one a named owner and date. Basis owns infrastructure, finance owns ledger items, and the data lead owns CVI. Shared ownership usually means nobody tracks it.

#### Can I reduce downtime with this list?

**Answer:** Indirectly. Archiving, clean data and tested procedures reduce runtime and rework. Techniques such as near-zero downtime options also exist, but check eligibility with SAP documentation.

## Search terms

s4hana pre conversion checklist, ecc to s4hana technical prerequisites, s4hana system conversion checklist, sum dry run checklist, unicode cvi pre check, s4hana basis checklist, maintenance planner stack xml, s4hana conversion preparation

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json