Lift and Transform PeopleSoft to Oracle Cloud Infrastructure

Datavail 0 views 34 slides Oct 15, 2025
Slide 1
Slide 1 of 34
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34

About This Presentation

Lift and Transform PeopleSoft to Oracle Cloud Infrastructure
Migrating ERP systems like PeopleSoft to the cloud is a strategic move that promises agility, scalability, and cost savings—but it’s also a complex undertaking that requires careful planning and execution. For organizations looking to ...


Slide Content

LIFT AND TRANSFORM PEOPLESOFT
TO ORACLE CLOUD INFRASTRUCTURE
MAY 8 -MAY 11, 2023

Free Beer for a Year!

PRAMOD
ALLURI
VP, Datavail Solutions & Delivery,
Practice Lead Enterprise
Applications Division
•Pramod is VP, Datavail Solutions & Delivery, Practice Lead
Enterprise Applications Division at Datavail.
•He works with the High Tech/Process/Communications,
Media & Entertainment (CMT)/Services industries.
•He focuses on Mid/Large scale Business Transformation
programs leveraging modern technologies to deliver
tangible business value.
•Pramod has more than 28 years of experience solving
business challenges in Customer Advocacy, Business
Transformation, Operational Excellence and Sustainability.

ABOUT DATAVAIL
Our Range of Oracle Applications Services
Strategic
consulting
24x7 managed
services
Performance
tuning
Cloud
migrations
Assessments
& roadmaps
Monitoring
Upgrades
Data integration
& ETL
Applications & DB
We Support:
•Oracle PeopleSoft
•Oracle EBS
•Oracle Database
•Oracle Analytics
•Golden Gate
•WebLogic
•Oracle Data Integrator
•Cloud Platforms (AWS, Azure,
Oracle Cloud)
•And more …

•Cloud migrations are intricate and
complex projects that require expertise
in order to ensure a successful and
smooth migration for ERP/ Peoplesoft
applications.
•It is key that, before starting a cloud
migration, businesses ensure a
thorough and holistic migration plan is
put in place.
•We’ll discuss key areas to review that
are an absolute must for any Peoplesoft
preparing for a journey to the cloud.
INTRODUCTION
•Identify key risk areas and be prepared
with action plan and contingency in
planning phase versus being reactive.
•How this approach was applied to
PeopleSoft migration to OCI and
benefitted from it will be shared.

Peoplesoft migration used in this presentation -what was achieved by
customer.
•By migrating from obsolete hardware to OCI, the customer was able to achieve an impressive
40% cost benefit while also enjoying increased agility , flexibility and Productivity.
•The migration was completed within a short span of just 3 months , including the migration
of three environments (1 PROD + 2 DEV,TEST), upgrading the database from 12c to 19c,
and a People Tools upgrade.
•The migration involved a shift from the AIX operating system to Red Hat Enterprise Linux
(RHEL) with two payroll execution testing cycles.
•Successful transition that provided a solid foundation for future SaaS transformation projects.
INTRODUCTION

THE 7 ESSENTIAL ELEMENTS
7. Future State Backup &
Monitoring Solutions
1. Interface Jobs
2. Applications
Versions and
Certification Status
3. Current Storage
Solution
4. Data Migration Strategy
5. Storage
Footprint
6. Testing
Strategy

1. INTERFACE JOBS

•Identify all interface jobs and their connection methods
•Review understand current versus future state impacts due to Peoplesoft move.
•Review each interface job and their transaction volume stats.
•Any jobs with DB link connection method for processing versus interface table/staging
table involvement. Which may impact performance greatly with network latency.
INTERFACE JOBS

•Created efficient testing plan and KPI success criteria with interface jobs along with
performance needs.
•Interface connections to inbound/outbound to external vendors was identified and
planned for changes needed on either end, testing and production implementation
dates were communicated for validation.
•Understood SFTP server and its role changes with Peoplesoft migration , how it will
impact users with respect to daily operations.
INTERFACE JOBS REVIEW –GOALS ACHIEVED

2. APPLICATIONS
VERSIONS AND
CERTIFICATION
STATUS

•Review applications versions current state and certification status with Oracle Support,
and how it will impact migration dates.
•Application or DB-level
•OS Versions available on Cloud Platform, associated compatibility with current
application versions.
•There could be scenarios to consider changes at certain component level without
changing application-level functionality to stay close to Lift and Shift.
•Review strategy towards migrate first and upgrade later. Or do it together to benefit
from single round of testing based on timeline feasibility for migration.
APPLICATIONS VERSIONS AND CERTIFICATION STATUS

•Migrate from AIX to RHEL –Helped with planning Database migration approach given
big endian to small endian format change needs.
•Identified requirement to upgrade Database from 12c to 19c to stay current with oracle
support.
•Upgrade People Tools only requirement to support 19c Upgrade was identified.
•Aligned with security and compliance standards at O/S, DB, Application level.
APPLICATIONS VERSIONS AND
CERTIFICATION STATUS REVIEW –GOALS ACHIEVED

3. CURRENT
STORAGE SOLUTION

•Review Current Storage Solution and Database IOPS
requirement to meet business needs, so that
appropriate storage can be identified on the cloud
along with VM limitation
•Consider running your AWR report during both regular
and peak workloads from your existing infrastructure.
•This will help you choose the appropriate target server
to right-size for the target server build. Each cloud
platform provides these options differently.
CURRENT STORAGE SOLUTION
Potential areas to
review
•Virtual machine size
•Network throughput
•Disk types and
configurations

•Identified required VM’s, disks on OCI server to support database performance needs.
•Helped with cost estimate to be specific.
•Knowing there is room for scalability gave us confidence that performance won’t be of
any concern.
CURRENT STORAGE SOLUTION REVIEW –GOALS
ACHIEVED

4. DATA MIGRATION
STRATEGY

•Review Data Migration strategy from on-prem to Cloud to ensure cutover time is
minimal.
•Identify allowed downtime for cutover.
•Review various options to migrate the data over to target location.
•The bigger the size, the bigger the challenge…particularly when DB size bigger and
downtime window is minimal.
•Assure a process is identified and works as anticipated as part of POC to avoid possible
delays to the overall project.
DATA MIGRATION STRATEGY

•Given DB size less than 1 TB , allowed downtime for cutover being 24 hours.
•To achieve cross platform migration, planned for simple export and import method.
•To align with Testing Strategy needed to migrate data over network from on-premises
to OCI 2 times outside of production cutover. Allocated time required in project plan.
DATA MIGRATION STRATEGY REVIEW –GOALS ACHIEVED

5. STORAGE FOOTPRINT

•Evaluate Storage footprint cost reduction on the cloud with available options.
•Look at on-prem prod and non-prod DB storage utilization and cost.
•With cloud options and limitations around the storage, understand the impact and
change.
•Review and understand the options available from third party solution, as needed.
NOTE: Didn’t observe any benefits/concerns in this migration as size and no of environments were
on small scale.
STORAGE FOOTPRINT

6. TESTING STRATEGY

•Evaluate testing strategy to make sure surprises post migration will be at a minimum.
•KPI Testing strategy to include regression and load test scenarios.
•Not just jobs running and completing, but runtimes to be reviewed along with volume
details.
•Perform testing with PROD-like environment on cloud as a minor change in config
could increase the number of iterations for overall testing.
TESTING STRATEGY

•Allocated time for creating test scripts, execution separately as needed. Planned for
resource availability.
•Identified dates where production data backup is required to be used in each payroll
execution testing cycle.
•Agreed to conduct UAT on OCI production servers for performance and connectivity
validations.
•Provided confidence in production cutover success by executing the same process
twice before actual cutover.
TESTING STRATEGY REVIEW –GOALS ACHIEVED

7. FUTURE STATE
BACKUP AND
MONITORING
SOLUTIONS

•Review and understand backup solution on target
cloud platform for database.
•Backup -Will it be same or different? How does it
impact Recovery Time Objective (RTO) and
Recovery Point Objective (RPO)?
•Review monitoring tools and integration with ITSM
solution to understand the changes cloud would
bring for O/S level monitoring, and DB level
monitoring for operational needs.
•Review clone process and SLA’s with various teams
for operational needs as this could change the
amount of time required to perform clone with
cloud default options.
FUTURE STATE BACKUP AND MONITORING SOLUTIONS
•Review the environment Strategy, given new
environment build can be done with in a day or
two days with cloud capabilities. Keep minimum no
of environments for Operations and deploy and
remove based on needs.
•Review hibernation schedule for each environment
to optimize operational costs for required
environments to take advantage of compute costs.
Development team needs it up only for 12 hours ..
Remaining 12 hours we can keep it down with
automated shutdown and startup process while
meeting cloud platform requirements and
limitations.

•Implemented backup process to be cost effective utilizing cloud native tools aligning
RTO and RPO requirements.
•Implemented OEM monitoring for database.
•Utilize OCI console for VM monitoring.
•Established process for data refresh from PROD to DEV/TEST environments.
•Reviewed hibernation possibilities to utilize capabilities.
FUTURE STATE BACKUP AND MONITORING SOLUTIONS
REVIEW –GOALS ACHIEVED

CONCLUSION

By Reviewing these areas, unknown
concern will turn into known
concerns and possible actional plan
to address them as part of planning,
which makes the cloud journey much
more smooth and transparent for
various teams involved in a platform
change.
CONCLUSION

Q&A

Free Beer for a Year!

THANK YOU
[email protected]
PRAMOD ALLURI
VP, Datavail Solutions & Delivery, Practice Lead Enterprise Applications Division
datavail.com

Swap stories, ask questions, find answers
and learn from the JD Edwards community.
The JD Edwards community offers:
At Quest, you belong.
Event Hubs
Browse 150+ digital sessions from INFOCUS 22 or dig into other past conference content,
organized by track or hot topic
Special Interest Groups
Take your pick of 20 informal JD Edwards discussion groups including Business Analyst,
Finance, M&D and a host of other hot topics, including dedicated industry groups.
Strategic Content Centers
Expand your JD Edwards knowledge on Orchestrator, Release 22, and other hot topics