The procedure of the transition depends very much on the use cases implemented on the SAP Enterprise Portal and is therefore quite customer-specific.
Since no portal is like the other, the first step in the transition is to carry out a stocktaking or "portal inspection". Based on that everything else should be planned.
Basically, the transition can be approached/planned completely or partially. If the Business Use Cases allow it, a partial or step-by-step transition is recommended to reduce complexity. For example, you could proceed in a use case-oriented or data type-oriented manner.
The transition of the SAP EP based Universal Worklist (UWL) is an example of a use case that can be transformed to the cloud quite well separated. Likewise, the SAP Enterprise Portal-based document stores in Knowledge Management (KM) could be migrated in isolation as a closed data source. Since there are suitable successors or substitutes with the SAP Document Center/Document Service and the Egnyte partner solution recommended by SAP, this use case can indeed be described as a real (data) migration. In the transition phase of the partial transition, one would then operate a hybrid portal with integrated on-premise and cloud services.
Based on the proven VANTAiO portal project procedure model, we have developed a template/schema for the EP to CP transition. It consists of the following phases: Preparation, detailed conception, implementation (divided into waves/sprints) as well as introduction and go-live: