ECC 2027: The Planning Framework for Teams Who Haven't Started Yet

In March 2026 we published a survival guide for teams already in motion. This post is different. It is a planning framework for teams who have not started — the ones still debating RISE versus Private Edition, still treating ODP as a separate IT ticket, or still waiting for a clearer signal from SAP.

The signal already arrived. ECC maintenance ends in December 2027. ODP-RFC was technically blocked on June 9, 2026, with the temporary fallback expiring in December 2026. You do not get two independent programmes. You get one compound transformation with shared dependencies, shared risk, and a shared board narrative.

This framework has five phases. Skip none of them. Compress them if you must. Do not invent a sixth phase called "wait for more clarity."

---

Phase 0 — Admit the Dual Crisis (Week 1)

Most late programmes fail before they start because they frame the problem incorrectly.

Wrong frame: "We need an S/4HANA migration project."

Right frame: "We need a governed dual-crisis programme: migrate the ERP platform and replace non-compliant extraction pipelines before two hard deadlines collide."

Why this matters:

• Your analytics, reporting, and AI training pipelines may still depend on ODP-RFC. Those pipelines break (or are already on borrowed time) independently of when S/4HANA goes live.
• Your S/4HANA target architecture determines which extraction methods remain viable. Choosing RISE without answering "how does data leave SAP?" creates a second crisis mid-migration.
• Board risk is compound risk. A migration that lands on time with broken data pipelines is not a successful migration.

Week 1 deliverable: A one-page dual-crisis charter signed by the CIO (or equivalent) that names both deadlines, names a single programme owner, and states that extraction compliance is in scope for every migration decision.

Immediate technical action: Run SAP Note 3439624. You cannot plan extraction remediation without knowing which ODP-RFC subscribers are still active.

---

Phase 1 — Choose the Path (Weeks 2–4)

You have three commercially real paths. Everything else is delay dressed as analysis.

Path A — RISE with SAP

SAP runs the technical stack on a designated hyperscaler. You buy a subscription (ACV/TCV). BASIS load drops. Upgrade cadence is SAP-managed. Clean Core pressure increases. Hyperscaler choice and data-access patterns are more constrained than a customer-managed estate.

Choose RISE when: you lack BASIS capacity, want SAP to own infrastructure SLA, and can accept Clean Core constraints and SAP-controlled extraction pathways (including Business Data Cloud / OData patterns).

Path B — S/4HANA Private Edition (customer-managed IaaS)

You (or your SI) own the Azure/AWS landing zone, HA/DR design, and ops model. You keep more control over ABAP customisation, region/SKU selection, and data extraction architecture — including ABAP Push to Azure Data Lake, Event Hubs, or Fabric.

Choose Private Edition when: data sovereignty, ABAP flexibility, long-term cost transparency, or ODP-compliant extraction control matter more than outsourcing BASIS.

Path C — Stay on ECC past 2027 (extended maintenance)

This is a decision, not a non-decision. Extended maintenance means surcharges, declining patch coverage, and zero functional updates. It can be rational for a defined period — for example, to finish extraction remediation and land-zone work before a delayed S/4 cutover — but only with an explicit exit date and funded exit plan.

Choose extended maintenance only when: a board-approved exit date exists, ODP remediation is funded in parallel, and extended maintenance is framed as a bridge — never as a strategy.

Use the RISE vs Private Edition comparison on pricing.skynome.com for indicative TCO. It will not replace a negotiated SAP quote — it will stop you arguing from vibes.

Phase 1 deliverable: A path decision memo with a named recommendation, rejected alternatives, and the extraction architecture implied by the choice.

---

Phase 2 — Scope the Workstreams (Weeks 4–6)

A late programme that tries to "do everything" will finish nothing. Scope four workstreams with hard boundaries.

Workstream 1 — Platform & landing zone

Target landscape (RISE or Private Edition), network, identity, HA/DR, environments (DEV/QAS/PRD), cutover approach (brownfield, greenfield, or selective data transition).

Workstream 2 — Custom code & Clean Core

Custom Code Migration analysis, remediation backlog, Clean Core policy for what stays, what is retired, and what moves to BTP or side-by-side extensions.

Workstream 3 — Integration continuity

CPI/BTP flows, third-party interfaces, IDoc partners, RFC destinations. Map every interface that will break when the ECC system is replaced or when ODP subscribers are removed.

Workstream 4 — Data extraction compliance (the dual-crisis workstream)

Classify every pipeline from Note 3439624 output:

• Replace now (pre-Dec 2026 fallback): production-critical ODP-RFC consumers still on fallback
• Replace with S/4 target in mind: pipelines that should land on OData, ABAP Push, or certified partners on the target architecture
• Decommission: inactive subscribers nobody noticed were dead

Do not let Workstream 4 become a "phase 2 after go-live" item. That is how you go live with a governed ERP and a broken data estate.

Phase 2 deliverable: A dual-crisis backlog with owners, dependencies, and a single critical path that includes at least one extraction milestone before December 2026.

---

Phase 3 — Build the Business Case Boards Will Fund (Weeks 6–8)

Late programmes often fail at funding because the business case is written as a technology upgrade. Rewrite it as risk removal plus option value.

Cost of inaction (must quantify):

• Extended maintenance surcharge trajectory after Dec 2027
• Security and compliance exposure on unsupported Enhancement Packages (if already out of mainstream)
• Broken or fallback-dependent analytics pipelines after December 2026
• Opportunity cost of delayed Clean Core / AI readiness (Joule, Copilot, Azure OpenAI) on an ungoverned estate

Cost of action (must be honest):

• Licence / subscription (RISE ACV or S/4 + IaaS)
• Implementation and SI fees
• Custom code remediation
• Extraction rebuild (often under-budgeted)
• Dual-run and hypercare

Value of governance (must be explicit):

• Fewer rework cycles from undocumented decisions
• Shared cutover between ERP and data pipelines
• Measurable readiness via Governance Readiness Score™ across migration, extraction, Clean Core, DR, and AI domains

Phase 3 deliverable: A board pack with three slides that matter: dual-crisis risk, path recommendation with TCO range, and a 90-day funded start (not a 24-month fantasy Gantt).

---

Phase 4 — Govern Execution Like a Programme, Not a Project (Ongoing)

If you are late, you cannot afford unmanaged scope. Install governance before the first SI day-rate invoice.

Minimum operating rhythm:

• Weekly critical-path review (platform + extraction, same meeting)
• Bi-weekly architecture decision records (ADRs) — especially for extraction method per pipeline
• Monthly GRS or domain score refresh on Migration Readiness and Data Extraction Compliance
• Hard freeze rules for new ECC customisation that does not have an S/4 remediation path

Cutover rule for dual-crisis programmes:

You do not declare go-live success when ECC is switched off. You declare it when:

1. S/4 (or RISE) production is stable against agreed SLOs, and
2. Tier-1 analytics / data pipelines are running on compliant methods, and
3. ODP-RFC subscribers for production workloads are decommissioned or documented as residual risk with an exit date

Anything less is a partial go-live with a deferred outage.

---

The 90-Day Start Plan (For Teams Starting This Month)

If you are reading this in August–September 2026 and truly have not started, do this:

| Days | Action | |---|---| | 1–7 | Dual-crisis charter + Note 3439624 run + named programme owner | | 8–21 | Path decision workshop (RISE vs Private Edition vs bridge) with extraction architecture attached | | 22–45 | Workstream scoping + SI shortlist + landing zone / RISE discovery | | 46–60 | Board business case + funded 90-day mobilisation budget | | 61–90 | Kick off Workstream 4 Tier-1 ODP replacements in parallel with sandbox / discovery for S/4 |

You will not finish S/4HANA in 90 days. You can finish the decisions that determine whether the next sixteen months produce a migration — or produce another year of slides.

---

Where Skynome Fits

Skynome does not replace your SI for a full S/4 build. We govern the decisions that make a late programme survivable:

• Dual-Crisis Assessment — Migration Readiness + Data Extraction Compliance scored together under GRS
• ODP Compliance Review — Note 3439624 interpretation, Tier-1 pipeline replacement design (ADF options, OData, ABAP Push)
• RISE vs Private Edition advisory — path decision with indicative TCO and extraction implications
• GRS Live Monitoring — continuous scoring after the initial assessment so posture does not degrade mid-programme

Request a Dual-Crisis Assessment or start with the Governance Readiness Score.

December 2027 does not move. December 2026 (ODP fallback) does not move either. The only variable left is whether your planning framework treats them as one programme.

---

This framework reflects Skynome's advisory practice as of August 2026. ECC mainstream maintenance end dates are set by SAP and may be subject to SAP's official communications. Extended maintenance terms vary by contract. Path selection and TCO figures are indicative — negotiate RISE and licence pricing directly with SAP. Skynome is independent of SAP and Microsoft.