ECC to S/4HANA Migration: A Guide for SAP PS Consultants

·4 min read
ECC to S/4HANA Migration: A Guide for SAP PS Consultants

Mainstream maintenance for SAP ECC ends on 31 December 2027, with optional extended maintenance until the end of 2030 (see SAP's history). For companies that use SAP Project System, the move to S/4HANA raises specific questions: what happens to open projects, their costs and budgets, and their settlement history?

This guide summarizes how to prepare the PS part of an ECC to S/4HANA migration. For what changes functionally, read What Changed for SAP PS in S/4HANA first.

Advertisement

1. Choose the migration approach

There are three main approaches, and each has different consequences for project data:

  • System conversion (brownfield): the existing ECC system is converted to S/4HANA. All projects, their history, settlement rules and configuration are kept. This is the fastest route for PS, but it also carries over old design choices and data quality issues.

  • New implementation (greenfield): a new S/4HANA system is built, usually on SAP standard processes, and only selected data is migrated. For PS this typically means migrating open projects only, and redesigning project profiles and processes.

  • Selective data transition: a mix of both, where configuration and selected data (for example certain company codes or years) are moved with specialized tools. Useful for complex landscapes, but it requires specialized partners.

For PS, the key question is how much project history you need in the new system. Long-running capital or customer projects with years of cost history often push towards conversion or selective transition.

2. Assess your system early

  • SAP Readiness Check: run it on your ECC system to see which simplification items apply to your PS usage, which add-ons are affected and how big the conversion effort is.

  • Simplification items for PS: review each relevant item with the business, since some older functions are no longer available or are only in the compatibility scope.

  • Custom code: PS implementations often include many enhancements, reports and interfaces (see enhancement options). Use the ABAP Test Cockpit checks for S/4HANA to find code that must be adapted, for example code that writes to or reads from tables replaced by the Universal Journal.

  • Finance prerequisites: the move to the Universal Journal, Business Partner and, if planned, event-based revenue recognition has a direct impact on PS and must be designed together with the finance team.

3. Clean up project data before the migration

Data quality work in ECC pays off whatever approach you choose:

  • Close what is finished: set completed projects to technically completed (TECO) or closed (CLSD) after final settlement, and archive old projects where possible.

  • Check settlement rules: make sure all projects with costs have correct settlement rules and that settlements are up to date.

  • Review open commitments: purchase requisitions and purchase orders assigned to projects that are no longer needed should be closed.

  • Align budgets: review budgets and availability control settings on open projects, so that what you migrate makes sense.

4. Migrating open projects (new implementation)

In a greenfield approach, the typical scope for PS is:

  • project definitions and WBS elements of open projects, with their statuses and key attributes;

  • networks and activities, if they are still used for scheduling, procurement or confirmations;

  • budgets and plan values, where needed for availability control and reporting;

  • open purchasing documents and sales documents linked to projects;

  • cost balances, usually brought over as totals per WBS element rather than full line-item history.

The SAP S/4HANA Migration Cockpit is the standard tool for loading data in a new implementation and offers predefined migration objects, including objects for project data. Check which PS objects are available for your target release and plan custom solutions for anything not covered.

LSMW was the workhorse of many ECC migrations, as described in the lessons learned on our Data Migration page, and it is still technically available in S/4HANA. However, SAP no longer recommends it for S/4HANA: the Migration Cockpit is the strategic tool, with predefined objects that SAP maintains for each release. If you still consider LSMW for specific cases, check the related SAP Notes for your release first.

Advertisement

5. Test the full project lifecycle

Unit tests of single transactions are not enough. Plan integration tests that run complete project scenarios:

  • create a project, plan costs and revenues, assign budget and check availability control;

  • procure materials and services for networks, and post confirmations and timesheets;

  • bill the customer (milestone or resource-related billing);

  • run a complete period-end closing: overhead, revenue recognition or results analysis, and settlement;

  • check the reports and Fiori apps your users rely on.

6. Cutover and go-live

  • complete period-end closing and final settlement in ECC before the cutover;

  • freeze project structure changes during the cutover window;

  • reconcile migrated project totals (costs, budgets, commitments) between the old and new system, and get business sign-off;

  • plan hypercare with PS experts available for the first period-end closing in S/4HANA, which is where most issues appear.

Key takeaways

  • Decide early how much project history you need: it drives the choice of approach.

  • Run the Readiness Check and review the PS simplification items with the business.

  • Clean up projects, settlement rules and commitments in ECC before migrating.

  • Test complete project lifecycles, including period-end closing, not just single transactions.

  • S/4HANA projects usually follow the SAP Activate methodology, so align your PS workstream with its phases.

Every migration is different. Use this guide as a checklist and always confirm details in the SAP documentation for your target release.

Advertisement
Looking for the reference pages? See the SAP PS transaction codes, database tables and module overview.