This phase involves collecting the necessary information to start the migration. During this phase, the scope of intervention and the involved technological ecosystem (DB ODI APEX PL/SQL VPD SAP BO QlikView/QlikSense, etc.) are identified, as well as internal and external software dependencies (touchpoints),
definition of test cases for components impacted by the porting, and drafting a detailed plan and service engagement to support the activities.
This is the core phase of the migration strategy involving the porting of all identified software components to OCI and the migration of historical data for each application. During this phase, the structural creation and configuration of the target environments, porting of all identified software to OCI, application of any necessary adjustments/rework,
creation and configuration of user environments, and the initial load of historical data are carried out
This phase involves executing appropriate tests and subsequent go-live of the application in OCI. During this phase, Unit Tests, No Regression Tests, and Performance Tests are conducted, analysis of necessary hardware resources for correct performance/cost balance,
support for factories in executing E2E Integration Tests, and scheduling starts in OCI on the new cloud environments
This is the final phase necessary for the recovery and release of on-prem resources. This phase involves supporting the progressive or big-bang deletion of on-premise ODI flows and any other technologies migrated to OCI,
as well as unused on-premise DB objects