Rapid Migration of a Legacy System into Oracle Fusion Cloud Product Lifecycle Management

The objective of this use case is to migrate legacy-system data from a newly acquired company into Oracle Cloud Product Lifecycle Management (PLM), which is your single source of truth.

Description	Integration Type	Integration Options	Notes
Scenario 1: As a company, you've recently expanded by acquiring a new business. This business brings along a suite of legacy systems, such as Oracle E-Business Suite, that manage an extensive collection of item data, including details about product structures, catalogs, and associated attachments. Your objective is to migrate this data into Oracle Cloud PLM, which is your single source of truth. This scenario usually demands: Complex data preparation. Data transformation. Iterative data clean-up. Automated large-scale validation. Iterative performance tuning. Rapid cut over.	Inbound	Smart Spreadsheet File-based data import (FBDI) (recommended only for non Oracle Cloud PLM customers).	Web Services and Oracle Integration Cloud (OIC) aren't recommended for this use case.
Scenario 2: As a company, you're migrating from an on-premise Oracle Cloud PLM system, such as Oracle Agile PLM (A9 change controlled data) to Oracle Cloud PLM, which is managing an extensive collection of item data, including details such as Items, Item structures, associated attachments, redlines, revisions, and change-order information. Your objective is to migrate this data into Oracle Cloud PLM, which is your source of truth. This scenario usually demands: Complex data preparation. Data transformation. Iterative data clean-up. Automated large-scale validation. Iterative performance tuning. Rapid cut over. For more information, see Import Data Using FBDI.	Inbound	File-based data import (FBDI) for Item, Item Structure, Changes, Approved Manufacturer List (AML), and Attachments. Oracle Web Services for Item, Item Structure, and Change REST APIs.

Description

Integration Type

Integration Options

Notes

Scenario 1: As a company, you've recently expanded by acquiring a new business. This business brings along a suite of legacy systems, such as Oracle E-Business Suite, that manage an extensive collection of item data, including details about product structures, catalogs, and associated attachments. Your objective is to migrate this data into Oracle Cloud PLM, which is your single source of truth.

This scenario usually demands:

Complex data preparation.
Data transformation.
Iterative data clean-up.
Automated large-scale validation.
Iterative performance tuning.
Rapid cut over.

Inbound

Smart Spreadsheet
File-based data import (FBDI) (recommended only for non Oracle Cloud PLM customers).

Web Services and Oracle Integration Cloud (OIC) aren't recommended for this use case.

Scenario 2: As a company, you're migrating from an on-premise Oracle Cloud PLM system, such as Oracle Agile PLM (A9 change controlled data) to Oracle Cloud PLM, which is managing an extensive collection of item data, including details such as Items, Item structures, associated attachments, redlines, revisions, and change-order information. Your objective is to migrate this data into Oracle Cloud PLM, which is your source of truth.

This scenario usually demands:

Complex data preparation.
Data transformation.
Iterative data clean-up.
Automated large-scale validation.
Iterative performance tuning.
Rapid cut over.

For more information, see Import Data Using FBDI.

Inbound

File-based data import (FBDI) for Item, Item Structure, Changes, Approved Manufacturer List (AML), and Attachments.
Oracle Web Services for Item, Item Structure, and Change REST APIs.