Migrate your Oracle Project Management Cloud data

Projects are the root entity in Oracle Fusion PM. Every other object (Tasks, Expenditures, Budgets, Contracts) carries a Project identifier as a foreign key. We migrate Projects with their classification, status, dates, and owner assignments. Custom Project attributes are supported via mapping when the attribute schema is captured during discovery.

Tasks form a hierarchy under Projects with WBS (Work Breakdown Structure) relationships. Oracle's REST API exposes /fscmRestApi/resources/{version}/projects/{projectId}/child/ProjectTasks. We preserve the hierarchy and dependencies during migration. Task-level baselines are migrated as a separate payload since they are stored as distinct objects.

Resources link people or equipment to Tasks and Projects with assignment dates, allocation percentages, and roles. We map Resources to the destination system's resource pool. Note that Resource Manager data lives in a separate module within Fusion and may require a separate export scope.

Task Followers represent subscription-style notifications for specific tasks. The REST endpoint is /child/TaskFollowers under ProjectTasks. We preserve the follower set but note that most destination systems handle notifications differently; we map Followers to a custom property or notification tag on the equivalent Task record.

Expenditure Batches are cost transactions imported from subledgers and third-party systems. They require a Requires expenditure batch approval workflow step in Project Costing before they commit to the financial record. We migrate the batch headers and line items, but the approval state resets and must be re-completed in the target environment. Batch naming conventions and transaction source mappings must be carried forward.

Budgets are versioned financial plans at the Project level with baseline and forecast variants. Oracle stores budgets in a dedicated planning cube. We extract budget rows and recreate them in the destination, noting that budget vs. forecast comparisons are schema-dependent on the target system's financial model.

Project Contracts define billing terms, milestones, and revenue recognition rules. They are part of Project Contracts Cloud Service and carry complex billing schedules. We migrate contract headers and line items, but revenue recognition configurations typically require re-setup in the destination as they are governed by accounting rules.

Billings capture invoiced amounts against Project Contracts. Oracle stores billings as AR invoices linked to Projects. We migrate billing headers; line-level invoice details are migrated separately as Invoice objects. Customer and party mappings are critical here to ensure billing addresses and tax configurations are correctly resolved.

Oracle Fusion extends standard objects with Descriptive Flexfields (DFFs). These are defined at the segment level and stored as key-value pairs. We extract DFF values during export and map them to equivalent custom fields in the destination. Flexfield definition metadata must be migrated first so that the target schema can accept the values.

Attachments are stored in Oracle Content and Experience (OCEC) or as FBL (File Storage) entries. We download attachments to a staging location and re-upload them to the destination's document management system, preserving folder hierarchies where supported. Filename and MIME type metadata is preserved in a manifest file.

Oracle uses Configuration Packages (ZIP archives of setup XML) to migrate lookups, profile options, flexfields, and workflow rules between environments. We can extract and re-apply Configuration Packages as part of a full environment migration. Note that edition gating may cause some objects to be unavailable in lower-tier environments.

Project approval and notification workflows in Fusion PM are built on BPM Worklist. Workflow rules, approval hierarchies, and assignment configurations are stored as workflow definitions. We document the workflow configuration as part of migration scoping; complex workflow re-implementation typically requires a consultant review in the destination environment.