# Oracle Agile PLM End of Life and Cloud PLM Migration Readiness Assessment

> Source: https://netray.co/tools/agile-plm-to-cloud-migration-readiness-assessment
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Ten questions on your Agile PLM release, process extensions, event handlers, integrations, vault and data quality, scored into a readiness band with next steps.

## Category

oracle

## Erp

Oracle Agile PLM

## Industry

Discrete Manufacturing

## Audience

- PLM administrator
- Agile PLM developer
- Engineering systems manager
- IT architect

## Tool

**Kind:** assessment

**Questions:**

#### Which Agile PLM release are you running in production?

**Help:** 9.3.6 is the last 9.3.x release. Older releases add an in-place upgrade or extra data mapping work before any move.

**Options:**

##### Agile PLM 9.3.6 with recent patches applied

**Score:** 4

##### Agile PLM 9.3.6, patches well behind

**Score:** 3

##### Agile PLM 9.3.0 to 9.3.5

**Score:** 1

##### Agile PLM 9.2.x or older (including Agile Advantage)

**Score:** 0

#### How many custom process extensions (Java PX, Script PX, custom actions, custom autonumber sources) and event handlers do you run?

**Help:** In Java Client count the entries under Admin, Data Settings, Process Extensions and under Admin, System Settings, Event Management (Events, Event Handlers, Event Subscribers). None of this code runs in Fusion Cloud PLM; each one needs a redesign or retirement decision.

**Options:**

##### Fewer than 5, all documented

**Score:** 4

##### 5 to 20, mostly documented

**Score:** 3

##### 20 to 50, or poorly documented

**Score:** 1

##### More than 50, or nobody knows the full list

**Score:** 0

#### How does Agile PLM send items, BOMs and changes to your ERP?

**Help:** Typical paths: Agile Content Service (ACS) publishing aXML, Agile SDK or Web Services programs, the Design to Release integration pack built on AIA, or custom middleware.

**Options:**

##### No ERP integration, or a simple manual export

**Score:** 4

##### One documented integration (for example ACS to middleware to ERP)

**Score:** 3

##### AIA Design to Release pack or several custom SDK programs

**Score:** 1

##### Multiple undocumented integrations to several ERPs and MES

**Score:** 0

#### How heavily have you extended the class model (custom subclasses, Page Two and Page Three attributes, lists)?

**Help:** Check Admin, Data Settings, Classes. Every custom subclass and attribute needs a mapping to a cloud item class or extensible flexfield.

**Options:**

##### Out of the box classes, under 50 custom attributes

**Score:** 4

##### A few custom subclasses, 50 to 200 attributes

**Score:** 3

##### Many subclasses, 200 to 500 attributes

**Score:** 1

##### Over 500 custom attributes or many overlapping subclasses

**Score:** 0

#### How many active change workflows do you have, and how complex are their status criteria?

**Help:** Look at Admin, Workflow Settings, Workflows: count active workflows, statuses, entry and exit criteria and approver rules.

**Options:**

##### 1 to 3 workflows with simple criteria

**Score:** 4

##### 4 to 10 workflows, moderate criteria

**Score:** 3

##### More than 10 workflows or many criteria based routings

**Score:** 1

##### Workflows depend on PX code or event handlers to route

**Score:** 0

#### How large is the file vault, and how much do users depend on AutoVue viewing and markups?

**Help:** Measure the File Manager vault size on disk and the number of file folders. AutoVue markups stored with attachments need their own migration decision.

**Options:**

##### Under 500 GB, AutoVue not used or used for viewing only

**Score:** 4

##### 500 GB to 2 TB, some markups

**Score:** 3

##### 2 to 10 TB, markups used in change review

**Score:** 1

##### Over 10 TB or AutoVue markups are part of formal approvals

**Score:** 0

#### How good is the data in items, BOMs, manufacturers and changes?

**Help:** Think about duplicate parts, released items with blank key attributes, open changes stuck for years, and manufacturer parts with no AML link.

**Options:**

##### Clean: duplicates and stale changes are managed

**Score:** 4

##### Mostly clean, known pockets of bad data

**Score:** 3

##### Significant duplicates and abandoned changes

**Score:** 1

##### Unknown, never profiled

**Score:** 0

#### Which modules beyond Product Collaboration do you use?

**Help:** Product Quality Management (PQM), Product Governance and Compliance (PG&C), Product Portfolio Management (PPM) and Product Cost Management (PCM) each carry their own objects and data to map.

**Options:**

##### Product Collaboration only

**Score:** 4

##### PC plus one of PQM, PG&C, PPM or PCM

**Score:** 3

##### PC plus two or three other modules

**Score:** 1

##### Most modules, with PG&C compliance data or PPM projects in active use

**Score:** 0

#### What is the support status of the Oracle Database, WebLogic Server and operating system under Agile PLM?

**Help:** Check each component against the Oracle Lifetime Support Policy and the Agile PLM certification matrix on My Oracle Support.

**Options:**

##### All components on certified, supported releases

**Score:** 4

##### One component near the end of its support window

**Score:** 3

##### One component already out of Premier Support

**Score:** 1

##### Several components unsupported or uncertified

**Score:** 0

#### What skills does your team have with Oracle Fusion Cloud PLM and Product Hub?

**Help:** Cloud PLM uses item classes, extensible flexfields, change orders and approval rules configured through Setup and Maintenance, plus REST APIs and Oracle Integration rather than Java PX.

**Options:**

##### Trained team that has run a Cloud PLM pilot

**Score:** 4

##### Some training, no hands on project

**Score:** 3

##### Agile skills only, no cloud exposure

**Score:** 1

##### Agile knowledge sits with one person or a departed contractor

**Score:** 0

**Bands:**

#### High risk

**Min:** 0

**Max:** 39

**Verdict:** Your Agile PLM estate depends on code, integrations or people that would block a move. Stabilise and document before planning a migration date.

**Recommendations:**

- Check your release and every underlying component in the Oracle Lifetime Support Policy and plan to stay on Premier or Extended Support while you prepare.
- Export the full list of process extensions, event types, handlers and subscribers and record what each one does and who owns it.
- Document every ERP and MES integration end to end, including ACS destinations and SDK programs.
- Name a second person who can administer Agile PLM.

#### Significant work

**Min:** 40

**Max:** 59

**Verdict:** A move is feasible but customisation, data quality or module scope will drive most of the effort and risk.

**Recommendations:**

- Rationalise PX code: retire what users no longer need and map the rest to cloud configuration, approval rules or Oracle Integration flows.
- Run a data profiling pass on items, BOMs and AMLs and start cleansing duplicates and stale changes in Agile now.
- Decide per module (PQM, PG&C, PPM) whether it moves, is replaced or is archived.
- Size the vault and decide which file history must migrate and which can be archived read only.

#### Prepare

**Min:** 60

**Max:** 79

**Verdict:** Your estate is in reasonable shape. A structured preparation phase should close the remaining gaps before a migration project.

**Recommendations:**

- Map custom subclasses and attributes to cloud item classes and extensible flexfields.
- Simplify workflows to the routings the business actually uses.
- Train two people on Cloud PLM and run a pilot with a representative product family.
- Agree the cutover rule for open changes: complete in Agile or recreate in the cloud.

#### Ready

**Min:** 80

**Max:** 100

**Verdict:** Low customisation, clean data and a supported stack. You can plan a migration with confidence.

**Recommendations:**

- Freeze new PX and class changes in Agile PLM from the start of the project.
- Plan a trial migration with full data volumes and reconcile item, BOM and change counts.
- Rebuild the ERP integration on the cloud REST APIs or Oracle Integration and test it with real changes.
- Plan the read only retention period for the Agile PLM system after cutover.

## Content

**Intro:** This assessment scores how ready an Oracle Agile PLM 9.3.x estate is for a move to Oracle Fusion Cloud PLM, or for a longer stay on premises while you plan. It focuses on the things that actually drive effort: process extensions, event handlers, ERP integrations, class extensions, vault size and data quality.

**Sections:**

#### How to use it

**Body:** Answer the ten questions with the people who run Agile PLM day to day: the PLM administrator, whoever maintains the PX code, and the integration owner. Most answers come straight from Java Client: Admin, Data Settings, Classes for subclasses and attributes; Admin, Workflow Settings for workflows; Admin, Data Settings, Process Extensions and Admin, System Settings, Event Management for custom code. The score is a percentage of the maximum. Export the result to PDF and attach it to the business case or the support renewal discussion, because it shows where the money will go.

**Bullets:**

- Count, do not guess: export PX and event lists before answering.
- Answer for production, not your test instance.
- Re-run the assessment after each cleanup phase to show progress.

#### Why event handlers and PX code dominate the effort

**Body:** Agile PLM 9.3 has an Event Management framework: event types (for example create object, update title block, change status for workflow) fire event subscribers, which call event handlers such as Java PX or Groovy Script PX, synchronously or asynchronously, before or after the action. Older custom actions and custom autonumber sources are also Java PX. Fusion Cloud PLM does not run customer Java or Groovy on the server. Each handler has to be replaced by configuration (approval rules, item rules, extensible flexfields), by an Oracle Integration or REST based flow, or retired. That is why the PX count question carries the same weight as data quality.

#### Support status and end of life

**Body:** Do not plan around dates from blogs or forum posts. The Premier, Extended and Sustaining Support dates for Agile PLM releases, and for the Oracle Database and WebLogic Server releases underneath, are published in the Oracle Lifetime Support Policy documents for Applications and for Technology products. Check them for your exact release and then for the certified stack on My Oracle Support. Sustaining Support keeps access to existing patches and knowledge but no new fixes, so a stack that drops to Sustaining Support is a security and audit question, not only a PLM question. Use those dates as inputs to the plan this assessment produces.

#### Common mistakes

**Body:** Teams often treat the vault as a file copy and forget that attachments carry versions, file folder relationships and AutoVue markups. Another frequent problem is migrating every custom attribute because nobody can say which ones are used; profile attribute population first and drop empty ones. Agile Configuration Propagation (ACP) is a tool for moving configuration between Agile environments, not an integration to ERP, so do not count it as one. Finally, open changes are the hardest objects to move: decide early whether they finish in Agile PLM or are recreated in Cloud PLM.

**Cta:** If you want engineers to ask questions of your Agile PLM data, or of the archive you keep after migration, in plain English on your own servers, we can set that up.

**Faq:**

#### Is Oracle Agile PLM end of life?

**Answer:** Agile PLM 9.3.6 is the final 9.3.x release and Oracle's strategic PLM product is Fusion Cloud PLM. The exact Premier, Extended and Sustaining Support dates are set in the Oracle Lifetime Support Policy for Applications. Check the current version of that document for 9.3.6 rather than relying on dates quoted elsewhere.

#### What is event management in Oracle Agile PLM?

**Answer:** It is the framework in Agile PLM 9.3 that lets you react to system actions. You define an event for an event type and object type, attach an event subscriber with a trigger (pre or post, synchronous or asynchronous) and point it at an event handler, usually a Java PX or Groovy Script PX. It is the main place custom business logic lives.

#### Can Agile PLM process extensions run in Oracle Cloud PLM?

**Answer:** No. Fusion Cloud PLM does not host customer Java or Groovy code on the application server. Logic has to move to cloud configuration such as item rules, approval rules and extensible flexfields, or to external flows through Oracle Integration and the Cloud PLM REST APIs. Some PX code can simply be retired.

#### What should we do if we are not ready to migrate yet?

**Answer:** Stay on a supported Agile PLM 9.3.6 stack while you prepare. Use the time to inventory and rationalise PX code, profile and cleanse items and BOMs, document integrations, simplify workflows and train staff on Cloud PLM. Each of these lowers migration cost whenever the project starts.

## Search terms

oracle agile plm end of life, oracle agile plm cloud, oracle agile product lifecycle management plm, event management in oracle agile plm, oracle agile plm system, agile plm to fusion cloud plm migration, agile plm 9.3.6 support, agile plm process extensions migration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json