Migrate from Workfront to Trello

Workfront Portfolios have no direct Trello equivalent. We map each Workfront Portfolio to a Trello Workspace as a top-level grouping container. Workspace names and descriptions migrate. Workfront financial rollup data (planned revenue, budget) has no Trello destination and is included in the financial extract alongside Billing Records.

Workfront Programs group related Projects. Trello has no native Program object. We map each Program to a Trello Board, with a naming convention prefix (ProgramName-BoardName) to preserve hierarchy visibility. Programs without Projects are preserved as empty boards for the customer to populate.

Workfront Projects map 1:1 to Trello Boards. Project name becomes Board name, Project description migrates as the board description, and Project status (Current, On Hold, Complete, Dead) maps to a board label. Active projects become open boards; completed projects become archived boards. We extract project dates (planned start, projected completion) as card due dates on the first card of each board.

Workfront Tasks map to Trello Cards. Task name becomes Card title, task description becomes Card description, and task status maps to Card list position (To Do, Doing, Done). Assignments to Workfront Users map to Trello Board Members via email resolution. Priority in Workfront maps to Trello label color (red for high, orange for medium, green for low).

Workfront Subtasks inherit the parent Task schema and are stored as separate rows with a parentID reference. We flatten Subtasks into Checklist items on the parent Card, preserving the subtask name, assignee, and due date. If a Subtask itself has subtasks, we create a nested checklist within the checklist item using Trello's checklist-in-checklist structure via the API.

Workfront Users (active licensed users) map to Trello Members by email address. We extract user name, email, and primary Job Role as a Trello label on any cards assigned to that user. Inactive Workfront users are not migrated unless their historical task assignments are needed for data completeness; in that case they appear as card members without Trello login access.

Workfront custom fields (text, number, date, dropdown) are discovered via the Workfront API before migration. If the destination Trello workspace is on Standard or Premium, we map Workfront picklist custom fields to Trello Labels (creating label names from picklist values). For Standard/Premium workspaces with Power-Up custom fields enabled, we map typed fields (date, number, dropdown) to Trello Power-Up custom fields. Free-tier workspaces cannot use Power-Up custom fields; all custom field data becomes card descriptions or labels only.

Workfront Documents attach to Projects or Tasks and support versioning. We extract document metadata (file name, version, upload date, linked proof approval status) and download the file via the Workfront API. Each document becomes a card attachment in Trello. File content is uploaded directly to the Trello Card via the Trello API. Proof approval status is written into the card description as a text block since Trello has no native proofing layer.

Workfront Notes are conversation threads attached to Projects, Tasks, or other objects. Each Note (author, timestamp, rich text body) migrates as a Trello Card comment. We preserve the original author name and timestamp. Rich text converts to plain text with basic formatting preserved where Trello comment markdown allows.

Workfront Issues track blockers or change requests logged against a Project or Task. We map Issues to Trello Cards on the board that corresponds to the parent Project. Workfront Issue status (Open, Closed, On Hold) maps to list position. We add a label named 'Issue' to distinguish these cards from standard tasks. Request Queue intake data becomes card description text.

Workfront Approvals define a workflow of stages and approvers attached to Tasks, Projects, Documents, or Timesheets. Trello has no approval workflow record type. We extract approval status (Approved, Rejected, Pending) and associate it with the Card as a label (Approved, Rejected, Pending). The full approval history including approver, stage, and timestamp is written to a separate CSV export delivered alongside the migration.

Workfront Billing Records capture billable revenue against a Project. Once a Billing Record is marked Billed, Workfront permanently locks it and no edits are possible. We extract all Billing Records (including locked Billed records) before migration as a CSV financial extract with project name, billing record ID, amount, status, and date. This extract is delivered as a standalone file. Trello has no financial record type, so no Billing Record data migrates into Trello cards; the extract preserves it for the customer's finance team.