Migrate from Gauss Box Projects to Trello

Gauss Box Projects map directly to Trello Boards. Project name, description, start date, and end date migrate to Board name, description, and a date Custom Field capturing the project window. Each Board is created at the Workspace level with default visibility set per the customer's preference. We inventory all projects during discovery and flag any with complex nested subprojects that may require multiple boards or a board-per-subproject structure.

Gauss Box Phases become Trello Lists within each Board. Phase name and phase-level deadline migrate to List name and a due date Custom Field on the first card or a dedicated date card in the list. Phases are the primary ordering mechanism in Gauss Box; we preserve their sequential relationship by creating Lists in phase order. If a project has more than 25 phases, we split the board into multiple boards per phase cluster to stay within Trello's practical column limit.

Gauss Box Tasks map to Trello Cards within the List corresponding to their parent Phase. Task name, description, assignee, due date, priority, and status migrate to Card name, description, member assignment, due date, label (for priority), and List position. Task attachments and comments migrate as card attachments and card comments respectively. We preserve card ordering within each List to match the original task sequence.

Gauss Box Subtasks become Trello Checklist items on the parent Card. We preserve the parent-child relationship by creating a named Checklist (e.g., 'Subtasks') on each Card containing all child subtasks as checklist items. Subtask status (complete/incomplete) maps to checklist item checked/unchecked. If subtasks have their own assignees, due dates, or descriptions beyond a name, we promote them to separate Cards and add a label 'Subtask-of: [parent task name]' to preserve the hierarchy.

Gauss Box Gantt chart data (task start/end dates, dependencies, milestones) has no native Trello equivalent. We migrate start and end dates as Custom Date Fields on Cards and flag Trello power-ups (Timeline, BigGantt) as the rebuild option for visual Gantt representation. Task dependencies are inventoried as a written dependency map because Trello does not enforce dependency ordering natively; customers use the Dependencies power-up or a third-party tool to rebuild dependency logic.

Gauss Box time entries and activity logs have no native Trello equivalent. We migrate time estimate, actual time logged, and budget comparison as Custom Number Fields on Cards labeled 'Estimated Hours', 'Logged Hours', and 'Budget Hours'. Trello does not aggregate these fields automatically; the customer should use a time-tracking power-up (Clockify, Everhour) if ongoing time logging is required, or use the migrated values as a baseline for future tracking.

Gauss Box task and project comments migrate to Trello Card comments. Comment body, timestamp, and author name (resolved to Trello member if the author has a matching Trello account) migrate directly. Threaded comment chains in Gauss Box flatten into sequential comments in Trello with a quoted attribution header (e.g., '[Author] replied:') to preserve context. We note that Trello comments are not threaded and do not support @mention notifications without a power-up.

Files attached to Gauss Box tasks and projects migrate as Card attachments in Trello. We map file name, file size, upload date, and the attached-by user. Storage tier constraints on Gauss Box are inventoried during scoping; we flag any attachment sets exceeding 50MB total per Card (Trello's practical limit for attachments) and advise splitting large files across multiple Cards or using Trello power-ups for cloud storage linking (Google Drive, Dropbox) instead of direct upload.

Gauss Box Custom Fields via attribute sets map to Trello Custom Fields on Cards. We inventory the full attribute set schema during discovery, match field types (text, number, date, dropdown) to Trello's supported Custom Field types (text, number, date, single-select, multi-select, checkbox), and create the destination Custom Field definitions before migration. Only Standard ($5/user) and Premium ($10/user) Trello plans include Custom Fields; we confirm the customer's target plan during scoping.

Gauss Box Users map to Trello Workspace Members. We match users by email address and invite any unmatched users to the Workspace before migration. Gauss Box department and role assignments are inventoried as metadata; Trello uses Workspace roles (Standard, Admin, Observer) and board-level membership rather than a department hierarchy, so we map Gauss Box roles to a combination of Workspace role and board member access levels. External collaborators in Gauss Box map to Trello Board guests.

Gauss Box external collaborators with view-only or limited roles migrate to Trello Board Guests. Guest access is granted per board, and we map the original Gauss Box access level (full, limited, view-only) to Trello's Guest permission model (can view, can comment, can edit per board settings). We flag any Gauss Box collaborators that had project-level access but no task-level access, as Trello does not support column-level or card-level access restrictions without a power-up.

Gauss Box Dashboard widgets (project health, team activity, resource usage, time overview, budget overview) have no direct Trello equivalent in the Standard workspace views. We deliver a written inventory of each widget with its source data fields and recommend Trello power-ups (Cor本, Screenful, Blue Cat Reports) or a connected BI tool (Looker Studio, Power BI) for dashboard reconstruction. Custom dashboard configurations do not migrate as dashboard layouts; they are documented for manual rebuild.