Migrate from TeamGantt to Trello

TeamGantt Projects map to Trello Boards. Each Project's start date is inferred from its earliest task start date in TeamGantt (there is no explicit project start/end field), so we use that earliest task date as the Board creation context. Projects with multiple milestone groups can be mapped to separate Lists within a single Board or to separate Boards entirely; the customer chooses the board structure during scoping. Custom project-level fields migrate to Trello Custom Fields on the Board.

TeamGantt Tasks map to Trello Cards. We preserve: task name, description (notes), start date, due date, duration, percent complete, and assignee. Percent complete from TeamGantt maps to Trello's Card cover color or a checklist item completion ratio depending on customer preference. Cards are created in the target List (mapped from the TeamGantt Group/Subtask structure) before moving to the next phase.

TeamGantt Groups represent the subtask hierarchy within a Project. Each Group maps to a Trello List, and Tasks within the Group become Cards in that List. Nested sub-groups are flattened to one level of List; deeply nested subgroups are mapped as Cards with the full path name preserved in the Card title for manual reorganization post-migration. The mapping spec documents the nesting depth for the customer's admin to evaluate against their Trello board structure.

TeamGantt Milestones (zero-duration date markers) map to Trello Cards with the milestone name and the target date set as the Card due date. We flag milestones in the Card name prefix (e.g., '[MILESTONE]') so they are visually identifiable. The milestone association to parent Project is preserved in the Board name. There is no native milestone type in Trello; if the customer requires a calendar or timeline view of milestones, we recommend the Planyway or Placker Power-Up post-migration.

Task dependencies define predecessor/successor chains in TeamGantt. Trello has no native dependency model. We export the full dependency graph (predecessor_id, successor_id, type, lag_days) as a written dependency map and include a ranked list of Cards requiring manual link setup. If the customer licenses a dependency Power-Up (Placker, GoodGantt, Planyway), we provide the data in the format required by that Power-Up's import tool. Dependencies are not migrated programmatically because no stable Trello native API supports them.

TeamGantt Checklist items on Tasks map to Trello Card Checklists. We preserve checklist item names and completion status. Checklist item order is preserved. Trello supports multiple checklists per Card; we maintain the original checklist structure grouping within each Card. Checklist-level completion percentages map to the same percent-complete logic used for Card cover or summary.

TeamGantt Labels map directly to Trello Board Labels. Label names and colors transfer. Label assignments across all Tasks are preserved as Card Label assignments. If the TeamGantt account uses more labels than the target Trello Board supports (10 label colors per Board by default), we map excess labels to label name prefixes and group by color family.

TeamGantt Discussion threads on Tasks map to Trello Card Comments. We preserve full comment text, author name, author email, and timestamp. Comment ordering is maintained chronologically. Trello does not support threaded replies natively; flat comment chains map directly. If the source comments contain @mentions, we note them as plain-text mentions in the comment body since Trello @mentions are a different mention system.

TeamGantt custom fields exist at both project and task levels. We discover all custom field definitions via the TeamGantt API (field type, label, options for picklist fields) and create equivalent Trello Custom Fields on the target Board before data import. Text, number, date, and checkbox types map directly. Picklist fields map to Trello Dropdown Custom Fields with the original option values. Custom fields with no equivalent Trello type are flagged for the customer to choose a representation (text, label, or checklist).

TeamGantt Users (task assignees and project collaborators) map to Trello Board Members. We resolve by email match. Guest users in TeamGantt who have limited project access map to Trello Members added to the relevant Boards only. Trello Free tier supports unlimited Members per Board, so no member-count constraint applies. Users without a Trello account are held in the reconciliation queue for the customer to provision accounts before card assignment migration proceeds.

TeamGantt time entries (tracked hours per task) have no native Trello equivalent. We append time entry data to the Card description in a structured format (date, user, hours, notes) and optionally create a 'Time Log' checklist item per Card for manual tracking. If the customer licenses a Trello time-tracking Power-Up post-migration, we provide the time entry data in the format required for that Power-Up's import.

TeamGantt Baselines capture a snapshot of the original planned schedule for comparison against actual progress. Trello has no baseline or planned-vs-actual comparison feature. We export all saved baselines as a structured CSV (task name, planned start, planned end, actual start, actual end, variance days) and deliver it as a written handoff artifact. The customer's admin uses this to manually recreate baseline data in a spreadsheet or a third-party reporting tool. We do not migrate baselines programmatically because no Trello API or Power-Up supports this data model.

The TeamGantt Workloads report (available on Pro and Unlimited plans) shows per-user task assignments and hour allocations. Trello has no native workload view. We export the Workloads report as a CSV (user, task, hours assigned, hours logged) and deliver it as a written artifact. For teams using a Trello Power-Up with workload features (Planyway, Placker), we provide the data in the format required for that Power-Up's import. If the source account is on Basic or Standard, workload data is sourced from the CSV export fallback.