Key Considerations for EBS to Public Cloud Journey

Key Considerations for EBS to Public Cloud Migration

Introduction

Many organizations now want to take advantage of cost efficiency, scalability, security, and other benefits the cloud offers. For Oracle customers exploring Public cloud for their mission critical application, OCI automatically comes to the top of their assessment list. However this blog is relevant even if you are exploring AWS or GCP or any other public cloud provider for your Oracle application.

Migrating your EBS to public cloud infrastructure has to be planned and relevant questions needs to be answered, and you should also be aware of potential challenges to avoid at each stage of your EBS migration journey. You will have to identify and engage with relevant stakeholders and internal team members to make timely decisions and ensure the project is executed with a tentative timeline for each and every phase.

Certified expert partners can help fill missing skill gaps and can also help accelerate your cloud migration project to get it “first time right”.

This blog will help you guide with the key considerations for each of the phases of the OCI to Public cloud migration journey.

Phases to Migrate EBS to Public Cloud

What this Blog Covers

  • A checklist of questions to be answered.
  • An inventory of potential challenges to avoid.
  • A list of stakeholders to consult and make decisions.
  • An approximate number of months to complete each step.
  • The critical cost components to budget for.
  • A brief outcome to expect at the end of each step.

Plan

1. Learn whether cloud-based service adoption is practical & feasible.

Beyond the agility, flexibility and cost savings the cloud brings to the table, trends and technologies driving digital transformation today are also behind the mass migration to cloud computing. Cost vs benefits to be incurred for migration EBS to Cloud have to be assessed at this planning stage. Oracle has made this decision easy by simplifying the process by which EBS can be easily migrated to OCI, which might not be the case while migrating to AWS or GCP.

Trying to keep up with this growing demand for capacity is a difficult and costly onprem. A decision during a technology refresh cycle to move to cloud will be easy by justifying cost vs benefits.

Questions to ask

  • What does the organization require (based on regulations and contracts) to manage data?
  • What are the benefits expected from adoption?
  • What capital expenses will IT incur if most applications are migrated to a public cloud environment?

Stakeholders to engage: Project sponsor, CFO, business partners, IT security/data privacy specialist, legal advisor, HR advisor

Outcome: Determine the organization’s long-term vision for public cloud adoption based on value proposition and legal and cost requirements to be met.

Timeline: 3-9 months
Major Cost Components: 1 + 5%–10% time of stakeholders

2. Set up cloud migration as a project.

At this stage it is important to identify appropriate talent to manage large-scale enterprise-wide migration project. These could include IT / business. Assessing internal talent early can help identify the need for adding skills from certified Oracle cloud vendors / partners. Getting stakeholder buy-in from different business units for various business users will be important. CxO will have to be convinced with business reasons rather than just IT. A Oracle certified partner can help with advisory for the complete project and also deliver a TCO analysis to help you engage with various stakeholders.

Questions to ask

  • What are the key requirements for cloud migration?
  • What are the key factors that will determine our cloud migration delivery model?

Stakeholders to Engage: Project manager, application manager, change manager, project sponsor, enterprise architect, IT security/data privacy specialist, IT operations manager(s), subject matter experts, business analysts

Outcome: Determine the cloud delivery model, and identify the project management team and stakeholders.

Timeline: Entire migration can span 1–24 months depending on applications’ size and complexity.
Major Cost Components: 60% time of project management team + 5%–10% time of other stakeholders + project management software tools + collaboration tools

3. Manage governance and change adoption.

Upskilling staff for new roles and responsibilities is time consuming. Hence this has to be done early enough to nor slow down the migration. Identifying appropriate roles among business units and IT to make decisions, provide guidance, and support communications. Business users will not be convinced with only infrastructure migration to the cloud they need more value to their application. Instead of convincing people to migrate EBS to OCI with a Lift and shift strategy, adding enhancements & integration with SaaS environments for EBS would definitely take their interests.

Questions to ask

  • How do we identify and engage key IT and business stakeholders?
  • What communication messages will facilitate adoption of a cloud-based platform?
  • What are the staff and end-user training requirements?
  • How do we measure the progress of user adoption?

Stakeholders to Engage: Project sponsor, senior management, service desk manager, application end users

Outcome: Implement new metrics, and define roles and responsibilities for effective adoption of the new solution.

Timeline: Planned across the entire application migration process; between 1–24 months depending on the applications size and complexity
Major Cost Components: Developing communication materials + 2%–5% time of senior management and 5%-10% time of other stakeholders of senior management

Accelerating EBS migration to OCI

4. Analyze and prioritize application migration requirements.

Some application interdependencies are hard to locate until the migration happens. In case your application environment is complex, engage a certified Oracle MSP/MSE partner to help you in diving deep to ensure nothing is left to chance.

Migrating to new delivery models may require revisiting/revising data privacy policies. You may not need the exact same resources on the cloud as you have onprem. Get the right fit if you have excess infrastructure or are undersized to save cost or avoid slow systems respectively.

Questions to ask

  • Which EBS modules do we prioritize for migration based on costs, business value, risk, and integration requirements?
  • How will we manage a Hybrid environment in case of partial EBS migration to OCI?
  • Is there a need for adding new capabilities or functionalities for applications selected?
  • How will hosting this application on the cloud enhance its functionality and performance?
  • What are the resource requirements for application configuration to the cloud environment?
  • What are the security and integration readiness requirements?
  • What are the technical requirements and timeline for migrating the server and database to the cloud environment?

Stakeholders to Engage: Application manager, IT security/data privacy specialist, business continuity planning and disaster recovery planning manager

Outcome: Identify and prioritize the scope of migrating an application.

Timeline: 1–3 months depending on the complexity of the application and the environment
Major Cost Components1: Time to interview business partners + time to identify and collaborate with application owners + time to develop a tiering map + 8%–10% time of stakeholders

Build

5. Select a cloud vendor and a migration support provider.

Conducting due diligence of niche cloud solutions with limited information. While Oracle OCI automatically may come to the top of the list. It is wise to assess capabilities of other cloud providers too. Migration support providers lack knowledge of organization’s business and system complexity. However Oracle has few expert cloud certified partners in North America , (called MSE partners), trained for easy to complex migration projects. They can add more value than just migration like, Managed services, single billing of all Oracle services, security management, managing your Oracle relation on your behalf.

Questions to ask

  • What are the technical requirements to be included in the RFP, including SLAs for the service?
  • What trade-offs between cost, features, and technical fit should we consider for selecting cloud vendors and migration support providers?

Stakeholders to Engage: IT procurement, application manager, project sponsor, IT security/data privacy specialist

Outcome: Finalize the cloud vendor based on technical fit and cost–benefit analysis.

Timeline: 2–3 months depending on the number of providers in the market
Major Cost Components1: Visiting cloud provider locations + migration support provider contract + 5%–10% time of stakeholders

6. Develop and test proof of concept (POC).

A sample test may not highlight all critical security and performance issues. Configuration of a testing environment may not be as complex as a production environment, which may lead to unexpected failures during actual migration. Hence the testing environment should be taking into consideration various scenarios of the production environment.

Questions to ask

  • What are the key applications to be tested during POC?
  • What performance, security, and compliance parameters are to be tested in the cloud environment?
  • What are the success criteria for POC?

Stakeholders to Engage: IT operations manager(s), database manager, IT security/data privacy specialist, service desk manager, change managers, quality assurance manager

Outcome: Identify and fix performance, security, and compliance issues for migrating applications to the cloud environment.

Timeline: 3–6 months depending on the business criticality of the application
Major Cost Components1: Third-party application support + 10%–15% time of stakeholders

7. Upgrade the existing infrastructure environment.

High costs of upgrading core infrastructure increase the difficulty of getting stakeholder buy-in. Hence it is important to get the right size of all the components beforehand. Unexpected cost outcomes can be overcomed with the help of certified partners who have the right tools and technology to ensure your cost fall within the planned budget. They can also help avoid technical difficulty in deploying data and application access management plan for public cloud environments

  • What additional network bandwidth is required to support the cloud environment?
  • What are the technical requirements to integrate the new solution with existing IT Service Management processes?
  • What does the service desk need to know about the cloud environment?
  • How will cloud adoption affect existing operational processes?

Stakeholders to Engage: Vendor, IT operations manager(s), database manager, IT security/data privacy specialist, finance operations manager, IT procurement manager, IT administrators

Outcome: Upgrade the Infrastructure environment to enable effective utilization of the new solution.

Timeline: 3–4 months depending on the current maturity of the environment, size of Applications, maturity of IT service management processes
Major Cost Components1: Capital investment in setting up the environment + 10%–12% time of stakeholders

Migrate

8. Migrate to the cloud.

Many security and performance issues surface only during migration of complex applications or Integrations to the cloud environment. Security and performance issues could cause unexpected disruption of work. Hence planning well can help you ensure smooth and successful migration.

  • How do we ensure limited or no downtime for mission-critical applications?
  • What backup resources are required to manage any failures during migration?

Stakeholders to Engage: IT operations manager(s), database manager, IT security/data privacy specialist, applications owner, change manager, project manager

Outcome: Migrate the application to the cloud environment with minimal disruption to work.

Timeline: 2–4 months depending on the interdependencies of the application and the security requirements
Major Cost Components1: Network bandwidth + hosting cost + one-time set fees and charges + 5%–10% time of stakeholders

Run

9. Manage the vendor relationship.

Minimizing vendor lock-in to balance data integration and performance requirements. Leverage services from the migration vendor partner with strict control on SLA’s, measure them on a continuous basis. Leverage them to help optimize and fine tune your cloud for maximization of performance. You can let them take the many critical but routine tasks off your hands, so your team can focus exclusively on your strategic business opportunities.

  • How do we measure vendor risk?
  • How do we monitor vendors continuously in terms of cost, benefit, and ease of use of the solution?

Stakeholders to Engage: Vendors, IT procurement, IT operations manager(s)

Outcome: Assess the vendor using metrics to predict risk exposure over time.

Timeline: Ongoing through the life cycle of vendor engagement
Major Cost Components: Monitoring software tools + contract for managed service + 5%–7% time of stakeholders