Migrate from ProjeQtOr to Trello

ProjeQtOr Projects map directly to Trello Boards. We extract project name, description, status, start date, and end date from the ProjeQtOr Project table and create a Trello Board per Project. The ProjeQtOr project status (template, planned, in-progress, finished, closed) maps to Board visibility and archived state in Trello. We set the Board description from ProjeQtOr's project description field. Multi-project portfolios in ProjeQtOr become multiple Trello Boards, which is the standard Trello organization pattern.

ProjeQtOr Tasks map to Trello Cards. We preserve task name, description, status, priority, planned work hours, and actual work from the ProjeQtOr Task table. Parent-child task hierarchies (WBS numbering) map to Trello Card hierarchy via a naming convention (e.g., parent card name with indented child names in the description) since Trello does not support native parent-card relationships. We also create checklist items for child tasks within the parent Card to preserve the WBS structure in a readable format.

ProjeQtOr Milestones map to Trello Cards on a dedicated Milestones List or Board. We set the Card name from the milestone name, the due date from the milestone target date, and apply a specific milestone label (created in Trello during migration) to distinguish milestone cards from regular task cards. Completed milestones get archived or moved to a Completed Milestones list. Standalone milestones without a parent task become Cards with the milestone label and no parent card association.

ProjeQtOr Resources (team members with calendar availability and cost rates) map to Trello Board Members. We extract resource name, email, and capacity settings from the ProjeQtOr Resource table and invite each as a Trello member. ProjeQtOr skill profiles and cost-rate fields have no Trello equivalent; we document these in a separate Skills and Rates inventory file delivered alongside the migration for the customer admin to reference outside Trello.

ProjeQtOr Resource Allocations bind a Resource to a Task with a start date, end date, and daily assignment percentage. We assign the corresponding Trello Card Member (the Resource) and create a checklist item with the allocation period and percentage. Planned hours from the allocation map to a planned-hours custom field on the Card (Standard plan and above). Multiple resources assigned to a single task produce multiple Card Members, matching Trello's multi-assignee model. We flag any resource allocations exceeding 100 percent in the same ProjeQtOr task as a conflict in the migration reconciliation report.

ProjeQtOr Expense records have no native Trello equivalent. Trello has no financial fields, cost amounts, VAT, or budget tracking. We create a Card per expense in a dedicated Expenses Board or list, storing expense category, amount, date, and project association in the Card description and custom fields. The customer should evaluate whether a dedicated expense-tracking Power-Up or a separate financial tool is required for ongoing expense management post-migration. This is a documented capability gap, not a data loss gap.

ProjeQtOr Risks include probability, impact, mitigation plan, and owner. Trello has no structured risk fields. We create Cards with a Risk label, storing probability as a number custom field, impact as a dropdown custom field, mitigation plan in the Card description, and owner as a Card Member. This is a mapping to the closest Trello primitive, not a structural equivalent. The customer should review whether a dedicated risk register Power-Up is needed for ongoing risk management.

ProjeQtOr Issues (bugs, incidents, change requests) map to Trello Cards with an Issue label. We extract issue type, priority, status, and description and create a Card per issue in a dedicated Issues list or board. Priority maps to Trello Card priority labels (e.g., P1, P2, P3). The customer should evaluate whether a dedicated bug-tracking Power-Up is required for software development teams managing issue workflows beyond simple labeled cards.

ProjeQtOr document records reference files stored on the application server filesystem. We locate each file in the ProjeQtOr document storage directory and upload it as an attachment to the corresponding migrated Trello Card using Trello's REST API. We preserve the original folder hierarchy as a reference in the Card description. File uploads use Trello's attachment endpoint with the file binary included in the request body. Cards with no matching file on disk are flagged in the reconciliation report with the file path reference for manual resolution.

ProjeQtOr Budget records track planned versus actual spending per project. Trello has no native financial or budget fields. We create a Budget Board with Cards representing budget line items, storing planned amount, actual amount, variance, and category in Card custom fields. The customer should evaluate a dedicated budget-tracking Power-Up or external financial tool for ongoing budget management. We deliver a written budget data inventory as a structured CSV so the customer's finance team can import into their preferred financial system.

ProjeQtOr Versions track product releases linked to a project with version name, number, status, and target date. We map these to Trello Cards with a Release label, storing version number, status, and target date in Card custom fields. If the customer uses a Trello Power-Up for release management, we document the recommended configuration and the version data inventory for manual migration into the Power-Up's data model.

ProjeQtOr stores custom fields in an EAV (Entity-Attribute-Value) table structure with object-type and ID references. We enumerate all custom field associations per object during discovery, flatten them into the destination custom field structure, and create the corresponding Trello Custom Fields (Standard plan and above) before importing Cards. ProjeQtOr custom fields that have no matching Trello custom field type (e.g., multi-select from a large value list) are merged into the Card description field and flagged in the custom field inventory delivered to the customer. Trello Custom Fields support checkboxes, dates, dropdowns, numbers, and text.

ProjeQtOr custom status workflows per object type define which statuses are available per project or object class. We read the ProjeQtOr workflow definition table during discovery and create a Trello List per status value on the target Board. Status ordering from ProjeQtOr maps to List ordering in Trello from left to right. We document any ProjeQtOr statuses that have no natural Trello equivalent (e.g., status values tied to approval workflows) as items requiring a manual rebuild decision post-migration.