Top Danmark
Governing a Complex SAP S/4HANA Conversion in a Regulated Insurance Environment
Client Overview
Topdanmark is one of Denmark’s leading insurance companies, operating in a highly regulated financial environment where system stability, audit compliance, and operational continuity are critical.
SAP systems support core financial, claims, and policy administration processes — making any major platform transformation a high-risk initiative.
The Context
Topdanmark initiated a conversion from SAP ECC to SAP S/4HANA.
Unlike a greenfield implementation, a conversion project involves:
- Legacy custom code
- Historical data complexity
- Integrated third-party systems
- Existing process structures
- Business-critical uptime requirements
A conversion is not a redesign from scratch.
It is a transformation under constraint.
The Challenge
The S/4HANA conversion introduced several critical challenges:
- Identifying and handling custom developments
- Managing technical remediation
- Aligning business processes to S/4 capabilities
- Ensuring regression stability
- Maintaining operational continuity during transformation
- Controlling release waves and deployment risk
In a financial environment, instability during conversion can impact:
- Financial reporting
- Claims processing
- Regulatory compliance
- Customer service operations
The tolerance for disruption was minimal.
The Role
The engagement focused on governance and structured execution within the S/4HANA conversion program.
Change & Release Governance
- Structuring release waves
- Coordinating cross-functional dependencies
- Managing transport sequencing
- Ensuring approval discipline
Risk-Controlled Deployment
- Supporting structured cutover preparation
- Aligning IT deployment with business readiness
- Ensuring rollback awareness and contingency planning
Landscape Transparency
- Supporting visibility across systems and dependencies
- Identifying technical risk areas
- Aligning technical remediation with business priorities
The role required balancing technical understanding with governance discipline.
Governance Approach
Rather than treating the conversion as a purely technical upgrade, the approach emphasized:
- Structured control mechanisms
- Clear ownership and responsibilities
- Defined decision gates
- Transparent release management
- Business-aligned timing
The conversion was governed as a transformation program — not a system upgrade.
The Result
- Controlled release cycles during conversion
- Reduced deployment risk
- Clearer visibility across program dependencies
- Strong coordination between IT and business stakeholders
- Stabilized go-live preparation
The S/4HANA conversion was executed with focus on control and continuity rather than speed alone.
Strategic Insight
Conversions are often underestimated.
They appear “simpler” than greenfield programs — but legacy complexity increases hidden risk.
Success depends on:
- Strong governance
- Controlled change management
- Structured release execution
- Cross-functional coordination
Experience in conversion programs builds a deep understanding of how SAP landscapes evolve — and how risk must be managed during structural transformation.
Why This Matters
Organizations planning S/4HANA conversions often focus heavily on technical readiness.
However, governance maturity often determines success. Understanding how to structure release control, manage dependencies, and align business readiness is critical to avoiding post-go-live instability.
Closing Perspective
S/4HANA conversions are not technical migrations.
They are risk-managed transformations of business-critical platforms. Structured governance is the difference between controlled modernization — and operational exposure.
Client Overview
H&M Group is one of the world’s largest fashion retailers, operating across multiple markets with complex supply chain, finance, and retail system landscapes.
SAP plays a central role in supporting global business processes — making structured change and release management critical to operational stability.
The Context
At H&M, SAP Solution Manager was used as the central Application Lifecycle Management platform, with a strong focus on ChaRM (Change Request Management).
The landscape was large.
The release cycles were complex.
The business impact of failure was high.
Even minor change errors could affect:
- Retail operations
- Logistics flows
- Financial postings
- Store operations across markets
This was not about configuring ChaRM.
This was about running enterprise-scale release governance from the customer side.
The Challenge
The environment included:
- Multiple parallel development tracks
- High release frequency
- Cross-functional dependencies
- Global rollout complexity
- Strict separation of duties
Key challenges included:
- Ensuring release transparency
- Preventing transport conflicts
- Coordinating approvals across stakeholders
- Maintaining stability during peak business periods
- Balancing agility with control
In global retail, downtime is not theoretical.
It is revenue impact.
The Role
Working on the customer side, responsibility included:
- Running ChaRM-based release cycles
- Coordinating change approvals
- Governing transport sequencing
- Aligning development and business readiness
- Ensuring structured go-live procedures
This required both technical understanding and governance discipline.
Release management was treated as a control function — not an administrative task.
Governance Approach
Changes were grouped into controlled release waves with:
- Defined scope boundaries
- Clear approval checkpoints
- Transport sequencing rules
- Pre-go-live validation
No uncontrolled deployments.
Transport Governance & Risk Control
ChaRM was used not only for documentation, but for:
- Enforcing approval workflows
- Preventing unauthorized transport imports
- Ensuring correct sequencing
- Creating traceability between change and deployment
This reduced production risk significantly.
Business Alignment
Release planning was aligned with:
- Business calendars
- Peak retail seasons
- Financial closing periods
- Market rollout schedules
Governance was aligned to business reality — not just IT timelines.
The Result
The structured ChaRM governance model delivered:
- Controlled enterprise release cycles
- Reduced transport conflicts
- Improved transparency for stakeholders
- Strong audit traceability
- Stable go-lives across complex landscapes
Most importantly:
Release governance became predictable instead of reactive.
Strategic Insight
Large SAP landscapes do not fail because of missing features.
They fail because of uncontrolled change.
This engagement built deep practical experience in:
- Enterprise release governance
- Transport control in complex landscapes
- Cross-functional coordination
- Change transparency under pressure
Why This Matters Today
As organizations transition toward SAP Cloud ALM, many underestimate what structured change governance really requires.
Tools change.
Governance principles do not.
Experience running enterprise ChaRM from the customer side provides critical insight when designing future lifecycle governance models — including transitions toward SAP Cloud ALM.
Closing Perspective
Enterprise SAP environments require more than configuration skills.
They require structured control, release discipline, and business-aligned governance.
That is the difference between technical setup — and operational stability.
More Clients...
