Migrate from Oracle Project Management Cloud to Trello

Each Oracle Project migrates to a Trello Board. Oracle's project identifier becomes the board name prefix (for example, PRJ-1234 Project Name) so that the original Oracle reference is preserved. Oracle's project status (Active, On Hold, Closed) maps to Trello board visibility settings and an archived-card strategy: Closed projects become archived boards or board labels. Project classification categories migrate as Board Labels so PM leads can filter by program or business unit within Trello's filter view. Note that Trello board creation via API requires a Standard tier or above on the destination Trello workspace.

Oracle Project Tasks with a WBS (Work Breakdown Structure) hierarchy migrate as Trello Cards. The Oracle parent task relationship maps to card hierarchy through a parent-card reference: we create a primary Card for the parent task and link child tasks as either Checklist items (for flat sub-tasks) or as separate Cards linked via a Trello Power-Up (such as Cards for Hierarchy or Hierarchy for Trello) if the destination workspace has that Power-Up enabled. Oracle task dates map to Trello Card due dates; task progress percentage maps to a Checklist progress custom field. Task description migrates as the Card description. We flag the depth of the WBS during scoping because Trello natively supports only two levels (card and checklist item) without a hierarchy Power-Up.

Oracle Project Resources linked to Tasks migrate as Trello Card Members. We extract the resource person's name or role from Oracle's Resource assignments, match by email against Trello workspace members, and add each matched user as a member on the corresponding Card. Role labels (for example, 'Lead Developer', 'QA Engineer') migrate as Card Labels. Oracle resource allocation percentage (for example, 50% on a given task) is noted in the Card description because Trello does not support allocation percentage natively. Resource capacity and utilization metrics have no equivalent in Trello and are excluded from migration scope.

Oracle Task Followers (subscription-style notifications on tasks) migrate to Trello Card Watchers if the destination workspace uses a Power-Up that supports watch functionality, or as Card Members added in read-only context. Most destination Trello workspaces do not natively support the follower-watcher model; we document the original follower set in the task record description so that the PM lead can manually assign watchers post-migration.

Oracle Expenditure Batches contain cost transactions tied to project costing and GL entries. Trello has no financial model and cannot represent cost line items. We do not migrate Expenditure Batches as data records. Instead, we deliver a written inventory of all Oracle Expenditure Batch headers and line counts, flagging the total count and total cost value, so the customer's finance team can export to a spreadsheet and maintain outside Trello. This is a fundamental capability gap, not a mapping limitation.

Oracle Project Budgets store versioned financial plans (baseline, forecast) at the project level with planning cube rows. Trello has no budget, cost, or financial field at the board level. We extract Oracle budget row summaries (total budget amount, version, fiscal period) and document them in a reference report delivered alongside the migration. We do not migrate budget line items as Trello records. This is a capability gap that the customer's PM and finance leads must address with a separate budgeting tool or spreadsheet post-migration.

Oracle Project Contracts define billing terms, milestones, revenue recognition rules, and AR invoice generation. Trello's card model cannot represent contract terms, billing schedules, or revenue recognition. We deliver a written inventory of Oracle Contract headers and milestone summaries (contract number, client name, total contract value, milestone dates) as a reference document. The customer's contracts team should manage this data in a dedicated contract lifecycle management tool or CRM post-migration.

Oracle Project Billings represent invoiced amounts against Project Contracts stored as AR invoices linked to Projects. Trello has no invoice, billing, or accounts receivable model. We do not migrate billing records. The customer's finance team should manage AR data in an ERP or accounting system post-migration. We document the count of billing records per project in the reference inventory for audit purposes.

Oracle Descriptive Flexfields (DFFs) with key-value segment data attached to Projects and Tasks migrate to Trello Custom Fields if the destination workspace is on Trello Premium ($10/user/month) enabling the Custom Fields Power-Up. We extract DFF segment values at export time, match each segment to a Trello Custom Field by name and data type (text, number, date, dropdown), and attach values to the corresponding Cards and Boards. If the destination workspace is on Free or Standard tier, DFF values are documented in a separate reference report and the customer's admin creates equivalent custom fields manually post-migration.

Oracle Project Attachments stored in Oracle Content and Experience (OCEC) or FBL file storage download to a staging location and are re-uploaded as Card Attachments on the corresponding Trello Cards. We preserve the original filename and a reference link back to the Oracle document ID in the Card description. Attachments that exceed Trello's 10MB per file limit are flagged during scoping and uploaded to the customer's Google Drive, Dropbox, or SharePoint with the share link embedded in the Card description. Trello Business Class or Premium is required for Power-Up attachments beyond the standard 10MB limit.

Oracle Configuration Packages (ZIP archives of setup XML including lookups, profile options, flexfield definitions, and workflow rules) are not applicable to Trello. Trello does not have a setup-data or configuration-package model. We document the DFF segment definitions and lookup values in a written reference document for the customer's admin to configure as Trello Custom Fields and Labels post-migration. Workflow rules from Configuration Packages are documented separately in the Workflow inventory.

Oracle Project approval and notification workflows built on BPM Worklist (approval hierarchies, expenditure batch approval, task notification rules) have no equivalent in Trello. Trello's native Automations (Butler) support trigger-action rules such as moving cards on due date or adding members on card creation, but do not support multi-level approval chains, conditional branching based on financial thresholds, or GL posting triggers. We deliver a written inventory of every active Oracle workflow with its trigger, conditions, approver hierarchy, and downstream action, plus a Trello Butler or third-party automation recommendation for each. The customer's admin rebuilds these post-migration.