Migrate from workspace.pm to Trello

workspace.pm Projects map directly to Trello Boards. We preserve Project name, description, start and target dates (as Board background date markers), status, and cost fields where relevant. Active and archived Projects map to open and archived Boards respectively. The Board is the parent container for all downstream List and Card records.

workspace.pm Tasks map to Trello Cards under their corresponding Board. Title, description, status (mapped to List placement), assignee (mapped to Trello member), due date (Card due date field), and priority (mapped to Label color or Custom Field) transfer. Cards with a single List on a Board are straightforward; cards that need to appear in multiple Lists require cross-board linking documented for the customer's admin.

workspace.pm Subtasks map to Trello Checklist items attached to the parent Card. We preserve the subtask title, completion status (checked vs unchecked), and ordering sequence. Trello supports multiple Checklists per Card which maps to nested subtask groups in workspace.pm. Ordering is maintained by processing subtasks in sequence during card creation.

workspace.pm Milestones have no native Trello equivalent. We reconstruct them as color-coded Labels (e.g., a dedicated 'Milestones' label group with per-milestone label names) and optionally attach a due date to milestone Cards to preserve the date anchor. The customer chooses the label naming convention during scoping. Milestone-to-project linkage is preserved by ensuring milestone Cards sit on the correct Board.

workspace.pm predecessor-successor task dependencies have no native Trello link mechanism. We capture dependency pairs during extraction and store them as a 'Blocked By' or 'Blocking' Custom Field on each affected Card (text type, holding the linked Card name or URL), or as a card-label dependency tag. We deliver a dependency map document listing every affected Card pair for the customer to implement Trello's native card-linking manually or via Butler automation.

workspace.pm Custom Fields (at project and task level) map to Trello Custom Fields with type translation: text, number, and date types migrate directly. Multi-select picklists migrate to Trello Dropdown type with the options preserved. Currency and percentage types have no Trello equivalent and migrate as Text fields with a notation in the mapping spec. We request the full workspace.pm custom field schema before migration to pre-create Custom Fields on each destination Board. Fields must be created per-Board in Trello; there is no global Custom Field definition.

workspace.pm Resource allocation records (user, project assignment, role, allocation percentage, dates) map to Trello Members. We extract the assignee from each task record and add the Trello member by email match. The allocation percentage and role store as Custom Fields on the Card since Trello Members do not carry allocation metadata. Unmatched users go to a reconciliation queue for the customer's admin to provision before migration.

workspace.pm time entries (hours, user, date, description) have no native Trello object. We store them as a 'Time Logged' Custom Field (number type) on the Card, with the most recent entry or a summed total depending on whether the customer requests summary or detailed migration. Trello time-tracking Power-Ups are a post-migration admin decision; we document the recommended setup. Entries are also captured in a time_log audit CSV for reference.

workspace.pm task comments migrate to Trello Card Comments preserving comment text, author, and timestamp. Rich text in comments migrates as plain text with formatting stripped. Comments on Projects migrate to Board description or a pinned Card as the most equivalent location. Trello's comment threading is flat, so any nested comment structures from workspace.pm flatten.

File attachments linked to workspace.pm tasks or projects migrate as Trello Card Attachments. We extract attachment metadata (filename, uploader, upload date) and the file reference URL. The file itself is downloaded and re-uploaded to Trello if workspace.pm's export includes the file content, or the URL is preserved as a link attachment if content transfer is not possible. Attachment migration for large files requires Trello Premium for >10MB per file.

workspace.pm portfolios aggregate multiple projects and have no native Trello equivalent. We extract portfolio-to-project associations during the pre-migration audit and reconstruct them in Trello as a Board-naming prefix convention (e.g., 'PortfolioName > ProjectName' Board name), a dedicated Label group for portfolio tagging, or a written board-grouping plan the customer's admin implements. Portfolio-level custom fields store as Board-level Custom Fields or in a board description field.

workspace.pm Gantt chart visualizations are derived from task dates, dependencies, and milestones — not stored as independent data objects. We do not migrate Gantt configurations. The underlying task scheduling data (start dates, end dates, dependencies) migrates as part of the task export; the Gantt visual is reconstructed by the customer's admin in Trello using a Timeline Power-Up or calendar-based view if required.