Migrate from Oracle Project Management Cloud to Microsoft Project

Oracle Fusion PM Projects are the root entity with a Project identifier that every child object references. We export Projects via Oracle's REST API (fscmRestApi/resources/projects) and serialize them into Microsoft Project XML format for import. The Oracle Project name, Project number, status, start date, and finish date map directly to Microsoft Project project-level fields. Oracle Project classifications (Project Type, Investment Class) transfer as enterprise custom fields in Microsoft Project.

Oracle ProjectTasks form a Work Breakdown Structure under Projects using parent-child relationships exposed at /fscmRestApi/resources/{version}/projects/{projectId}/child/ProjectTasks. We preserve the WBS number and task outline level during export and reconstruct the Microsoft Project outline hierarchy using the WBS path. Task-level dates, durations, percent complete, and constraints map directly. Note that Oracle task types (Plan, Tracking, Administrative) do not have Microsoft Project equivalents and are dropped or noted in the handoff documentation.

Oracle Project Resources link people or equipment to Tasks with allocation percentages, assignment dates, and roles. We extract Resource records from /fscmRestApi/resources/{version}/projectResources and create Microsoft Project Resources with Name, Type (Work vs Material), Max Units, and Cost Rate. Resource Manager assignments from Oracle map to the Resource Notes field or a custom Resource custom field. Note that Oracle's role-based resource pool and capacity planning do not transfer; these require manual rebuild in Microsoft Project Resource Sheet.

Oracle resource-to-task assignments expose TaskId, ProjectResourceId, Planned Units, and Assignment Work. We map these to Microsoft Project Assignment records under each Task with Units (as a percentage of Max Units), Work (in hours or days based on project calendar), and Assignment Cost. The Oracle assignment status (Planned, Requested, Nominated, In Process) does not have a Microsoft Project equivalent and is preserved in a custom Assignment field for PMO reference.

Oracle TaskFollowers represent subscription-style notifications for specific tasks exposed at /child/TaskFollowers. Microsoft Project does not have a native follower or watcher concept. We capture the follower set and store it as a multi-value text custom field on the task record. The customer can use this to configure Power Automate notifications or distribute a follower list to PMs for manual follow-up after migration.

Oracle Expenditure Batches are cost transactions linked to Projects and Tasks with GL-accounting implications. Microsoft Project has no subledger or batch approval model. We split expenditure data: actual costs attributable to specific tasks map to task-level Cost fields in Microsoft Project (Work × Cost Rate), and aggregate batch totals map to project-level custom fields for reference. The approval state is not preserved — every batch requires review in the destination. We flag batch count and total cost value during scoping and recommend the customer allocate a post-migration review period.

Oracle Project Budgets are versioned financial plans stored in a planning cube with baseline and forecast variants at the Project level. Microsoft Project supports Baseline (single) and up to 10 interim baselines per project. We extract Oracle budget rows and create Microsoft Project baseline entries for each major cost category (Labor, Materials, Equipment, Indirect). Forecast variants map to interim baselines. Cost budgets above the task level require custom fields or a separate budget reference document since Microsoft Project does not have a native multi-version budget cube.

Oracle Project Contracts define billing terms, milestones, and revenue recognition rules as part of Project Contracts Cloud Service. Microsoft Project has no native contract billing or revenue recognition model. Contract header fields (Contract Number, Contract Type, Contract Amount) map to project-level custom fields. Milestone billing events map to Microsoft Project milestone tasks with the milestone date and a custom cost field carrying the billing amount. Revenue recognition schedules and AR invoice linkages do not migrate and are documented for the customer's finance team to recreate.

Oracle Project Billings capture AR invoice amounts linked to Projects and are stored as AR invoice records. Microsoft Project has no billing or accounts-receivable model. We extract billing header totals and map them to project-level custom fields (Total Invoiced, Last Invoice Date, Invoice Count). Invoice line details are not migrated; we provide a reference export for the customer's finance team to maintain outside the project plan.

Oracle extends standard objects with Descriptive Flexfields (DFFs) stored as key-value segments. We extract DFF values during export and map them to Microsoft Project enterprise custom fields by type: string DFFs map to Text fields, numeric DFFs map to Flag or Number fields, and date DFFs map to Date fields. We must apply the DFF schema to the destination environment before data import or custom values are silently dropped. Oracle Configuration Packages (the ZIP archives used to migrate DFF definitions between environments) do not apply to Microsoft Project; we document DFF segment names and values for manual custom field creation.