The upgrade problem nobody wants to talk about
SAP has set a hard deadline: ECC reaches end of mainstream maintenance in 2027. Every SAP customer must migrate to S/4HANA. But the migration itself isn’t the hard part — the custom code is.
2.5M+
Avg. Lines of Custom ABAP
70%
Budget on Custom Code
2–4 yr
Typical Timeline
3x
Avg. Cost Overrun
Most organizations have spent decades layering custom transactions, reports, workflows, and interfaces on top of SAP ECC. When it’s time to move to S/4HANA, every one of those customizations becomes a migration liability — code that must be analyzed, refactored, retested, or rebuilt from scratch.
SAP itself recommends a “clean core” strategy: keep S/4HANA as close to standard as possible. But for organizations that already depend on custom processes, the question is brutal: where do those customizations go?
Six challenges that stall every S/4HANA migration
Custom ABAP Remediation
Millions of lines of custom code must be analyzed, refactored for S/4HANA compatibility, or rewritten entirely. Many programs use deprecated APIs and obsolete data models with no S/4HANA equivalent.
Business Process Disruption
Custom transactions and workflow variants that employees rely on daily don’t survive the migration. Teams lose productivity during the gap between decommissioning old processes and standing up new ones.
Integration Breakage
Custom RFCs, BAPIs, and middleware interfaces that connect SAP to other enterprise systems need to be re-architected. Every custom integration point is a potential failure during cutover.
Re-Customization Cycle
After spending years migrating to clean S/4HANA, business requirements immediately push teams to start customizing again — restarting the same cycle that made the upgrade painful in the first place.
User Adoption Friction
SAP Fiori apps deliver a standard UX that doesn’t match how teams actually work. Users resist the migration because the new interface feels like a downgrade from the custom screens they’ve used for years.
ABAP Talent Scarcity
The developers who built the original customizations have retired or moved on. Organizations face a shrinking talent pool for ABAP skills at the exact moment they need them most.
The Core Tension
SAP’s “clean core” guidance is correct: S/4HANA works best out of the box. But businesses still need the custom processes that drove them to customize ECC in the first place. The question isn’t whether to customize — it’s where.
Two plays, one principle: keep SAP clean
The rule is simple: if SAP does it well out of the box, let SAP do it. For everything else — the business-specific processes, the multi-system workflows, the experiences that make your organization unique — build in Kinetic.
Play 1: SAP for core, Kinetic for everything else
Every organization has processes that are pure SAP — GL postings, MRP runs, standard procurement. Those stay in SAP. But the fringe processes, the ones unique to your industry, your compliance requirements, your organizational structure — those are the ones that create technical debt when built in ABAP. Move them to Kinetic and SAP stays clean.
Keep in SAP
Core ERP Functions
Financial postings, materials management, production planning, standard procurement, warehouse management — anywhere SAP’s standard functionality covers the need without modification.
Build in Kinetic
Business-Specific Processes
Custom approvals, org-specific workflows, compliance checklists, multi-system onboarding, vendor portals, exception handling — anything that would require custom ABAP or Z-transactions.
Play 2: Kinetic as the experience layer across SAP instances
Many organizations run multiple SAP instances — separate environments for different business units, regions, or legacy acquisitions. Kinetic acts as the unified front-end that users interact with, orchestrating workflows that read from and write into multiple SAP systems simultaneously. Users see one experience. Kinetic handles the routing.
Architecture — Unified Experience Layer
Users
End Users · Managers · Approvers · External Partners
Experience & Orchestration
Kinetic Data — Unified UX, Workflows, Business Rules, Approvals
Integration
APIs · OData · RFCs · IDocs · MuleSoft · Middleware
ERP Systems
This is especially powerful during migrations. Organizations can run ECC and S/4HANA in parallel behind Kinetic — users keep working in the same Kinetic interface while the backend transitions from one system to another. No big-bang cutover. No user retraining.
Both Plays Work Together
Start with Play 1 during your S/4HANA migration — identify custom processes and rebuild them in Kinetic instead of re-customizing S/4HANA. Use Play 2 to run both systems in parallel during the transition, giving users a single front door while the backend migrates underneath them.
Nine processes that belong in Kinetic, not SAP
These are the processes that organizations commonly build inside SAP with custom ABAP — creating the technical debt that makes upgrades painful. Every one of them is a natural fit for Kinetic, where they can be built faster, changed easier, and never block an upgrade again.
Procurement Approvals
Conditional routing based on cost center, amount thresholds, and org hierarchy. In Kinetic it’s a configurable workflow that writes approved POs back via standard BAPI.
Employee Self-Service
Leave requests, address changes, benefits enrollment, pay stubs. Kinetic delivers a modern branded experience backed by standard SAP HCM APIs.
New Hire Onboarding
A single workflow spanning SAP HCM, Active Directory, facilities, IT equipment, and training. SAP alone can’t orchestrate all these systems.
Invoice & Payment Exceptions
Three-way match failures, blocked invoices, payment run exceptions. Custom ABAP exception handlers are among the hardest code to migrate.
Vendor & Partner Portals
PO acknowledgment, ASN submission, invoice upload — all without giving third parties SAP access. Kinetic provides the portal; SAP provides the data via OData.
Capital Project Requests
Business case submission, multi-department approval, budget check against SAP CO, asset creation in SAP AM — one orchestrated process instead of custom PS/IM workflows.
Audit & Compliance Checklists
SOX controls, segregation of duties reviews, periodic access certifications. Forms and approval chains that change frequently — trivial in Kinetic, a nightmare in ABAP.
Plant Maintenance
Mobile-friendly work orders, inspection checklists, parts requests, photo capture — feeding results back into SAP PM through standard interfaces.
Custom Data Entry & Reporting
Replace Z-transactions and custom ALV reports with dynamic forms that validate against SAP master data via OData — without a single line of ABAP.
The Rule of Thumb
If a process touches SAP data but exists because the standard SAP transaction didn’t fit how your organization works — it belongs in Kinetic. The data stays in SAP. The experience, logic, and orchestration move out. SAP becomes a system of record, not a system of engagement.
What changes: before and after
| Dimension | Customized SAP (Today) | SAP + Kinetic (Target) |
|---|---|---|
| Custom Code | Millions of lines of ABAP embedded in SAP core; blocks upgrades | Zero custom ABAP — business logic lives in Kinetic workflows |
| Upgrade Path | 2–4 year projects; extensive regression testing; high go-live risk | Routine upgrades — Kinetic layer is independent of SAP version |
| Process Changes | Change requests queue behind ABAP dev; weeks-to-months cycle | Process owners adjust workflows with low-code tools; days-to-hours |
| User Experience | Fiori standard or custom SAP GUI; limited UX control | Fully custom, branded UX — tailored to how users actually work |
| Talent | Specialized ABAP developers; shrinking, expensive talent pool | Low-code configuration — broader team can maintain processes |
| Cross-System | Custom middleware and point-to-point integrations | Kinetic orchestrates across systems — SAP is one endpoint of many |
| Risk | Each customization increases future migration risk | SAP stays clean — no compound risk from customization drift |
The bottom line
The Clean Core, Made Practical
SAP’s “clean core” vision is the right destination. Kinetic is how you actually get there — without sacrificing the custom processes your organization depends on.
Keep SAP standard. Keep your processes yours. Let Kinetic be the customization layer SAP never gave you.