Lesson 5 of 6
The business role in a conversion
7 min
System conversions are often led by IT, and the technical work is genuinely large: database migration, software update, data conversion, custom code adaptation. That leads some organizations to treat the business as a spectator. It is a mistake. Only the business can say whether the converted system produces the right results.
Why business involvement is essential
- Data is transformed, not just copied: customers become business partners, finance data moves into the Universal Journal, inventory valuation moves into the material ledger. Someone must confirm the results are right.
- Simplification items change some processes, and only process owners can decide how to adapt.
- Custom reports and forms the business relies on may break or change.
- Users need to be ready on day one: training, roles and authorizations, and support.
Business deliverables
| Deliverable | What it means | Contoso example |
|---|---|---|
| Process validation | Run key business processes end to end in the converted test system and confirm the results | Order to cash, procure to pay and plan to produce in company code 1710, plants 1710 and 1720 |
| Data validation | Compare key figures before and after conversion and confirm they match | Trial balance, open AR and AP, asset values, stock quantity and value per plant |
| Master data readiness | Cleanse and prepare data in ECC before conversion | Remove duplicate customers and suppliers; complete tax numbers for business partner conversion |
| Role and training readiness | Confirm users can do their jobs with new roles and apps | Credit analysts trained on SAP Credit Management; warehouse on MIGO |
| Cutover sign-off | Formal go or no-go after the final conversion, based on evidence | Finance and operations leads sign after validating production data |
What the business delivers in a conversion.
Data validation: before and after
Financial data conversion moves ECC finance data into the Universal Journal. SAP's conversion process includes reconciliation steps, but the business must still compare its own key figures. The standard pattern is simple: capture key reports before the conversion, run the same reports after, and compare.
| Check | Before conversion (ECC) | After conversion (SAP S/4HANA) | Expected |
|---|---|---|---|
| Trial balance by company code | Balance per G/L account, company code 1710 | Trial Balance app, same period | Identical balances |
| Open customer items | Open AR list by customer | Open AR by business partner | Same totals; customers mapped to business partners |
| Open supplier items | Open AP list by vendor | Open AP by business partner | Same totals |
| Fixed assets | Asset balances and accumulated depreciation | Asset balances in new asset accounting | Same values per asset class |
| Inventory | Stock quantity and value per plant | Stock and material ledger values per plant | Same quantities and values |
Mock conversions and dress rehearsals
Conversions are rehearsed several times on copies of production. Each mock conversion is a chance for the business to practice validation, measure how long it takes, and find data issues early. By the final rehearsal, business validation should be a scripted, timed activity with named people, because on the real cutover weekend it sits on the critical path to go-live.
- Mock 1First conversion of a production copyFind blockers; business tries the validation scripts
- Mock 2Second conversion with fixesFull process and data validation; defects logged
- Dress rehearsalTimed, end-to-end like the real cutoverBusiness validation timed and signed as a rehearsal
- CutoverProduction conversionBusiness validates, signs go or no-go
- HypercareFirst weeks liveKey users support, monitor and fix
Roles and responsibilities in practice
In a well-run conversion, each process area has a process owner who makes decisions on simplification items and signs off results, one or more key users who write and run validation and test scripts and later train colleagues, and data owners who cleanse and validate master data. Finance usually has the heaviest validation load, because every balance must be proven. Plan their time: month-end close and conversion rehearsals compete for the same people, and a validation team that is also closing the books will cut corners.
What would you do?
In Contoso's second mock conversion, the trial balance matches, but open AR is 42,000 USD lower after conversion than before. IT says "finance balances, so the conversion is fine". What should the AR process owner do?
- Only the business can confirm that a converted system produces correct business results.
- Business deliverables: process validation, data validation, master data readiness, role and training readiness, cutover sign-off.
- Validate data by comparing key reports before and after conversion.
- Rehearse validation in mock conversions so it is fast and reliable at cutover.
Check your understanding · not graded
Lesson check
1. Why is business validation needed even in a technical system conversion?
2. What is the basic pattern for data validation in a conversion?
3. What is the purpose of mock conversions for the business?
4. Which master data activity typically happens in ECC before conversion?