Migrate from OpenProj to Trello

OpenProject Projects map to Trello Boards. The Project name becomes the Board name; Project description maps to the Board description or the first card pinned to the board as a summary. Members with roles map to Board members, though Trello has a simpler permission model (Admin, Member, Observer) without OpenProject's per-project role inheritance. We attempt email-matched member mapping; unmapped members are listed in a reconciliation card on the destination board.

OpenProject Work Packages map to Trello Cards. Subject maps to Card title; description maps to Card description; startDate maps to Card due date (or as a custom card field); dueDate maps to the due date picker. Assignee maps to Card member if a matching Trello user exists via email. Status is preserved as a Card label (using the status name as label text) and the Card position within its List reflects the status column where applicable. Priority and responsible fields map to additional labels or description notes.

OpenProject Types (Task, Feature, Bug, Milestone, Phase, Epic, and any custom types) map to Trello Labels. We create Labels on each destination Board with the exact type name as label text and a consistent color mapping derived from the source type. Trello limits labels to 25 characters; types exceeding this are truncated at 25 characters with a note in the migration report. Types without a matching Label on the destination board are created during migration.

OpenProject Statuses (New, In Progress, Closed, and custom statuses) map to Trello List positions within a board. We configure the destination board's Lists to match the most commonly used OpenProject status values per project. Cards are placed in the List matching their source status. Closed work packages are archived in Trello if the destination board has an Archive List configured. Status probability and workflow configuration do not migrate; Trello cards do not carry stage probability data.

OpenProject's parent-child Work Package hierarchy has no native Trello equivalent. Child Work Packages are created as separate Cards on the destination board, and the parent-child relationship is documented in each child's Card description as a reference link (parent Card ID or name). For branches of up to 10 children, we optionally create Checklist items on the parent Card pointing to child Card links. This is a documentation pattern, not a structural hierarchy, since Trello does not enforce parent-child rules.

OpenProject time entries (hours, rate, cost, spent-date, comment) cannot map to any native Trello field. We encode each time entry as a structured text block in the Card description with format 'Logged: Xh on YYYY-MM-DD — comment'. For migrations in scope, we ask the customer to select the Trello Power-Up (Toggl Track, Clockify, or Planyo) they will adopt post-migration and we configure time entry descriptions to match that Power-Up's expected input format so manual re-entry is minimised. Time entries are not deleted; they are preserved in the migration record for the customer's admin to import into the selected Power-Up.

OpenProject Versions (sprints, milestones, releases) map to Trello Labels with a version-name prefix (e.g., 'v2.1', 'Sprint 14', 'Release Q3'). Version status (open, locked, closed) is noted in the Label description field. Version date (effectiveDate) is preserved in the Card description for milestone versions. Versions are not enforced as a scoping mechanism in Trello; they are informational labels on cards.

Files attached to OpenProject Work Packages migrate as Card attachments in Trello. OpenProject's API limits file link creation to 20 elements per request; we pre-scan the source to identify Work Packages exceeding this threshold and batch them into safe chunks. File metadata (filename, author, created-at) is preserved in the attachment record. Trello Free caps attachments at 10 MB per file; we flag files exceeding this limit and upload them to a Google Drive or SharePoint folder with a link substituted in the Card.

OpenProject Wiki Pages belong to a project and support Markdown content. Trello has no native wiki equivalent. We convert each wiki page to a PDF or Markdown file and attach it to a summary Card on the destination board. Card description includes the page title, project name, and a note that the full content is in the attached file. Hyperlinks within wiki pages are preserved if the target exists on the destination board; external links are kept as-is.

OpenProject Meetings (title, date, duration, location, attendees, minutes text) have no Trello equivalent. We create a Card per meeting with the meeting title, date, duration, and attendee list in the Card description. Meeting minutes in Markdown are attached as a PDF to the Card. The meeting Card is placed in a dedicated 'Meetings' List on the board if the destination board has one, otherwise in the first List.

OpenProject Documents (project-scoped files with descriptions) map to Card attachments on a summary Card for the project, or to individual Cards with the document name as the title and the description preserved. Document folder hierarchy is not maintained in Trello; we document the original path in the Card description. Documents are the most attachment-heavy object in OpenProject and may require the Trello attachment size fallback (Google Drive link substitution) if file sizes exceed the 10 MB limit.

OpenProject Cost module data (budget, labour costs, unit costs) has no Trello equivalent at any tier. We document the full budget and cost entry summary in a dedicated Card per project titled 'Budget Summary — do not archive', with the estimated budget, actuals, and variance encoded as a structured table in the Card description. This is a read-only reference record; Trello does not support cost tracking or financial fields. The customer may link this card to a financial tracking tool via Power-Up or external URL.