The 2027 Deadline and What It Actually Means
SAP's mainstream maintenance for SAP ECC (ERP Central Component) ends on December 31, 2027. After this date, SAP will not release new legal and regulatory updates, security patches, or functional corrections for ECC. Extended maintenance is available at significant additional cost, but it is a delay tactic, not a strategy.
For automotive enterprises, the consequences of running unsupported ERP software are severe: audit findings in IATF 16949 and ISO 27001 reviews, inability to meet new regulatory reporting requirements (e.g., EU Corporate Sustainability Reporting Directive), and vendor support gaps that slow innovation. The industry consensus is clear: migrate to S/4HANA before 2027.
The Three Migration Paths Compared
SAP S/4HANA Migration Path Comparison
| Factor | System Conversion (Brownfield) | Selective Data Transition | Greenfield (New Implementation) |
|---|---|---|---|
| Timeline | 12–18 months | 18–30 months | 24–36 months |
| Custom code retention | High (remediate existing Z-code) | Partial (selective migration) | Minimal (redesign from scratch) |
| Process disruption | Low–Medium | Medium | High |
| Business transformation opportunity | Limited | Medium | High |
| Data migration complexity | Low (in-place conversion) | High (selective extraction) | High (full data migration) |
| Suitable for | Complex landscapes, time-sensitive deadlines | Consolidating multiple ECC systems | Complete process redesign mandated |
For most automotive enterprises — particularly Tier-1 suppliers with established, IATF-certified manufacturing processes — system conversion (brownfield) is the practical choice. It minimizes disruption to production-critical processes while meeting the 2027 deadline. Greenfield reimplementations are appropriate when a company is simultaneously undergoing significant business transformation, such as a merger or carve-out.
The Custom Code Problem: Z-Code in Automotive SAP Systems
Definition
Z-Code (Custom ABAP)
Custom developments in SAP systems, typically prefixed with 'Z' or 'Y', created by in-house developers or implementation partners to extend or modify standard SAP functionality. Automotive SAP systems often carry 10,000–50,000+ custom objects accumulated over 15–20 years of operation.
Custom ABAP code is consistently the biggest technical risk in automotive SAP migrations. SAP's Readiness Check will identify incompatible objects, but a raw object count tells you little about business risk. A custom Z-program used daily by the production planning team is categorically different from an obsolete Z-report no one has run in five years.
The correct approach is a three-stage custom code analysis: (1) usage profiling — identify which custom objects are actually executed in production; (2) S/4HANA compatibility assessment — determine which used objects require remediation; (3) business criticality classification — prioritize remediation by business impact.
In our experience with automotive SAP landscapes, typically 40–60% of custom objects can be retired without business impact (they are simply unused), reducing the actual remediation scope significantly.
Automotive-Specific SAP Considerations
Standard SAP S/4HANA migration guides do not account for automotive-specific complexity:
**Production Planning (PP) integration**: Automotive PP processes — sequence scheduling, line balancing, JIT/JIS delivery — have specific S/4HANA behaviors that differ from ECC. Production planners must be involved in UAT from the beginning.
**Quality Management (QM) with IATF 16949**: QM customizations supporting IATF 16949 quality records must be carefully evaluated for conversion. Loss of QM data integrity is a major audit risk.
**Supplier portal and EDI integration**: ODETTE EDI connections and supplier portal integrations need to be tested against S/4HANA's updated IDoc and API structures.
**TISAX implications**: An ERP migration is a significant change event under your ISMS. Your TISAX documentation (risk register, asset inventory, change management records) must be updated to reflect the migration, and your TISAX auditor should be informed.