SAP Enable Now Migration: Preserve and Modernize Your Content
Moving is the best opportunity to tidy up
Moving is rarely just a change of location. It is a moment of decision. What do we take with us? What needs to be revised? And what can finally be discarded?
The switch from SAP Enable Now to tts performance suite is just such a moment. Over the years, companies have made considerable investments in documentation, simulations, and e-learning. This content is valuable. It contains process knowledge, training logic, and technical experience.
The key question is therefore not: “Will our content be lost?”
But rather: “How can we secure its value—and at the same time use the change for qualitative further development?”
A structured move protects your investment. And creates space for modernization.
The value lies in the content – not in the system
In many discussions with SAP managers, the same concern arises: When the system ends, does the usefulness of our content also end? Behind this question lie budget, project time, and technical expertise. At first glance, this investment seems inextricably linked to the tool used.
However, a system change does not automatically mean a loss of knowledge. The decisive factor is how structured the transfer is. Those who see the change as a mere tool replacement overlook the strategic dimension. Those who use it as an opportunity for consolidation not only secure existing content, but also strengthen their overall user enablement in the long term.
The question is therefore not: “What are we losing?”
But rather: “How can we make existing knowledge usable in a future-proof way?”
Taking stock instead of rushing into action: preserve 60%, renovate 20% in a targeted manner
Changing systems does not mean starting from scratch. Experience shows that most of the existing content can continue to be used.
Around 60% of the content can be migrated and transferred unchanged. The decisive factor here is not technical feasibility, but professional relevance: Which content is still valid and actually needed in everyday work?
Another 20% is recreated. About 15% of this would have had to be revised anyway because processes, roles, or interfaces have changed. Another 5% is deliberately recreated to use modern formats and support users more specifically in their workflow.
The remaining 20% will deliberately not be carried over as part of a structured clean-up.
This will not result in a radical restart, but rather a controlled transition with a secure investment and clear further development.
Two ways to migrate existing content in a structured manner
There are two practical approaches available for migrating from SAP Enable Now to the tts performance suite, depending on your objectives and further development requirements.
1. Stable transfer: SCORM import
Current content that is to continue to be used can be exported directly from SAP Enable Now as SCORM and imported into the tts performance suite.
It remains fully executable and can even be made available in the workflow in a context-sensitive and role-based manner. For content that is technically correct and still didactically appropriate, this is the fastest way to ensure continuity.
This option protects your investment – without additional development effort.
2. Further development: Export to e-learning template
A second option is available for content that is valuable but needs to be flexible for future editing.
The SAP Enable Now .dkp format can be exported and imported into the e-learning template of the tts performance suite. This allows content to remain editable and can be modernized step by step. This means that existing knowledge is not frozen, but can be further developed.
Both approaches enable a controlled transition. The decision depends on whether stability or further development is the priority..
More than migration: effectively developing content
Migration ensures continuity. But the real added value of the tts performance suite comes into play when content is consciously developed and new opportunities are specifically exploited.
A system change can be more than just a technical transfer. It creates a moment of reflection: Which formats really support users in their workflow today? And where is it worth redesigning the didactic approach?
Content that made sense in SAP Enable Now does not automatically fulfill the same function in the new environment. Classic job help may be technically correct. In everyday use, however, users often benefit more from clearly structured step-by-step lists that guide them through a process in a targeted manner.
This is where the strategic decision lies: Do we revise what we have, or do we redesign it to increase its usability in the work context?
The platform opens up new possibilities for knowledge provision. Those who use the change to modernize formats in a targeted manner not only increase the timeliness but, above all, the effectiveness of the enablement.
Secure what you have. Improve in a targeted manner. And rethink where it makes sense.
Meaningful migration: Secure existing content and develop it in a targeted manner
The switch from SAP Enable Now to tts performance suite is not a break with the past. It is an opportunity to secure existing content and develop it in a targeted manner. Your content investment remains intact: a large part of it can be transferred and used immediately. At the same time, the move opens up the opportunity to critically review content, clean it up, and redesign it where it makes sense.
Those who take a structured approach win twice. The transition remains stable and effectiveness in everyday work increases.
Ultimately, it's not about moving content from A to B. It's about providing knowledge in such a way that users can execute processes securely, efficiently, and in compliance with regulations.
A move can be exhausting. But it can also be liberating. The crucial question is: Are you using the change only for migration or for the qualitative further development of your entire user enablement?
FAQ: Migration from SAP Enable Now to tts performance suite
Can existing SAP Enable Now content continue to be used in tts performance suite?
Yes. Existing content can either be exported as SCORM and transferred in a functional format or imported into the e-learning template of the tts performance suite. This means that it remains usable and, depending on the option chosen, can also be edited further. Your previous content investment will not be lost.
Will migrated content remain editable in the future?
If content is transferred in SCORM format, it remains stable and executable, but cannot be edited directly.
If you want to further develop content flexibly, you can export the SAP Enable Now format and transfer it to the e-learning template of the tts performance suite. This creates editable learning objects.
Does all existing content have to be migrated?
No. Complete migration is not usually advisable. Experience shows that around 60% of content can be transferred directly and reused. Around 20% is recreated – often because processes, roles, or interfaces have changed. The remaining 20% is deliberately not migrated as part of a structured clean-up process, as it is outdated or no longer relevant.
Can migrated content be made available directly in the workflow?
Yes. Transferred content—including content in SCORM format—can be made available in the tts performance suite in a context-sensitive and role-based manner within the workflow. Users receive the content directly where they need it.
This means that support is not limited to training formats.
Is the migration AI-based?
No. Migration to the tts performance suite is structured and does not involve AI-supported transformation. This means that content is transferred in a controlled manner without automated content conversion.
This transparency is a decisive advantage, especially for organizations with high compliance, data protection, or quality requirements.
