As you may already know, SAP continues to recommend deploying SAP Fiori for SAP S/4HANA using an embedded SAP Fiori Front-End Server.
Over the years, many customers who initially started with a standalone FES have been transitioning to embedded deployment to reduce complexity, optimise operations, and align with SAP’s long term architecture.
Looking ahead, this direction becomes even more explicit. As outlined in the SAP Fiori Deployment Options and System Landscape Recommendations (as of Guide’s Version 10.3, February 2026) under the section Outlook: Fiori Deployment, the guide explicitly states:
SAP Fiori Deployment Options and System Landscape Recommendations, Section ‘Outlook: Fiori Deployment”
“Please be aware that as of SAP S/4HANA 2027 the embedded deployment option will be the only available deployment option”. This effectively makes embedded deployment not just the recommended approach, but the standard going forward for SAP Fiori in SAP S/4HANA landscapes.
In this context, we’re excited to share the updated “Moving from Standalone to Embedded Deployment in SAP Fiori for SAP S/4HANA” guide, based on SAP S/4HANA 2025, which becomes even more relevant for customers planning or progressing through this transition.
The guide was first published in October 2019 (version 1.0). It has since evolved through multiple updates, including version 2.1 in December 2024, which focused on SAP Fiori for SAP S/4HANA 2023. The most recent version, 3.0 released in March 2026, is based on SAP Fiori for SAP S/4HANA 2025.
This latest update (Version 3.0, March 2026) has been driven with strong input from SAP product experts, including Peter Persiel (peterpersiel) , whose contributions have helped shape the guide based on real-world customer experiences and evolving SAP Fiori architecture.
So what actually changed?
This blog highlights the latest updates and key enhancements introduced in the 2026 version of the guide (Version 3.0 March 2026), helping you quickly understand what’s new, what’s improved, and what to consider for your projects going forward.
Why this update matters?
Version 3.0 of this guide is an important refresh. It reflects:
- Alignment with SAP S/4HANA 2025 and SAP Fiori for SAP S/4HANA 2025, and important announcements planned in the future releases of SAP S/4HANA.
- The continued evolution of SAP Fiori architecture and activation tooling, especially in embedded deployments
- Lessons learned from more recent customer implementations, translating real project experience into more practical guidance
- Increased focus on clean core, maintainability, and lifecycle management
Why do you need this guide?
This guide is essential for SAP S/4HANA customers currently running or considering a hub/standalone SAP Fiori Front-End Server deployment, and who are planning or preparing for a transition from a hub/standalone SAP Fiori Front-End Server deployment to an embedded deployment.
It provides clear, structured guidance to support a smooth transition, covering both technical and practical aspects of the move. Whether you are upgrading your SAP S/4HANA system or proactively aligning with SAP’s long term architectural direction, this guide helps you plan and execute the transition with confidence.
From planning, installation, and configuration to post migration validation and optimisation, it brings together everything you need to successfully move to an embedded SAP Fiori deployment.
It helps you:
- Understand the benefits of moving to embedded FES deployment
- Know the right time to make the shift
- Navigate technical prerequisites, sizing, and system considerations
- Simplify the migration process with actionable steps, tools, and examples
- Ensure a seamless experience for users by resolving common issues
- Minimise disruptions by retaining user personalisation and role assignments
- Gain tips on how to enhance usability and performance
By following this guide, you can align with SAP best practices and unlock the full potential of SAP Fiori embedded deployment.
- Simplified architecture in SAP S/4HANA 2025
Some Front-end components are now part of the core platform, reducing system complexity - More practical, end-to-end guidance
Covers not just migration steps, but also planning, validation, and long term operations - Better control of custom content migration
Helps define what custom content to move and adds validation after migration instead of blindly transporting everything - Improved transport strategy guidance
Real world options for handling transports depending on your landscape and ongoing development activities - Extended launchpad configuration coverage
Includes transport of launchpad parameters, plug ins, and configuration settings beyond just apps and catalogs - Built-in validation step
Dedicated step to validate custom content in the embedded system after migration - Enhanced personalisation migration
Clear guidance using tools like /UIF/MIGRATE_FES_PERSO to retain user settings, homepages, and UI changes - Explicit system alias and RFC adjustments
Clear steps to adjust system aliases and RFC destinations post migration - Smarter SAP Notes handling
Explicit step to identify and implement missing SAP Notes after migration, avoiding common post go live issues - Stronger focus on business roles
Additional step to review and optimise business roles after migration in line with modern Fiori design
You’ll find much more on our SAP Fiori for SAP S/4HANA topic page
Other helpful links:
Brought to you by the SAP S/4HANA RIG and Customer Care team.
