Migrate from Worksection to monday Work Management

Worksection Projects map directly to monday.com Boards. The Worksection project name, description, status, start date, and due date migrate to the Board name and description, with a Status column pre-created on the destination board to hold the Worksection project status values. Project-level custom fields from Worksection Administration become Board-level columns on the monday.com board, requiring schema consolidation if multiple source projects use different custom field definitions.

Worksection Tasks map to monday.com Items within the appropriate Board Group. Task title, description (rich text), assignee, due date, priority, and status transfer directly. Worksection priority levels (low, normal, high, urgent) map to a Status column with corresponding labels. The task description HTML is sanitized and inserted as the item's description column.

Worksection Subtasks migrate as monday.com native Subitems attached to their parent Item. The parent-child relationship is resolved at migration time using Worksection's subtask parent reference and restored by linking each subitem to the corresponding migrated parent item. Subitem title, assignee, due date, and status all transfer directly.

Worksection time entries map to monday.com Time Tracking entries on the item. Each entry's hours, description, and date migrate. If rate-based billing is configured in Worksection, the financial cost value transfers to the Workload column as a billable value. Note: Worksection stores per-user rates at the account or project level and calculates cost on export; monday.com calculates billable amount from its own hourly rate column, so rate-based financial data that should recalculate post-migration is flagged for the customer to verify.

Worksection task labels and stage tags migrate to monday.com Labels or Tags column (the customer selects during scoping). Each distinct Worksection label becomes a distinct tag in the monday.com column. Worksection color tags and project-level color coding are dropped by Worksection's own migration export and cannot be reconstructed; we flag this cosmetic gap explicitly.

Worksection member accounts (email, name, role) map to monday.com workspace members by email match. Roles migrate as board-level permissions if the Worksection role maps to a monday.com team role; otherwise individual board invites are set to the closest equivalent permission level. Any Worksection member without a matching monday.com email is held in a reconciliation queue for the customer's admin to provision before record import.

Worksection Teams and Departments map to monday.com Groups within the destination Board. If the Worksection workspace used teams for project scoping, each team maps to a separate board Group. Team membership is resolved by matching member email addresses against the migrated Worksection member list.

File attachments on Worksection Tasks and Projects migrate as monday.com file column entries. FTP-linked and Google Drive references from Worksection are resolved to physical files where accessible credentials allow, and the resolved files are uploaded to the monday.com item's Files section. Pinned image states from Worksection task cards do not transfer as there is no equivalent pinning mechanism in monday.com.

Worksection task comments migrate as monday.com Activity updates on the item. Author attribution and original timestamp transfer. Threaded replies in Worksection are imported as sequential Activity entries since monday.com does not support nested reply threading. The flattened ordering preserves chronological intent.

Worksection task-level dependencies visible in the Gantt chart map to monday.com native Dependency columns on Items. We resolve the predecessor and successor item IDs at migration time and create the monday.com dependency links. Note: Worksection's stage 'next stage' linking between pipeline stages does not transfer and is dropped by Worksection's own export logic; we document this gap for the customer to re-implement manually in monday.com if needed.

Worksection custom fields created per-project via Administration map to monday.com Board columns. This mapping requires additional scoping because each Worksection project can define its own custom field schema independently, while monday.com columns are board-level and shared across all items. We consolidate per-project fields into a union set, flag any conflicting type definitions (e.g., same field name as text in one project and as a number in another), and create the merged column schema before import.

Worksection financial costs per task and hourly rate configuration are imported as billable values in the monday.com Workload column. The per-user hourly rate is not stored as a reusable monday.com rate configuration; instead, the calculated cost amount transfers as a static value. Customers who rely on rate-based financial reporting should verify the migrated values against the source after cutover.