Migrate from Workfront to monday Work Management

Workfront Portfolios group Programs for top-level financial and progress reporting. monday.com has no native portfolio object—Workspaces are the top-level container but lack portfolio-level rollup reporting. We map Portfolios to Workspaces and flag the loss of cross-program financial aggregation. Customers requiring portfolio visibility in monday.com typically implement a dedicated Portfolio board with linked Items or use monday.com's reporting views across boards.

Workfront Programs group related Projects under a Portfolio and carry Program-level dates and progress. We map Programs to monday.com Boards, preserving the Program name as the Board name and the Program status as a Status column. Program-level custom fields migrate as Board-level columns if the Program is the highest entity; if Programs nest within a Portfolio, we add a Program column to the Board Items to preserve the grouping context.

Workfront Projects are the primary work container and map to monday.com Boards or Groups depending on the customer's board strategy. If the customer prefers one Board per Project, we create individual Boards with Project metadata (dates, status, priority, portfolio assignment) stored as columns. If the customer uses a Program-level Board with Groups per Project, we create Groups and preserve the Project name, dates, and status within the Group structure. Workfront project templates generate Board templates in monday.com.

Workfront Tasks map to monday.com Items on the target Board. Standard Workfront task fields (name, description, status, priority, planned dates, actual dates, percent complete, planned hours) map to monday.com column types: Status for status, Priority for priority labels, Date for start/end dates, Numbers for hours, and Formula or Numbers for percent complete. Assignments to Users migrate to monday.com Person columns; assignments to Job Roles migrate to a Dropdown column with a note that the Role-to-User mapping requires admin review post-migration.

Workfront Subtasks are child Tasks stored as separate rows with a parentID reference. monday.com Subitems (Pro+ tier) attach as a nested item under a parent Item. We extract Workfront Subtask rows, resolve the parent Task reference, and create monday.com Subitems linked to the parent Item. Subitem column types mirror the parent Item schema. Note: Subitems are only available on monday.com Pro and Enterprise plans; we confirm the destination plan tier during scoping.

Workfront custom fields (text, number, date, currency, dropdown, checkbox, user, role) map to the closest monday.com column type: Text to Text, numbers to Numbers, dates to Date, currency to Numbers with a label, picklist to Dropdown or Status, checkbox to Checkbox, and user references to Person. Multi-select picklists in Workfront map to multi-select Dropdown columns in monday.com. We discover the full custom field schema via the Workfront API before migration and generate a column creation manifest for the monday.com destination.

Workfront Users map to monday.com workspace Members. We resolve by email match across both systems. Job Roles (billing-rate-carrying role assignments in Workfront) have no direct monday.com equivalent—we preserve role assignments as a Dropdown column on Items and recommend the customer assigns role-carrying users manually in monday.com's Workload view post-migration. Inactive Workfront users are not invited to monday.com but are noted in the user mapping manifest.

Workfront Documents attach to Projects, Tasks, or Issues and support versioning. We extract document file content via the Workfront API and upload to monday.com as file attachments on the corresponding Items. Document versions become multiple file attachments with version labels. Proof approval status (Approved, Rejected, Pending) is extracted and stored as a Status column on the Item. monday.com does not support document proofing workflows—review cycles must be recreated using monday.com's native commenting and @-mentioning or a third-party document review integration.

Workfront Approvals attach to Tasks, Projects, Documents, or Timesheets and define multi-stage approver workflows. monday.com has no native approval routing or approval object. We extract approval status (Pending, Approved, Rejected) and approval history (approver, timestamp, comments) and store it as a read-only Status column on the migrated Item. We deliver a written approval reconstruction guide that maps each Workfront approval stage to a monday.com workflow step (Status column update or automation trigger) that the customer's admin rebuilds post-migration.

Workfront Notes are conversation threads attached to Projects, Tasks, or other objects with author, timestamp, and rich text content. We extract the full note history and insert as monday.com Updates on the corresponding Item, preserving the author name, timestamp, and rich text body. Images embedded in Workfront notes are extracted as separate file references. Updates are inserted in chronological order.

Workfront Issues track blockers or change requests logged against a Project or Task and appear in Request Queues as public intake forms. We map Issues to monday.com Items with a status column reflecting the Issue status (Open, On Hold, Closed). Request Queue metadata (queue name, request type) migrates as an additional Dropdown column. Intake form custom fields migrate as columns on the Issue Items.

Workfront Timesheets record hours logged against Tasks or Projects, associated with a User and date range. monday.com's Time Tracking column (available on Pro+ plans) logs hours per Item per User. We extract timesheet entries and create Time Tracking records on the corresponding Items in monday.com. The original billing rate from Workfront Job Roles does not migrate; the customer sets billing rates manually in monday.com or uses a separate billing integration.

Workfront Project Templates define reusable project structures including tasks, assignments, and default custom field values. We extract the template structure (task hierarchy, default assignments, default custom field values) and recreate it as a monday.com Board Template. Task-level template steps become Groups or recurring Items in the template. Template-level custom field defaults map to column defaults in monday.com.