{"id":112870,"date":"2026-06-01T15:30:49","date_gmt":"2026-06-01T10:00:49","guid":{"rendered":"https:\/\/www.guvi.in\/blog\/?p=112870"},"modified":"2026-06-01T15:30:50","modified_gmt":"2026-06-01T10:00:50","slug":"how-to-build-an-sap-roadmap","status":"publish","type":"post","link":"https:\/\/www.guvi.in\/blog\/how-to-build-an-sap-roadmap\/","title":{"rendered":"How to Build an SAP Roadmap in 2026\u00a0"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><strong>What Is an SAP Roadmap?<\/strong><\/h2>\n\n\n\n<p>An <strong>SAP Roadmap<\/strong> is a structured, long-term strategic plan that outlines how an organization will adopt, upgrade, migrate, or expand its SAP ecosystem over time.<\/p>\n\n\n\n<p>It answers three critical questions:<\/p>\n\n\n\n<ul>\n<li><strong>Where are you now?<\/strong> (Current SAP landscape assessment)<\/li>\n\n\n\n<li><strong>Where do you want to go?<\/strong> (Target architecture and business goals)<\/li>\n\n\n\n<li><strong>How will you get there?<\/strong> (Phases, timelines, resources, and milestones)<\/li>\n<\/ul>\n\n\n\n<p>An SAP Roadmap is not a single document; it is a living plan that evolves with your business, SAP product releases, and regulatory requirements.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>TL;DR:<\/strong>&nbsp;<\/h2>\n\n\n\n<p>An SAP Roadmap is a step-by-step strategic plan that helps companies migrate from legacy SAP systems, such as ECC, to modern platforms like SAP S\/4HANA. In 2026, roadmap planning is critical because SAP ECC support is ending by 2030, pushing organizations to modernize faster.<\/p>\n\n\n\n<p>A complete SAP Roadmap usually follows 7 phases:<\/p>\n\n\n\n<ol>\n<li><strong>Discovery &amp; Assessment: <\/strong>&nbsp;Audit current SAP systems, integrations, custom code, and data quality<\/li>\n\n\n\n<li><strong>Strategy &amp; Vision: Choose<\/strong> Greenfield, Brownfield, or Bluefield migration approach<\/li>\n\n\n\n<li><strong>Architecture &amp; Design: <\/strong>Define target cloud\/on-prem architecture, integrations, and security<\/li>\n\n\n\n<li><strong>Business Case &amp; Funding:<\/strong> Build ROI, TCO, and transformation budget approval<\/li>\n\n\n\n<li><strong>Implementation Planning:<\/strong> Select partners, governance, testing, and cutover strategy<\/li>\n\n\n\n<li><strong>Build &amp; Testing: <\/strong>Configure S\/4HANA, migrate data, run UAT, and train users<\/li>\n\n\n\n<li><strong>Go-Live &amp; Hypercare: <\/strong>Launch production system, stabilize operations, and transition to BAU support<\/li>\n<\/ol>\n\n\n\n<p>Key 2026 SAP trends include:<\/p>\n\n\n\n<ul>\n<li>AI-powered automation through <strong>Joule<\/strong><\/li>\n\n\n\n<li>Stronger <strong>Clean Core<\/strong> requirements<\/li>\n\n\n\n<li>Heavy adoption of <strong>RISE with SAP<\/strong><\/li>\n\n\n\n<li>Expansion of <strong>SAP BTP<\/strong> for integrations and extensions<\/li>\n\n\n\n<li>Industry-specific cloud solutions<\/li>\n<\/ul>\n\n\n\n<p>Companies with a clear SAP Roadmap reduce migration risk, control costs, improve adoption, and accelerate digital transformation success.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why an SAP Roadmap Matters in 2026<\/strong><\/h2>\n\n\n\n<p>SAP has officially set <a href=\"https:\/\/support.sap.com\/en\/offerings-programs\/strategy.html\" target=\"_blank\" rel=\"noreferrer noopener nofollow\"><strong>2027<\/strong><\/a> as the end-of-mainstream maintenance deadline for SAP ECC, now extended to <strong>2030 with extended support<\/strong>. This makes roadmap planning more urgent than ever for thousands of companies still running legacy SAP systems.<\/p>\n\n\n\n<p>Without a roadmap, organizations risk:<\/p>\n\n\n\n<ul>\n<li><strong>Unplanned downtime<\/strong> during rushed migrations<\/li>\n\n\n\n<li><strong>Cost overruns<\/strong> from poor scoping<\/li>\n\n\n\n<li><strong>Failed go-lives<\/strong> due to insufficient change management<\/li>\n\n\n\n<li><strong>Compliance gaps<\/strong> if regulatory-mandated upgrades are skipped<\/li>\n\n\n\n<li><strong>Loss of competitive advantage<\/strong> from delayed digital transformation<\/li>\n<\/ul>\n\n\n\n<p>A well-built SAP Roadmap is your single most important tool for de-risking enterprise transformation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Real-World SAP Roadmap Example<\/strong><\/h2>\n\n\n\n<p><strong>Scenario:<\/strong> Mid-market manufacturing company, 800 employees, running SAP ECC 6.0 since 2009.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The Challenge<\/strong><\/h3>\n\n\n\n<p>A European industrial equipment manufacturer with operations in 4 countries had been running SAP ECC with heavy customization, over 2,400 custom ABAP objects. With SAP&#8217;s 2030 deadline approaching and a new CFO demanding better financial reporting, the board mandated an S\/4HANA migration.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The Roadmap Decision<\/strong><\/h3>\n\n\n\n<p>After a 10-week Discovery phase, their SAP Readiness Check revealed that 38% of custom objects were either redundant or replaceable by standard S\/4HANA functionality.&nbsp;<\/p>\n\n\n\n<p>They chose a <strong>Selective Data Transition (Bluefield) approach<\/strong>, migrating open transactions and active master data, while leaving historical data in a decommissioned archive system.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The Phased Approach<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Wave<\/strong><\/td><td><strong>Scope<\/strong><\/td><td><strong>Timeline<\/strong><\/td><td><strong>Rationale<\/strong><\/td><\/tr><tr><td>Wave 1<\/td><td>Finance (FI\/CO) + Procurement (MM)<\/td><td>Months 1\u201314<\/td><td>Highest business priority, cleanest data<\/td><\/tr><tr><td>Wave 2<\/td><td>Finance (FI\/CO) + Procurement (MM)<\/td><td>Months 12\u201322<\/td><td>Complex; runs parallel to Wave 1 stabilization<\/td><\/tr><tr><td>Wave 3<\/td><td>Manufacturing (PP\/QM) + Plant Maintenance (PM)<\/td><td>Months 20\u201330<\/td><td>Most complex, highest customization<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The Outcomes<\/strong><\/h3>\n\n\n\n<ul>\n<li>Month-end financial close reduced from 8 days to 3 days<\/li>\n\n\n\n<li>Custom object count reduced from 2,400 to 610,&nbsp; a 75% reduction<\/li>\n\n\n\n<li>Total project cost came in at \u20ac4.2M,&nbsp; 8% under budget<\/li>\n\n\n\n<li>Go-live achieved with zero critical incidents during hypercare<\/li>\n<\/ul>\n\n\n\n<p><strong>The single biggest lesson:<\/strong> The company invested \u20ac180,000 in data cleansing before the project started. Their project manager credited this decision with saving at least 3 months of schedule slippage and \u20ac400,000 in rework costs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The 7 Core Phases of an SAP Roadmap<\/strong><\/h2>\n\n\n\n<p><strong>Direct Answer:<\/strong> An SAP Roadmap typically follows 7 phases:&nbsp;<\/p>\n\n\n\n<p>(1) Discovery &amp; Assessment,<\/p>\n\n\n\n<p>&nbsp;(2) Strategy &amp; Vision,&nbsp;<\/p>\n\n\n\n<p>(3) Architecture &amp; Design,&nbsp;<\/p>\n\n\n\n<p>(4) Business Case &amp; Funding,<\/p>\n\n\n\n<p>&nbsp;(5) Implementation Planning,&nbsp;<\/p>\n\n\n\n<p>(6) Build &amp; Test, and<\/p>\n\n\n\n<p>&nbsp;(7) Go-Live &amp; Stabilization. Each phase has defined outputs, owners, and entry\/exit criteria.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 1: Discovery &amp; Current State Assessment<\/strong><\/h3>\n\n\n\n<p>Before planning where you&#8217;re going, you must deeply understand where you are.<\/p>\n\n\n\n<p><strong>What happens in this phase:<\/strong><\/p>\n\n\n\n<ul>\n<li>Inventory your current SAP systems (ECC, BW, CRM, SRM, etc.)<\/li>\n\n\n\n<li>Identify customizations, interfaces, and third-party integrations<\/li>\n\n\n\n<li>Assess technical debt and technical risks<\/li>\n\n\n\n<li>Map current business processes to SAP modules<\/li>\n\n\n\n<li>Evaluate data quality and master data governance<\/li>\n\n\n\n<li>Identify regulatory and compliance obligations<\/li>\n<\/ul>\n\n\n\n<p><strong>Key outputs:<\/strong><\/p>\n\n\n\n<ul>\n<li>Current landscape diagram<\/li>\n\n\n\n<li>Custom code volume analysis<\/li>\n\n\n\n<li>Interface inventory<\/li>\n\n\n\n<li>Data quality assessment report<\/li>\n<\/ul>\n\n\n\n<p><strong>Common mistake to avoid:<\/strong> Skipping or rushing discovery is the #1 cause of SAP project failures. Budget adequate time,&nbsp; typically 6\u201312 weeks for mid-size enterprises.<\/p>\n\n\n\n<p><strong>Phase 1 Readiness Checklist:<\/strong><\/p>\n\n\n\n<ul>\n<li>&nbsp;SAP Readiness Check completed and results reviewed<\/li>\n\n\n\n<li>Custom code volume and complexity scored<\/li>\n\n\n\n<li>&nbsp;Interface and integration inventory documented<\/li>\n\n\n\n<li>Current system landscape diagram created<\/li>\n\n\n\n<li>Key stakeholders identified and interviewed<\/li>\n\n\n\n<li>Data quality baseline assessment completed<\/li>\n\n\n\n<li>Regulatory and compliance obligations catalogued<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 2: Strategy &amp; Future Vision<\/strong><\/h3>\n\n\n\n<p>This is where business and IT leadership align on the &#8220;North Star&#8221; of the transformation.<\/p>\n\n\n\n<p><strong>What happens in this phase:<\/strong><\/p>\n\n\n\n<ul>\n<li>Define target architecture (e.g., SAP S\/4HANA Private Cloud, Public Cloud, or Hybrid)<\/li>\n\n\n\n<li>Choose deployment model: Greenfield, Brownfield, or Selective Data Transition (Bluefield)<\/li>\n\n\n\n<li>Align SAP strategy with enterprise digital transformation goals<\/li>\n\n\n\n<li>Benchmark against industry peers and best practices<\/li>\n\n\n\n<li>Engage SAP account team for product roadmap alignment<\/li>\n<\/ul>\n\n\n\n<p><strong>Greenfield vs. Brownfield vs. Bluefield:&nbsp; What&#8217;s the Difference?<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Approach<\/strong><\/td><td><strong>What It Means<\/strong><\/td><td><strong>Best For<\/strong><\/td><\/tr><tr><td><strong>Greenfield<\/strong><\/td><td>Start fresh, reimplementing SAP from scratch on S\/4HANA<\/td><td>Companies wanting a clean slate and a full process redesign<\/td><\/tr><tr><td><strong>Brownfield<\/strong><\/td><td>In-place conversion, migrate existing ECC to S\/4HANA<\/td><td>Companies want speed and continuity<\/td><\/tr><tr><td><strong>Bluefield \/ Selective Data Transition<\/strong><\/td><td>Hybrid,&nbsp; selectively migrate data and processes<\/td><td>Companies with complex, heterogeneous landscapes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Phase 2 Readiness Checklist:<\/strong><\/p>\n\n\n\n<ul>\n<li>&nbsp;Deployment model decided: Greenfield \/ Brownfield \/ Bluefield<\/li>\n\n\n\n<li><a href=\"https:\/\/www.guvi.in\/blog\/real-world-cloud-computing-applications\/\" target=\"_blank\" rel=\"noreferrer noopener\">Cloud strategy<\/a> defined: RISE \/ Private Cloud \/ On-Premise<\/li>\n\n\n\n<li>Target system landscape approved by IT leadership<\/li>\n\n\n\n<li>SAP product roadmap reviewed with SAP account team<\/li>\n\n\n\n<li>&nbsp;Executive sponsor confirmed and committed<\/li>\n\n\n\n<li>&nbsp;Transformation vision statement approved<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 3: Architecture &amp; Solution Design<\/strong><\/h3>\n\n\n\n<p>The technical blueprint of your SAP future.<\/p>\n\n\n\n<p><strong>What happens in this phase:<\/strong><\/p>\n\n\n\n<ul>\n<li>Design the target system landscape (SID strategy, clients, transport routes)<\/li>\n\n\n\n<li>Define integration architecture (SAP BTP, middleware, APIs)<\/li>\n\n\n\n<li>Plan SAP RISE adoption if applicable<\/li>\n\n\n\n<li>Design security, authorization, and access control frameworks<\/li>\n\n\n\n<li>Define reporting and analytics architecture (SAP Analytics <a href=\"https:\/\/www.guvi.in\/blog\/advantages-of-computer-network\/\" target=\"_blank\" rel=\"noreferrer noopener\">Cloud,<\/a> BW\/4HANA)<\/li>\n\n\n\n<li>Address extensibility strategy (side-by-side vs. in-app extensions)<\/li>\n<\/ul>\n\n\n\n<p><strong>Key tool in this phase:<\/strong> SAP&#8217;s own <a href=\"https:\/\/support.sap.com\/en\/alm\/sap-cloud-alm\/transformation\/btc.html\" target=\"_blank\" rel=\"noreferrer noopener nofollow\"><strong>Business Transformation Center (BTC)<\/strong><\/a> and <strong>Readiness Check<\/strong> tools help assess custom code compatibility and simplification item relevance before committing to a design.<\/p>\n\n\n\n<p><strong>Phase 3 Readiness Checklist:<\/strong><\/p>\n\n\n\n<ul>\n<li>&nbsp;Target architecture document signed off<\/li>\n\n\n\n<li>&nbsp;Integration architecture designed and approved<\/li>\n\n\n\n<li>&nbsp;Security and authorization concept drafted<\/li>\n\n\n\n<li>&nbsp;Clean core extensibility strategy defined<\/li>\n\n\n\n<li>&nbsp;Reporting and analytics architecture confirmed<\/li>\n\n\n\n<li>&nbsp;SAP BTP integration points identified<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 4: Business Case &amp; Funding Approval<\/strong><\/h3>\n\n\n\n<p>An SAP transformation is a multi-million-dollar investment. You need a bulletproof business case.<\/p>\n\n\n\n<p><strong>What your business case must include:<\/strong><\/p>\n\n\n\n<ul>\n<li><strong>Total Cost of Ownership (TCO):<\/strong> License, implementation, infrastructure, training, support<\/li>\n\n\n\n<li><strong>Return on Investment (ROI):<\/strong> Process efficiency gains, headcount optimization, reporting speed<\/li>\n\n\n\n<li><strong>Risk Cost of Inaction:<\/strong> Cost of staying on unsupported ECC systems<\/li>\n\n\n\n<li><strong>Phased investment model:<\/strong> Avoiding one-time capital shock<\/li>\n\n\n\n<li><strong>Benchmark data:<\/strong> Use SAP&#8217;s Value Lifecycle Manager (VLM) or third-party benchmarks<\/li>\n<\/ul>\n\n\n\n<p><strong>Stat to know:<\/strong> According to SAP benchmarks, organizations that fully migrate to SAP S\/4HANA report an average 17% reduction in operational costs and a 2x improvement in finance close cycles.<\/p>\n\n\n\n<p><strong>Phase 4 Readiness Checklist:<\/strong><\/p>\n\n\n\n<ul>\n<li>&nbsp;TCO model completed for 5-year horizon<\/li>\n\n\n\n<li>&nbsp;ROI calculation reviewed by Finance<\/li>\n\n\n\n<li>The risk cost of inaction is documented<\/li>\n\n\n\n<li>Funding request submitted and approved<\/li>\n\n\n\n<li>&nbsp;Implementation partner shortlist created<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 5: Implementation Planning<\/strong><\/h3>\n\n\n\n<p>This is where your roadmap becomes a project plan.<\/p>\n\n\n\n<p><strong>Key planning decisions:<\/strong><\/p>\n\n\n\n<ul>\n<li>Choose your system integrator (SI) or implementation partner<\/li>\n\n\n\n<li>Define project governance structure (Steering Committee, Project Board, Workstreams)<\/li>\n\n\n\n<li>Build your project charter and RACI matrix<\/li>\n\n\n\n<li>Define your sprint cadence (for agile delivery) or phase gates (for waterfall)<\/li>\n\n\n\n<li>Plan your testing strategy: Unit \u2192 Integration \u2192 UAT \u2192 Regression \u2192 Performance<\/li>\n\n\n\n<li>Define your cutover strategy and data migration approach<\/li>\n\n\n\n<li>Build a change management and training plan<\/li>\n<\/ul>\n\n\n\n<p><strong>SAP Activate Methodology:<\/strong> SAP recommends using its <strong>SAP Activate<\/strong> methodology for all S\/4HANA implementations,&nbsp; a prescriptive, agile-aligned framework consisting of six phases: Discover \u2192 Prepare \u2192 Explore \u2192 Realize \u2192 Deploy \u2192 Run.<\/p>\n\n\n\n<p><strong>Phase 5 Readiness Checklist:<\/strong><\/p>\n\n\n\n<ul>\n<li>&nbsp;System integrator selected and contracted<\/li>\n\n\n\n<li>&nbsp;Project governance structure established<\/li>\n\n\n\n<li>&nbsp;RACI matrix completed and communicated<\/li>\n\n\n\n<li>&nbsp;Project charter signed by steering committee<\/li>\n\n\n\n<li>&nbsp;Testing strategy and environments planned<\/li>\n\n\n\n<li>&nbsp;Change management and training plan drafted<\/li>\n\n\n\n<li>&nbsp;Cutover strategy and approach documented<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 6: Build, Configure &amp; Test<\/strong><\/h3>\n\n\n\n<p>The longest phase, where design becomes reality.<\/p>\n\n\n\n<p><strong>What happens in this phase:<\/strong><\/p>\n\n\n\n<ul>\n<li>Configure SAP S\/4HANA using Best Practice content or custom configuration<\/li>\n\n\n\n<li>Develop custom code, reports, forms, and enhancements<\/li>\n\n\n\n<li>Build and test integrations with third-party systems<\/li>\n\n\n\n<li>Execute data migration dry runs (typically 3+ rounds)<\/li>\n\n\n\n<li>Conduct user acceptance testing (UAT) with business key users<\/li>\n\n\n\n<li>Conduct performance and stress testing<\/li>\n\n\n\n<li>Train end users and super users<\/li>\n<\/ul>\n\n\n\n<p><strong>Critical success factor:<\/strong> Establish a <strong>Cutover Command Center<\/strong> before go-live. Every hour of unplanned downtime during cutover can cost enterprise organizations $50,000\u2013$500,000+.<\/p>\n\n\n\n<p><strong>Phase 6 Readiness Checklist:<\/strong><\/p>\n\n\n\n<ul>\n<li>Configuration complete for all in-scope modules<\/li>\n\n\n\n<li>&nbsp;Custom development complete and unit tested<\/li>\n\n\n\n<li>Integration testing completed,&nbsp; all interfaces passing<\/li>\n\n\n\n<li>&nbsp;Data migration dress rehearsal 1 and 2 complete<\/li>\n\n\n\n<li>&nbsp;UAT signed off by business key users<\/li>\n\n\n\n<li>&nbsp;Performance testing completed under load<\/li>\n\n\n\n<li>&nbsp;End-user training delivered to all user groups<\/li>\n\n\n\n<li>&nbsp;Cutover dress rehearsal completed<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 7: Go-Live, Stabilization &amp; Hypercare<\/strong><\/h3>\n\n\n\n<p>Go-live is not the finish line,&nbsp; it&#8217;s the starting line for adoption.<\/p>\n\n\n\n<p><strong>What a successful go-live looks like:<\/strong><\/p>\n\n\n\n<ul>\n<li>Phased or Big Bang cutover execution<\/li>\n\n\n\n<li>Hypercare period (typically 4\u20138 weeks post go-live)<\/li>\n\n\n\n<li>Dedicated support team available 24\/7 in hypercare<\/li>\n\n\n\n<li>KPI tracking against baseline measurements<\/li>\n\n\n\n<li>Rapid incident management and resolution<\/li>\n\n\n\n<li>Transition to BAU (Business-as-Usual) SAP support team<\/li>\n<\/ul>\n\n\n\n<p><strong>Phase 7 Readiness Checklist:<\/strong><\/p>\n\n\n\n<ul>\n<li>Go \/ No-Go criteria reviewed and approved by the steering committee<\/li>\n\n\n\n<li>&nbsp;Hypercare team rostered and on call<\/li>\n\n\n\n<li>&nbsp;Monitoring dashboards and alerting are configured<\/li>\n\n\n\n<li>&nbsp;Rollback decision criteria documented<\/li>\n\n\n\n<li>Post-go-live KPIs baselined and tracked<\/li>\n\n\n\n<li>Lessons learned session scheduled<\/li>\n<\/ul>\n\n\n\n<p><strong>Ready to Move from ECC to S\/4HANA?<\/strong> Don&#8217;t let the 2030 deadline catch you off guard. Learn how to plan, build, and execute a successful SAP S\/4HANA implementation,\u00a0 from discovery to go-live. <strong>\u00a0Enroll in HCL GUVI<\/strong><a href=\"https:\/\/www.guvi.in\/courses\/business-and-management\/sap-s4-hana\/?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=how-to-build-an-sap-roadmap\" target=\"_blank\" data-type=\"link\" data-id=\"https:\/\/www.guvi.in\/courses\/business-and-management\/sap-s4-hana\/?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=how-to-build-an-sap-roadmap\" rel=\"noreferrer noopener\"><strong> SAP S\/4HANA Course<\/strong><em>.<\/em>\u00a0<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>SAP S\/4HANA Roadmap: What&#8217;s New in 2026?<\/strong><\/h2>\n\n\n\n<p><strong>Direct Answer:<\/strong> SAP S\/4HANA&#8217;s 2026 roadmap focuses on five themes: embedded AI via Joule, expanded SAP BTP integration, RISE with SAP cloud adoption acceleration, industry cloud solutions by sector, and enhanced clean core extensibility standards.<\/p>\n\n\n\n<p>Key SAP product roadmap highlights for 2026:<\/p>\n\n\n\n<ul>\n<li><strong>Joule AI Copilot:<\/strong> Embedded across Finance, HR, Procurement, and Supply Chain,<a href=\"https:\/\/www.sap.com\/assetdetail\/2024\/05\/946160f3-be7e-0010-bca6-c68f7e60039b.html\" target=\"_blank\" rel=\"noreferrer noopener nofollow\"> automating repetitive tasks <\/a>and surfacing insights in natural language<\/li>\n\n\n\n<li><strong>Clean Core Strategy:<\/strong> SAP is enforcing stricter clean core principles, pushing customizations to BTP side-by-side extensions<\/li>\n\n\n\n<li><strong>SAP BTP Expansion:<\/strong> <a href=\"https:\/\/help.sap.com\/docs\/btp\/sap-business-technology-platform\/btp-extensions\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">SAP Business Technology Platform <\/a>is becoming the central integration, automation, and extensibility hub for all S\/4HANA customers<\/li>\n\n\n\n<li><strong>Industry Cloud:<\/strong> Pre-built, <a href=\"https:\/\/www.guvi.in\/blog\/types-of-computer-network-architecture\/\" target=\"_blank\" rel=\"noreferrer noopener\">cloud-native industry<\/a> solutions for Retail, Manufacturing, Utilities, Healthcare, and more,&nbsp; significantly reducing implementation timelines<\/li>\n\n\n\n<li><strong>RISE with SAP:<\/strong> The <a href=\"https:\/\/www.sap.com\/india\/products\/erp\/rise.html?pttid=7756&amp;campaigncode=crm-ya22-int-1517075&amp;source=ppc-in-googleads-search-22588893049-179121616959-clouderpgrow_s4s-x-x-x&amp;gclsrc=aw.ds&amp;gad_source=1&amp;gad_campaignid=22588893049&amp;gbraid=0AAAAA_r6tp3mlRLWPS_yNbX_ZK_Kw1XgH&amp;gclid=CjwKCAjwrNrQBhBjEiwAoR4VO9Hfn4LyXLLHf80aDUnPGM4RlYbidcat_MTNC_MYbdU1YothhnMohRoCUUEQAvD_BwE\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">bundled cloud ERP <\/a>migration program continues to be SAP&#8217;s preferred path for ECC customers moving to S\/4HANA Cloud<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>SAP Activate Methodology: Phase-by-Phase Breakdown<\/strong><\/h2>\n\n\n\n<p>SAP Activate is SAP&#8217;s official, agile-aligned implementation methodology for S\/4HANA. Understanding it is essential for anyone building or executing an SAP Roadmap.<\/p>\n\n\n\n<p><strong>Direct Answer:<\/strong> SAP Activate consists of six phases: Discover, Prepare, Explore, Realize, Deploy, and Run. Each phase has defined inputs, outputs, and quality gate criteria. It replaces the older ASAP methodology and is optimized for cloud and agile delivery.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 1<\/strong><strong>: <\/strong><strong>&nbsp;Discover<\/strong><\/h3>\n\n\n\n<p><strong>Goal:<\/strong> Understand the SAP solution, validate the business case, and align stakeholders.<\/p>\n\n\n\n<ul>\n<li>Access SAP Best Practice content in the SAP Activate Roadmap Viewer<\/li>\n\n\n\n<li>Run SAP Readiness Check to identify custom code and simplification impacts<\/li>\n\n\n\n<li>Complete a fit-to-standard analysis using SAP Best Practice scope items<\/li>\n\n\n\n<li>Validate technical and functional feasibility<\/li>\n<\/ul>\n\n\n\n<p><strong>Key output:<\/strong> Approved project charter and scope statement<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 2<\/strong><strong>: <\/strong><strong>&nbsp;Prepare<\/strong><\/h3>\n\n\n\n<p><strong>Goal:<\/strong> Set up the project, team, and governance structures.<\/p>\n\n\n\n<ul>\n<li>Establish project governance (Steering Committee, workstream leads, RACI)<\/li>\n\n\n\n<li>Set up system environments (Development, Quality, Production)<\/li>\n\n\n\n<li>Onboard the implementation team and begin change management<\/li>\n<\/ul>\n\n\n\n<p><strong>Key output:<\/strong> Project infrastructure ready; kickoff complete<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 3<\/strong><strong>: <\/strong><strong>&nbsp;Explore<\/strong><\/h3>\n\n\n\n<p><strong>Goal:<\/strong> Validate the solution design using fit-to-standard workshops.<\/p>\n\n\n\n<ul>\n<li>Run fit-to-standard workshops with business process owners for every in-scope module<\/li>\n\n\n\n<li>Document configuration decisions and delta design requirements<\/li>\n\n\n\n<li>Identify and scope custom development needs<\/li>\n\n\n\n<li>Lock scope,&nbsp; this is your scope freeze gate<\/li>\n<\/ul>\n\n\n\n<p><strong>Key output:<\/strong> Confirmed solution design document; agreed scope baseline<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 4<\/strong><strong>: <\/strong><strong>&nbsp;Realize<\/strong><\/h3>\n\n\n\n<p><strong>Goal:<\/strong> Build, configure, and test the solution.<\/p>\n\n\n\n<ul>\n<li>Configure the system based on the Explore phase decisions<\/li>\n\n\n\n<li>Develop custom objects, reports, forms, and integrations<\/li>\n\n\n\n<li>Execute iterative sprint-based build cycles with continuous testing<\/li>\n\n\n\n<li>Execute data migration dry runs (minimum 3 rounds)<\/li>\n\n\n\n<li>Deliver end-user training<\/li>\n<\/ul>\n\n\n\n<p><strong>Key output:<\/strong> Tested, trained, and data-validated system ready for UAT<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 5<\/strong><strong>:<\/strong><strong> Deploy<\/strong><\/h3>\n\n\n\n<p><strong>Goal:<\/strong> Prepare for and execute go-live.<\/p>\n\n\n\n<ul>\n<li>Complete user acceptance testing (UAT) sign-off<\/li>\n\n\n\n<li>Execute final cutover rehearsal<\/li>\n\n\n\n<li>Complete a go \/ no-go assessment with the steering committee<\/li>\n\n\n\n<li>Execute production cutover; activate hypercare support<\/li>\n<\/ul>\n\n\n\n<p><strong>Key output:<\/strong> Live production system; hypercare period begins<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 6<\/strong><strong>:<\/strong><strong> Run<\/strong><\/h3>\n\n\n\n<p><strong>Goal:<\/strong> Stabilize operations and transition to business-as-usual.<\/p>\n\n\n\n<ul>\n<li>Resolve outstanding incidents from hypercare<\/li>\n\n\n\n<li>Transition to the BAU support team<\/li>\n\n\n\n<li>Conduct a lessons learned workshop<\/li>\n\n\n\n<li>Begin continuous improvement and optimization of the backlog<\/li>\n<\/ul>\n\n\n\n<p><strong>Key output:<\/strong> Stable BAU operations; roadmap updated for next phase<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Industry-Specific SAP Roadmap Considerations<\/strong><\/h2>\n\n\n\n<p>An SAP Roadmap is not one-size-fits-all. Strategic priorities, compliance requirements, and module footprints vary significantly by industry.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Manufacturing<\/strong><\/h3>\n\n\n\n<ul>\n<li><strong>Priority modules:<\/strong> PP (Production Planning), QM (Quality Management), PM (Plant Maintenance), EWM (Extended Warehouse Management)<\/li>\n\n\n\n<li><strong>Key consideration:<\/strong> IoT integration with SAP Digital Manufacturing is a growing roadmap priority for smart factory initiatives<\/li>\n\n\n\n<li><strong>Roadmap tip:<\/strong> Manufacturing companies tend to have the highest custom code volumes due to MES integrations. Budget significant time for custom code remediation<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Retail &amp; Consumer Goods<\/strong><\/h3>\n\n\n\n<ul>\n<li><strong>Priority modules:<\/strong> SD (Sales &amp; Distribution), MM (Materials Management), IBP (Integrated Business Planning), CAR (Customer Activity Repository)<\/li>\n\n\n\n<li><strong>Key consideration:<\/strong> Omnichannel and e-commerce integration with SAP Commerce Cloud is increasingly critical<\/li>\n\n\n\n<li><strong>Roadmap tip:<\/strong> Seasonal trading peaks create hard go-live blackout windows. Plan your cutover calendar around trading calendars<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Utilities &amp; Energy<\/strong><\/h3>\n\n\n\n<ul>\n<li><strong>Priority modules:<\/strong> IS-U (Industry Solution Utilities), PM, FICO, and SAP S\/4HANA Utilities<\/li>\n\n\n\n<li><strong>Key consideration:<\/strong> The IS-U to S\/4HANA Utilities migration path is specialized; not all brownfield conversion tools apply<\/li>\n\n\n\n<li><strong>Roadmap tip:<\/strong> Utilities projects typically take longer due to extremely high data volumes in billing and metering, and <a href=\"https:\/\/www.guvi.in\/blog\/replit-automated-database-migrations\/\" target=\"_blank\" rel=\"noreferrer noopener\">data migration<\/a> is almost always on the critical path<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Healthcare &amp; Life Sciences<\/strong><\/h3>\n\n\n\n<ul>\n<li><strong>Priority modules:<\/strong> MM, FICO, PM, QM, and GxP compliance configuration<\/li>\n\n\n\n<li><strong>Key consideration:<\/strong> FDA 21 CFR Part 11, GMP, and GAMP5 validation requirements apply to SAP system validation. This adds 20\u201330% to testing timelines<\/li>\n\n\n\n<li><strong>Roadmap tip:<\/strong> Build your validation master plan before the Realize phase begins,&nbsp; not as an afterthought after configuration is complete<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Financial Services<\/strong><\/h3>\n\n\n\n<ul>\n<li><strong>Priority modules:<\/strong> FI, CO, TR (Treasury), FSCM (Financial Supply Chain Management), and regulatory reporting<\/li>\n\n\n\n<li><strong>Key consideration:<\/strong> IFRS 9, IFRS 17 (insurance), Basel IV (banking), and local GAAP compliance requirements heavily influence FI configuration and reporting design<\/li>\n\n\n\n<li><strong>Roadmap tip:<\/strong> Financial services organizations typically have the most complex integration landscapes, and integration architecture deserves disproportionate planning investment<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>SAP Roadmap vs. SAP Implementation Plan<\/strong><\/h2>\n\n\n\n<p><strong>Direct Answer:<\/strong> An SAP Roadmap is a strategic, multi-year vision document that defines what to build and when, while an SAP Implementation Plan is the tactical, project-level document that defines how to build it. The roadmap drives the implementation plan,&nbsp; not the other way around.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><\/td><td><strong>SAP Roadmap<\/strong><\/td><td><strong>SAP Implementation Plan<\/strong><\/td><\/tr><tr><td><strong>Time horizon<\/strong><\/td><td>3\u20135 years<\/td><td>6\u201318 months<\/td><\/tr><tr><td><strong>Audience<\/strong><\/td><td>C-suite, Board, IT Leadership<\/td><td>Project team, workstream leads<\/td><\/tr><tr><td><strong>Level of detail<\/strong><\/td><td>Strategic, high-level<\/td><td>Tactical, detailed tasks<\/td><\/tr><tr><td><strong>Owned by<\/strong><\/td><td>CIO \/ Transformation Lead<\/td><td>SAP Project Manager<\/td><\/tr><tr><td><strong>Updated<\/strong><\/td><td>Annually or at major milestones<\/td><td>Weekly \/ Sprint-by-sprint<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>SAP Roadmap Template: What Should It Include?<\/strong><\/h2>\n\n\n\n<p>A practical SAP Roadmap document should cover these eight components:<\/p>\n\n\n\n<p><strong>1. Executive Summary:<\/strong>&nbsp; Vision statement, strategic objectives, and top 3 business drivers for SAP transformation<\/p>\n\n\n\n<p><strong>2. Current State Summary:<\/strong>&nbsp; SAP landscape overview, key pain points, and custom code complexity score<\/p>\n\n\n\n<p><strong>3. Target State Architecture:<\/strong>&nbsp; Target SAP product landscape diagram, deployment model decision, and integration architecture overview<\/p>\n\n\n\n<p><strong>4. Transformation Approach:<\/strong>&nbsp; Greenfield \/ Brownfield \/ Bluefield decision with rationale, chosen methodology, and system integrator selection criteria<\/p>\n\n\n\n<p><strong>5. Phased Roadmap Timeline:<\/strong>&nbsp; Multi-year Gantt chart or swim-lane timeline with phase-by-phase milestones, deliverables, and critical path<\/p>\n\n\n\n<p><strong>6. Resource &amp; Investment Plan:<\/strong> Headcount (internal + external), budget by phase, and license and infrastructure cost projections<\/p>\n\n\n\n<p><strong>7. Risk Register:<\/strong> Top 10 risks with likelihood\/impact matrix and mitigation strategy per risk<\/p>\n\n\n\n<p><strong>8. Governance Model: <\/strong>&nbsp;Steering committee composition, escalation paths, and decision-making RACI<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>SAP Roadmap Tools and Resources<\/strong><\/h2>\n\n\n\n<p><strong>SAP-provided tools:<\/strong><\/p>\n\n\n\n<ul>\n<li><strong>SAP Readiness Check: <\/strong>Free tool to assess <a href=\"https:\/\/help.sap.com\/docs\/SAP_READINESS_CHECK?locale=en-US&amp;state=PRODUCTION&amp;version=latest\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">ECC-to-S\/4HANA<\/a> conversion readiness<br><\/li>\n\n\n\n<li><strong>SAP Business Transformation Center (BTC): <\/strong><a href=\"https:\/\/support.sap.com\/en\/alm\/sap-cloud-alm\/transformation\/btc.html\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Custom code<\/a> and process impact analysis<\/li>\n\n\n\n<li><strong>SAP Value Lifecycle Manager (VLM): <\/strong>&nbsp;ROI and <a href=\"https:\/\/www.sap.com\/campaigns\/dg\/business-suite-cio-glo?pttid=7756&amp;campaigncode=crm-ya22-int-1517075&amp;source=ppc-in-googleads-search-22588893052-179121617759-clouderpgrow_s4s-x-x-x&amp;gclsrc=aw.ds&amp;gad_source=1&amp;gad_campaignid=22588893052&amp;gbraid=0AAAAA_r6tp0Rva80GXkr7Yyih3Hj1V0F8&amp;gclid=CjwKCAjwrNrQBhBjEiwAoR4VO8-ewXv2SSm-GdeyuYE_ayMvQzXWatZACMAPzS9qAlYZwOQWb1IoJxoCSnkQAvD_BwE\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">business case modeling<\/a><\/li>\n\n\n\n<li><strong>SAP Activate Roadmap Viewer: <\/strong>&nbsp;<a href=\"https:\/\/www.sap.com\/india\/account.html?pttid=7825&amp;campaigncode=crm-yd25-crs-406952&amp;source=ppc-in-googleads--20804399037-157725264884-x_x-x-x-x&amp;gclsrc=aw.ds&amp;gad_source=1&amp;gad_campaignid=20804399037&amp;gbraid=0AAAAAqhkG6B9CQJuxQKN60japmt5TOxn6&amp;gclid=CjwKCAjwrNrQBhBjEiwAoR4VO_g7T9KvShjSaQ2CTiQm9qHNJipI4qFeHZB-8iSD9Zv1UPHJtmmTFRoCVFAQAvD_BwE\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Interactive methodology<\/a> guide and accelerator library<\/li>\n\n\n\n<li><strong>SAP for Me: <\/strong>&nbsp;<a href=\"https:\/\/me.sap.com\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Customer portal<\/a> for licenses, support, and product roadmap access<\/li>\n<\/ul>\n\n\n\n<p><strong>Third-party and complementary tools:<\/strong><\/p>\n\n\n\n<ul>\n<li><strong>LeanIX: <\/strong>&nbsp;IT landscape and <a href=\"https:\/\/help.sap.com\/docs\/leanix?locale=en-US&amp;state=PRODUCTION&amp;version=CLOUD\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">enterprise architecture<\/a> management<\/li>\n\n\n\n<li><strong>Signavio: <\/strong>Business <a href=\"https:\/\/www.signavio.com\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">process intelligence<\/a> and mining<\/li>\n\n\n\n<li><strong>Celonis: <\/strong>&nbsp;Process mining to <a href=\"https:\/\/www.celonis.com\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">identify inefficiencies<\/a> before SAP transformation<\/li>\n\n\n\n<li><strong>Tricentis: <\/strong>SAP <a href=\"https:\/\/www.tricentis.com\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">test automation <\/a>and risk-based testing<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Common SAP Roadmap Mistakes to Avoid<\/strong><\/h2>\n\n\n\n<ol>\n<li><strong>Skipping the discovery phase: <\/strong>&nbsp;You cannot design a roadmap without knowing your current landscape<\/li>\n\n\n\n<li><strong>Underestimating data migration complexity: <\/strong>&nbsp;Data is always harder, messier, and more time-consuming than expected<\/li>\n\n\n\n<li><strong>Ignoring change management: <\/strong>70% of SAP project failures are people problems, not technical problems<\/li>\n\n\n\n<li><strong>Over-customizing: <\/strong>Every custom object you build increases upgrade risk and total cost<\/li>\n\n\n\n<li><strong>No executive sponsorship: <\/strong>SAP transformations without a committed C-level sponsor rarely succeed<\/li>\n\n\n\n<li><strong>Treating go-live as the end: <\/strong>Post-go-live adoption and optimization drive the real ROI<\/li>\n\n\n\n<li><strong>Not aligning with SAP&#8217;s clean core strategy: <\/strong>&nbsp;Building non-clean-core customizations in 2026 is technical debt before you even go live<\/li>\n<\/ol>\n\n\n\n<p><strong>Actionable Next Steps<\/strong><\/p>\n\n\n\n<p>If you are starting your SAP Roadmap journey, here is a prioritized action list:<\/p>\n\n\n\n<ol>\n<li><strong>Run SAP Readiness Check<\/strong> on your ECC system today (free via SAP for Me)<\/li>\n\n\n\n<li><strong>Define your 2027\/2030 compliance posture<\/strong>: when does your maintenance window close?<\/li>\n\n\n\n<li><strong>Engage an SAP partner<\/strong> for a 2\u20134 week discovery and roadmap scoping engagement<\/li>\n\n\n\n<li><strong>Build your internal business case<\/strong> using SAP&#8217;s Value Lifecycle Manager<\/li>\n\n\n\n<li><strong>Align your roadmap with SAP&#8217;s clean core strategy<\/strong>: avoid building technical debt now<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>An SAP Roadmap is not a luxury; it is the strategic backbone of any successful SAP transformation. Whether you are planning your first SAP implementation, migrating from ECC to S\/4HANA, or expanding your SAP footprint to the cloud, a well-structured roadmap de-risks your investment, aligns your organization, and maximizes the value of your SAP ecosystem.<\/p>\n\n\n\n<p>The organizations that succeed in SAP transformations are not the ones with the biggest budgets; they are the ones with the clearest roadmaps.<\/p>\n\n\n\n<p>Your SAP Roadmap Starts Here!&nbsp;<\/p>\n\n\n\n<p>The organizations that succeed in SAP transformations are not the ones with the biggest budgets; they are the ones with the clearest roadmaps. Build the skills to lead yours.\u00a0 Start Your <a href=\"https:\/\/www.guvi.in\/courses\/business-and-management\/sap-s4-hana\/?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=how-to-build-an-sap-roadmap\" target=\"_blank\" data-type=\"link\" data-id=\"https:\/\/www.guvi.in\/courses\/business-and-management\/sap-s4-hana\/?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=how-to-build-an-sap-roadmap\" rel=\"noreferrer noopener\">SAP S\/4HANA Journey on HCL GUVI.\u00a0<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>What Is an SAP Roadmap? An SAP Roadmap is a structured, long-term strategic plan that outlines how an organization will adopt, upgrade, migrate, or expand its SAP ecosystem over time. It answers three critical questions: An SAP Roadmap is not a single document; it is a living plan that evolves with your business, SAP product [&hellip;]<\/p>\n","protected":false},"author":66,"featured_media":113403,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[998],"tags":[],"views":"25","authorinfo":{"name":"Salini Balasubramaniam","url":"https:\/\/www.guvi.in\/blog\/author\/salini\/"},"thumbnailURL":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/05\/SAP-Roadmap-300x116.webp","jetpack_featured_media_url":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/05\/SAP-Roadmap.webp","_links":{"self":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/112870"}],"collection":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/users\/66"}],"replies":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/comments?post=112870"}],"version-history":[{"count":7,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/112870\/revisions"}],"predecessor-version":[{"id":113522,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/112870\/revisions\/113522"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media\/113403"}],"wp:attachment":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media?parent=112870"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/categories?post=112870"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/tags?post=112870"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}