Migrate from OpenProject to Trello

OpenProject Projects map 1:1 to Trello Boards. Each OpenProject Project's activated Modules determine which Trello Lists to create on the target Board (e.g., a project with the Agile module active creates Lists corresponding to the project's Status workflow). We preserve the OpenProject project identifier and description in the Board description field. Projects with no Work Packages still create an empty Board with the project name and description.

OpenProject Work Packages map to Trello Cards. The Work Package Type (Task, Bug, Feature, Phase) maps to a Card label in Trello so that type distinctions are visible at a glance. Assignee maps to Trello Card members. Start Date and Due Date map to the Card due date. Description migrates as the Card description with OpenProject wiki markup stripped to plain text. Priority, Responsible, and estimated hours migrate as Card labels or description fields.

OpenProject Work Packages with a parent-child relationship decompose as follows: the parent Work Package becomes a Card; each child Work Package becomes a Checklist Item on that Card with its own due date and assignee preserved in the checklist item text. This flattens OpenProject's multi-level hierarchy into Trello's single-level card-with-checklists model. Teams requiring full hierarchical visibility in Trello add a Power-Up (such as Tree视图) or restructure into separate Cards linked via card-linking Power-Ups.

OpenProject Versions (milestones or sprints) map to Trello Lists on the Board. Version name becomes the List name. Version target date can be stored in the List description or as a Card label on a release-tracking Card. If the OpenProject project uses a Version-based board view, we create Lists per Version and distribute Work Packages by their Version assignment.

OpenProject custom fields have no native Trello equivalent. We map text and number custom fields to Card description appends (custom field name: value format) or to the Custom Fields Power-Up if the destination Trello workspace has it enabled. Multi-select list custom fields map to Trello Labels with the label color representing the custom field category. Date custom fields map to the Card due date if no native date field exists or are appended to the description if the Card already has a due date. The custom field inventory is delivered as a written mapping table for the customer's admin to configure in the Custom Fields Power-Up.

OpenProject time entries have no Trello equivalent—Trello has no native time tracking or cost reporting. We convert total logged hours per Work Package into a Card description entry (Total logged: X hours) or, if the customer has a time-tracking Power-Up installed, we map to that Power-Up's structure. We flag this discrepancy during discovery and the customer chooses the conversion strategy before migration. No cost entry migration is attempted as Trello has no cost model.

OpenProject attachments (on Work Packages, Wiki pages, Documents) migrate as Trello Card attachments if under Trello's 10 MB per-file limit. Files larger than 10 MB are flagged in the migration report with file name, size, and source URL; the customer's admin handles out-of-band transfer via Dropbox, Google Drive, or S3. We preserve the original file name and attachment URL in the Card description for traceability. Attachment comments and version history do not migrate.

OpenProject Wiki pages store formatted content and can embed work package lists. We extract wiki page text content, strip formatting to plain text, and create a pinned Card on the Board titled 'Project Wiki: [Page Name]' with the content in the Card description. Cross-document work package references are preserved as plain text links in the Card description. Full wiki structure (section hierarchy, image embeds) does not migrate; images are treated as attachments and follow the attachment migration path.

OpenProject Forums and their Messages have no Trello equivalent. We migrate Forum content as a dedicated Card titled 'Forum Archive: [Forum Name]' with thread content in the Card description (oldest first, newest last), including author, timestamp, and message text. Long threads are split across multiple Cards if the character count exceeds Trello's description limits. Forum permissions do not migrate; Board permissions handle access control in Trello.

OpenProject Documents (project-level file containers with title, description, and attached files) map to a Card titled 'Document: [Title]' with the document description and files attached. If the document has no files, the description alone migrates. Documents without an associated Work Package are attached to a project-level Card.

OpenProject Users map to Trello Workspace members by email address. We match on email; any OpenProject User without a matching Trello workspace member goes to a reconciliation queue for the customer's admin to provision accounts before migration. Admin status from OpenProject does not map to Trello roles; Board-level permissions handle access control in Trello.

OpenProject Members with Roles per project map to Trello Board members. Role names (Project Admin, Member, Viewer) are preserved in the Board member invitation as a note so the customer's admin can configure equivalent Trello permission levels (Admin, Normal, Observer) after migration. OpenProject's global roles do not map directly to Trello.