Hannaware LLC logoHANNAWARE LLC
Home › PeopleTools Upgrades › PeopleTools 8.63

PeopleTools 8.63 Upgrade: Planning Guide and Checklist

What to check, prepare and automate before moving your PeopleSoft applications to PeopleTools 8.63.

Published November 5, 2026 · Hannaware LLC

Where PeopleTools 8.63 stands

Oracle released PeopleTools 8.63 first for Oracle Cloud Infrastructure through PeopleSoft Cloud Manager (July 2026), then for on-premises installation (October 2026, starting with patch 8.63.04). With on-premises availability, PeopleTools 8.63 is now a practical target for organizations running 8.60, 8.61 or 8.62.

Always confirm the current patch level, certifications and support dates for your platform on My Oracle Support before you commit to a plan. Certifications change with each patch.

PeopleTools 8.63 upgrade checklist

1. Assess where you are

  • Record your current PeopleTools release and patch, application releases (HCM, FSCM, Campus Solutions, Interaction Hub, ELM) and PUM image levels.
  • Inventory customizations, integrations (Integration Broker) and batch processes that a new release could affect.
  • Note your infrastructure: database version, operating systems, WebLogic, Tuxedo, COBOL and search (Elasticsearch or OpenSearch).

2. Check certifications

  • Compare every infrastructure component against the PeopleTools 8.63 certifications for your platform.
  • Plan database, operating system or middleware upgrades that must happen before, or together with, the PeopleTools upgrade.
  • Confirm browser and client requirements for your users.

3. Decide where it will run

  • OCI: PeopleSoft Cloud Manager can provision and upgrade 8.63 environments.
  • On-premises or AWS: build new tiers with the 8.63 Deployment Packages (DPKs).
  • Use the upgrade to retire old servers instead of patching them in place.

4. Automate the environment builds

  • Expect to build the upgrade environment several times: initial pass, test moves and the final cutover.
  • Script the builds in Jenkins so every pass is identical, including start/stop, cache clearing and refreshes with data masking.
  • AI coding tools can speed this up considerably: we use them to automate building upgrade and patch servers and keep reusable automation for each upgrade and patch cycle.

5. Run the upgrade and test

  • Run the PeopleTools upgrade with Change Assistant and apply the PUM updates you need.
  • Plan at least one full test move before production, and time each step.
  • Give functional teams a clear test window for regression, integrations and reports.

6. Cut over with a short outage

  • Use the timings from your test moves to set a realistic cutover window.
  • Where possible, run PeopleTools and PUM upgrades in parallel across applications to shorten downtime.
  • Keep disaster-recovery environments in sync (for example with Oracle GoldenGate) and have a tested fallback.

7. Stabilize and stay current

  • Validate, tune application servers and JVMs for peak load, and monitor the first business cycles.
  • Put quarterly Critical Patch Updates (CPUs) and monthly Critical Security Patch Updates (CSPUs) on an automated schedule so the next upgrade starts from a clean, current baseline.

How Hannaware helps

Hannaware delivers PeopleTools upgrades end to end: readiness assessment, certification review, automated environment builds with Jenkins and AI-assisted tooling, the upgrade itself, and post-upgrade stabilization. Our upgrade experience spans PeopleTools 8.55 through 8.62 across HCM, FSCM, Campus Solutions and Interaction Hub, on-premises, on OCI with Cloud Manager, and on AWS.

Request a PeopleTools 8.63 upgrade assessment

See all PeopleTools upgrade services.