Migrate from Oracle Project Management Cloud to monday Work Management

Oracle Projects are the root entity in Fusion PM — every child object (Task, Resource, Budget, Contract) carries a Project identifier as a foreign key. We migrate Projects to monday.com Boards with the project name as the Board title, project status mapped to Board Group status columns (Active, On Hold, Closed), and project classification codes mapped to custom Board columns. Oracle's project number becomes a text column for external reference. Projects are migrated first so that every child record can resolve its parent Board during item import.

Oracle Project Tasks form a WBS (Work Breakdown Structure) hierarchy under Projects. We map the hierarchy to monday.com Subitems under Items within Board Groups. The task name becomes the Item name, task start and finish dates map to Date columns, and WBS level maps to Item depth in the Subitem hierarchy. Milestone tasks in Oracle map to a Status column set to Milestone value. Dependencies from Oracle (task-to-task predecessor links) map to the monday.com Dependencies integration column, or are documented as a manual rebuild step if the customer's Oracle dependencies are complex multi-path chains.

Oracle Resources link people or equipment to Tasks and Projects with assignment dates, allocation percentages, and roles. We map Resources to monday.com Person columns on Items and to the Workload view for capacity visibility. Oracle role assignments (Project Manager, Business Analyst, Developer) map to a multi-select Person column or a separate dropdown column for role tracking. Oracle's allocation percentage becomes a Number column; actual hours assignments map to a Number column with a formula for hour tracking. Note that monday.com has no native capacity leveling engine — capacity planning requires the Workload view plus manual rebalancing.

Oracle Task Followers represent subscription-style notifications for specific tasks. The REST endpoint is /child/TaskFollowers under ProjectTasks. We map Followers to monday.com Item Subscribers, preserving the follower set per Item. Note that monday.com subscriber access is view-only on the specific Item — there is no team-wide notification subscription model equivalent to Oracle's BPM Worklist notifications.

Oracle Expenditure Batches are cost transactions imported from subledgers and third-party systems. They carry a Requires Expenditure Batch Approval workflow step in Project Costing before committing to the financial record. monday.com has no financial schema, no expenditure tracking columns, and no approval routing for cost batches. We do not migrate Expenditure Batches. We deliver a written inventory of every Oracle Expenditure Batch with its total cost, date range, and approval status so the customer's finance team can re-create these in their chosen financial system (QuickBooks, NetSuite, Sage) or as a manual monday.com file column reference.

Oracle Project Budgets are versioned financial plans at the Project level with baseline and forecast variants stored in a dedicated planning cube. We extract budget rows and create Number columns on the monday.com Board for baseline and current forecast values. However, monday.com has no native budget variance calculation engine, no rollup to a portfolio budget, and no GL-linked cost capture. We flag the budget migration as informational-only and recommend the customer configure a third-party financial integration (for example, a Fyle or Airbase integration) for ongoing budget management post-migration.

Oracle Project Contracts define billing terms, milestones, and revenue recognition rules as part of Project Contracts Cloud Service with complex billing schedules. monday.com has no native contract management schema. We migrate contract header data (contract name, counterparty, total contract value, billing milestones as separate Items in the Board) and flag the revenue recognition rules as requiring manual re-documentation. The customer should retain the Oracle contract PDF in monday.com as a File column attachment or link to an external document store.

Oracle Project Billings capture invoiced amounts against Project Contracts as AR invoices linked to Projects. monday.com has no AR or invoicing capability. We do not migrate Billings. We deliver a written inventory of Oracle billing headers (invoice number, date, amount, status) so the customer's finance team can re-enter or import them into their accounting system. Historical billing data should be retained in Oracle as read-only archival or exported to a financial data warehouse.

Oracle Fusion extends standard objects with Descriptive Flexfields (DFFs) — setup-defined key-value segments stored as key-value pairs. We extract DFF values during export and map them to monday.com Custom Columns. Text DFFs map to Text columns, numeric DFFs to Number columns, date DFFs to Date columns, and list DFFs to Dropdown or Status columns. The customer must pre-create the custom columns in monday.com before migration because columns cannot be created via bulk import in the same pass as item data. We sequence the column creation step before the item migration run.

Oracle Attachments are stored in Oracle Content and Experience (OCEC) or as FBL (File Storage) entries. We download attachments to a local staging location during extraction, then upload them to monday.com File columns on the relevant Items. For very large files (over 100 MB) or file types that monday.com does not render inline (CAD files, large PDFs), we upload to a customer-provided cloud storage location and store the URL in a Link column on the Item. Oracle Content and Experience URLs are not valid post-migration and must be replaced with monday.com-hosted or customer-hosted URLs.

Oracle Configuration Packages (ZIP archives of setup XML) migrate lookups, profile options, flexfields, and workflow rules between Oracle environments. monday.com has no equivalent setup data export or import mechanism. We do not migrate Configuration Packages. We document the DFF segment definitions, lookup codes, and profile options from the Oracle configuration as a written setup guide so the customer's monday.com admin can recreate the equivalent custom columns, dropdown values, and integrations manually. Oracle edition-gated objects (objects valid in full ERP but not standalone PM) are specifically noted for manual handling.

Oracle Project approval and notification workflows are built on BPM Worklist with workflow definitions stored separately from project data. monday.com Automations are trigger-action recipes scoped to a single Board with different trigger types, action types, and conditional logic. We do not migrate BPM workflows as code. We deliver a written inventory of every active Oracle BPM workflow with its trigger, approver hierarchy, conditions, and routing path, plus a recommended monday.com Automation equivalent using Board-level triggers (When Status Changes, When Date Arrives, When Someone Joins) and actions (Change Status, Assign Person, Send Notification). The customer's admin rebuilds automations in monday.com post-migration.