Migrate from Twproject to Trello

Each Twproject project becomes a Trello board. We create the board in the target workspace, set visibility (public or private), and import the project name, description, start date, and target end date as board metadata. Trello's board-level metadata fields are limited compared to Twproject's project detail view, so dates migrate as card due dates or as a pinned board description note. Multi-phase projects in Twproject map to multiple Trello lists within the board (see Phase/List mapping below). Teams should decide on a board-naming convention and workspace assignment before migration begins.

Twproject's hierarchical project structure (project > phase > sub-phase > task) has no direct Trello equivalent. Trello supports only two levels: Board > List > Card. We flatten the hierarchy by mapping the top-level Twproject phase to a Trello List, and any nested sub-phases are handled as either additional Lists within the same board or as Card labels to preserve the original hierarchy signal. We document the original WBS path as a card label or as the first line of the card description during scoping so the admin can decide on the best flattening approach for their team.

Twproject tasks map directly to Trello cards. We preserve the task name as the card title, description as the card description (rich text), due date as the card due date, priority from Twproject's urgency field as a Trello Label (color-coded), and assignee as the card member. Twproject's parent-child subtask relationship maps to Trello checklist items within the parent card rather than as separate cards — this preserves the hierarchy within the card boundary while keeping the board flat. Task status in Twproject maps to the card's current list position or to a dedicated Done/Closed list.

Twproject Resources (user accounts with allocation and cost rate metadata) map to Trello workspace Members. We resolve by email match and map the user's Twproject display name to the Trello full name. Cost rate data from Twproject has no Trello native equivalent — we document it as a custom card field (if Business Class is purchased) or as a note in the card description. We also flag any Twproject Resource without a corresponding Trello account to the customer's admin for member provisioning before the card migration phase begins.

Worklogs are not included in Twproject's project JSON export. We extract them via direct API calls using the task ID association, pulling date, hours, user, and notes. Trello has no native time-entry object, so we embed worklog data as either a structured card description entry (date + hours + user) or as a read-only checklist item on the related card. Worklogs that represent billable hours should be migrated to a dedicated time-tracking Power-Up (such as Timesheet by Greep or Plinq) post-migration, which we recommend during scoping. Date-range scoping applies to limit extraction to the relevant active-project window.

Twproject's Costs & Revenues section (budget-vs-actual forecasts) is excluded from the project JSON export and fetched separately via API. Trello has no cost-tracking feature at any tier. We document cost data as structured text in the related card description and deliver a written cost data export as a supplementary CSV. For teams that need ongoing budget tracking, we recommend establishing a separate financial Power-Up or tool post-migration. Cost records are flagged as not migratable-native during scoping so the customer can plan accordingly.

Twproject custom fields (wizard-driven on tasks and projects) are retrieved via API and mapped to Trello Custom Fields. Trello Custom Fields are available on Standard ($6/user/month) and Business Class ($10/user/month) plans only — the free tier does not support them. We enumerate all Twproject custom field definitions during discovery, map data types to Trello's Custom Field types (text, number, date, checkbox, single-select, multi-select), and import values per card. If the customer is on Trello Free, we flag the limitation and recommend a plan upgrade or note which fields cannot be preserved.

Twproject's Gantt WBS (phases, sub-phases, tasks with start dates, end dates, dependencies, and milestones) has no native Trello equivalent. Trello natively stores only card title, description, due date, member, label, and list position. We map task start and end dates to card due dates and start dates, map the WBS phase path to a label (e.g., Phase-1-Design), and document the full dependency tree in a separate CSV for manual rebuild. Trello's Timeline Power-Up (Business Class) provides a Gantt-style view after migration but must be installed and configured post-migration — dependencies are not automatically re-created in Timeline.

Twproject's Kanban is a daily planning view rather than a top-level project object, driven by task status and assignments. We migrate the underlying task data (assignee, status, dates) which populates Trello's board views naturally. The Kanban board configuration itself (columns, swimlanes, WIP limits) is Twproject-specific and does not transfer — we document the column names and any WIP limit settings as a written reference for the customer's admin to reconfigure in Trello Lists or in a Power-Up.

Twproject tags on tasks and projects map to Trello Labels. We retrieve tag assignments via API, normalize them to Trello label names, and apply color assignments where Twproject uses a color taxonomy. Some Twproject tags may be flat while Trello labels are per-board — we note any workspace-level labeling strategy during scoping so tags used across multiple projects are handled consistently.

Twproject supports MS Project file import and export for projects that originated in Microsoft Project. We include MS Project metadata (task hierarchy, durations, dependencies) as card description notes or as labels if the project originated externally and the MS Project data is the primary record. We flag this during scoping to determine whether the MS Project import data is the authoritative source or supplementary.

Twproject's resource workload view shows assignment distribution across time periods per resource. Trello has no workload view — card membership is the only allocation signal. We map Twproject assignment data to card members, and document per-resource assignment load in a written CSV (resource, task, allocation percentage, date range) for the customer's admin to use when rebuilding workload visibility in a Power-Up or external resource management tool.