Learn How Carrier Migrated Their Global Oracle Jde Landscape to Aws Ent222

Title

AWS re:Invent 2022 - Learn how Carrier migrated their global Oracle JDE landscape to AWS (ENT222)

Summary

  • Carrier, a Fortune 500 company, successfully migrated their JD Edwards (JDE) 9.2 from on-premises to AWS Cloud.
  • The project was led by Rick Carey from Carrier, with technical support from Jeremy Shearer, a senior partner architect at AWS.
  • Carrier's commitment to AWS included moving over 70% of their 4,000 servers and nearly 1,000 applications to AWS.
  • The migration involved six JDE instances, 16 data environments, and over 50 business units globally.
  • Over 3,000 test scenarios were completed, and more than 500 interfaces and integrations were migrated.
  • The project was completed in 10 months, moving approximately 2,000 business users seamlessly to the cloud.
  • Technical challenges included data compression, character set and case sensitivity issues, and Julian date formats.
  • Lessons learned from a previous migration in 2021 helped improve the process, including right-sizing infrastructure and cost management.
  • The success of the project was attributed to effective communication, cross-functional team involvement, executive support, and selecting experienced partners.

Insights

  • Carrier's migration to AWS was part of a strategic move to modernize and align with a Cloud First approach, emphasizing customer support and efficiency.
  • The decision to choose AWS over other cloud providers, including Oracle Cloud Infrastructure (OCI), was based on factors such as cost, scalability, performance, disaster recovery, and data movement.
  • The migration process involved significant data compression, achieving an 80% rate, which allowed for network transfer without additional AWS data transfer services.
  • Technical solutions included using SQL Server on EC2, leveraging AWS Database Migration Service, and optimizing instance types for JD Edwards workloads.
  • The project emphasized the importance of addressing technical debt, reducing run costs, and improving user experience.
  • Cultural, language, and localization considerations were critical, especially for global teams.
  • Organizational Change Management (OCM) played a significant role in ensuring user adoption and leveraging new tools and capabilities.
  • The partnership with AWS was crucial, with AWS providing honest feedback and cost-saving recommendations.
  • The experience underscores the viability of AWS as a cloud solution for JD Edwards and similar enterprise applications.