Migrate from Worksection to Trello

Each Worksection Project becomes a Trello Board, and Worksection's workspace or client-level grouping maps to a Trello Workspace. Worksection's project name, description, status, and date range transfer to the Board. We handle the structural split by creating a Workspace for each client or organizational grouping, then creating Boards within that Workspace per project. Folder hierarchy within a Worksection project maps to Lists within the Trello Board.

Worksection Tasks map directly to Trello Cards. Task title becomes Card name, description migrates to Card description (markdown preserved where possible), due date maps to Card due date, priority maps to a Custom Field (Priority label, Business+ only) or a color-coded label, and assignee resolves to a Trello member by email match. Worksection's status field maps to the appropriate List (To Do, In Progress, Done) which we configure during migration scoping.

Worksection Subtasks migrate as Checklist items on the parent Card. Subtask title becomes the checklist item name, and subtask status (complete/incomplete) maps to checked/unchecked. We preserve the parent-child relationship by nesting all subtasks under a 'Subtasks' or 'Checklist' heading on the Card. Worksection's three-level hierarchy (Project > Task > Subtask) flattens to a Card with a Checklist, which is the structural limitation of the destination platform.

Worksection task labels and stage tags map to Trello Labels. We map label names directly to Label names and assign colors where Worksection's color tag system can be reverse-engineered. Note that Worksection color tags on projects (visual markers, not data fields) do not transfer per Worksection's own migration documentation — we flag this gap explicitly in the gotchas.

Worksection task comments migrate as Trello Card comments. Author attribution and timestamp are preserved in the comment metadata. Threaded discussion in Worksection migrates as a flat comment thread in Trello, which does not support nested replies natively. We preserve the chronological order of comments by posting them sequentially on the Card.

File attachments on Worksection Tasks and Projects migrate as Card attachments in Trello. We resolve FTP-linked and Google Drive file references from Worksection and attach the actual files where accessible. Attachment metadata (file name, size, upload date) is preserved. Google Drive attachment links transfer as links if the Drive file is accessible to the migrating team.

Time entries present the most significant mapping gap. Trello has no native time-tracking object. On Business Class ($10/user/month) and Enterprise plans, we create Custom Fields named 'Hours Logged' (number) and 'Time Description' (text) on each Card and populate them from Worksection time entries linked to that task. On free or Standard tiers where Custom Fields are unavailable, we add time entries as structured Checklist items under a 'Time Logged' heading. This is a degraded but functional preservation of the financial data context.

Worksection financial costs (hours at hourly rate) have no Trello native equivalent. On Business Class and Enterprise, we create a Custom Field 'Calculated Cost' on Cards and populate it with the Worksection cost value. Cost-per-task reporting for client billing requires a separate export or third-party reporting Power-Up post-migration. We flag this as a reporting gap and recommend the customer's admin set up a scheduled export from Worksection before cutover.

Worksection member accounts (email, name, role) map to Trello members by email match. We resolve each Worksection assignee and project member to a Trello workspace member. If a Worksection user does not have a Trello account, they are added to the workspace and invited during migration. Role permissions (admin, manager, member, guest) map to Trello's Workspace-level roles, though Worksection's granular per-project role grants do not have a direct Trello equivalent.

Worksection teams and departments map to Trello Workspaces. Each Worksection team becomes a separate Workspace containing the Boards migrated from that team's projects. This preserves organizational structure but requires the destination account to have enough Workspace seats for the number of teams being migrated (Enterprise allows unlimited Workspaces; Standard allows multiple Workspaces at no additional per-workspace cost).

Worksection per-project custom fields created via Administration map to Trello Custom Fields on Business Class and Enterprise. Each project defines its own schema independently in Worksection, so we perform field-level mapping per project during scoping. Custom field types (text, number, date, dropdown) map to the corresponding Trello Custom Field type. On Free and Standard tiers, custom fields are not available and we flag this as a data-loss gap for the customer's admin to address post-migration.

Worksection's own migration documentation explicitly states that project history, audit trails, and past-state activity logs are not transferred. This is a Worksection platform restriction, not a FlitStack AI limitation. We flag this upfront during scoping so the customer understands that the full chronological record of task changes, status transitions, and member activity within Worksection is permanently lost in the move. We do not attempt to reconstruct history from Worksection's API.