Migrate your workspace.pm data

Projects are the primary container in workspace.pm, holding all downstream objects. We map Project records 1:1 including status, dates, owner, and cost fields. Archived or completed projects are migrated with their status preserved unless the destination requires active records only.

Tasks sit under Projects and support standard fields: title, description, status, assignee, due date, priority. We preserve the task hierarchy where subtasks are defined and handle workspace.pm's status workflow values by mapping them to the destination's status vocabulary.

Subtasks are nested under Tasks. We flatten the hierarchy into the destination's native model — either native subtask structures or flattened task records with a parent reference — and preserve ordering within each parent.

Milestones are date-keyed project markers. We migrate Milestone name, target date, and associated project linkage. Where the destination uses a task-flag or label approach instead of a native milestone object, we replicate the date and name as a dedicated task record.

workspace.pm tracks predecessor-successor relationships between tasks. We capture these as dependency pairs and reconstruct them in the destination using that platform's native link mechanism, whether it is a dependency field, linking table, or external ID reference.

workspace.pm supports custom fields per project and potentially per task. We extract the full custom field schema including data type, picklist options, and values, then map them to the destination's custom field model. Picklist values require explicit value mapping if the destination uses a different enumerated set.

workspace.pm uses a Resource management layer to allocate team members to projects and tasks. We export the resource assignment records — user, role, allocation percentage, and dates — and map them to the destination's assignee or team membership model. Where the destination uses flat assignee fields only, we surface the allocation data as a custom field on the task.

Time tracking in workspace.pm captures logged hours against tasks or projects. We export the entry record: user, date, hours, and description. Mapping to the destination depends on whether the target has a native time-entry object or stores time as a numeric property on the task.

workspace.pm embeds discussion threads on tasks and possibly projects. We extract comment text, author, and timestamp. Where the destination has no native comment object, we attach comments as a text property or description append.

File attachments linked to tasks or projects are exported as URLs or file references depending on what workspace.pm's export exposes. We transfer attachment metadata — filename, uploader, upload date — and attempt to replicate the file link or re-upload to the destination storage.

workspace.pm's portfolio layer aggregates multiple projects for executive reporting. We export the portfolio-to-project associations and any portfolio-level custom fields. Since not all destination PM tools have a native portfolio object, we recreate the portfolio as a container project or tag group in the destination.

workspace.pm supports Kanban-style task views. These are presentation-layer configurations rather than data objects. We do not migrate board layouts, column definitions, or WIP limits as they are UI preferences that do not persist as exportable records.

Gantt chart visualizations are derived from task dates, dependencies, and milestones — not stored as independent objects. The underlying scheduling data is migrated as part of the task export; the Gantt view itself is recreated in the destination platform.

Dashboard reports and portfolio analytics are aggregate, read-only views generated from project and task data. We do not migrate dashboard configurations. The underlying data that powers the reports is available through the Projects and Tasks exports.