Migrate from Taskworld to monday Work Management

Taskworld Workspaces map to monday.com Workspaces as the top-level container. We preserve workspace-level settings, member lists, and organization metadata. Enterprise workspaces in Taskworld with dedicated cloud or on-premise deployment map to a monday.com workspace that the customer provisions in their tenant. Member seats are counted and reconciled against the destination plan tier; guest collaborators above the destination plan limit are flagged for seat audit.

Taskworld Projects map to monday.com Boards. The source project metadata (name, description, start date, due date, status) migrates as board properties. Taskworld's project view type (Kanban, Timeline, Calendar) is not preserved as a destination view setting because monday.com boards support all view types simultaneously; we configure the default view based on the customer's preference during scoping. Project-level tags migrate as board labels.

Taskworld Tasks map to monday.com Items within the appropriate Board and Group. Task attributes migrate as follows: assignee maps to Person column, due date maps to Date column, priority maps to Status or Label column (we define the label set during scoping), description text migrates as the Item's main text, and followers map to Watchers if the destination workspace has watchers enabled. Completed status maps to a Status column value of Done or Closed.

Taskworld checklist sub-items within a Task are direct children of the parent Task and carry completion status. monday.com sub-items are separate record types linked to the parent Item. We convert each Taskworld checklist item to a monday.com sub-item with its completion state preserved, preserving the percent-complete calculation shown on the parent Task. Sub-items do not carry assignees by default in monday.com unless the customer enables sub-item ownership during scoping.

Taskworld Custom Fields are defined per-project via the Customize panel. We extract all project-level custom field definitions and their types (text, number, date, dropdown, checkbox). At monday.com, we create equivalent columns on each destination Board. Where multiple Taskworld projects share the same custom field name and type, we configure the column once and add it to each relevant Board rather than re-defining per-board. The customer manually configures column presets if they want global availability without per-board addition.

Taskworld task dependency links (blocks/blocked-by direction) map to monday.com's Dependency column on the relevant Board. We preserve the directional dependency so that Timeline views in monday.com reflect the blocking relationship. Circular dependency detection runs during import; any circular links are flagged and resolved by removing the weakest dependency in the cycle.

Taskworld files are re-uploaded to monday.com storage (subject to the destination plan's storage limit: 250GB Standard, 1,000GB Pro, unlimited Enterprise). We link files to the corresponding Item via monday.com's File column or as an item update attachment. Files exceeding the destination storage limit are skipped and listed in a manifest for manual handling. The original file URL is preserved in an Item Update note if the file cannot be re-uploaded.

Taskworld task-level comments migrate to monday.com Item Updates with author attribution and timestamp. Project chat messages migrate as Updates on a designated board or as Items on a communication log board. Thread structure is preserved where comments have parent_id references; top-level comments map as standalone Updates, replies link as threaded Updates if the destination workspace supports threading, otherwise they flatten. Chat history availability depends on Taskworld plan tier at time of extraction.

Taskworld time entries (where available on the source plan) map to monday.com Time Tracking column values on the corresponding Item. Each time entry's duration and date migrate; task-level time logs become individual Time Tracking entries on the migrated Item. Note text from the time entry migrates as an Update on the Item. If the destination monday.com plan does not include Time Tracking (Basic tier), we flag this during scoping and offer time entries as Number columns or a separate Time Log board.

Taskworld tags applied to Tasks and Projects migrate as monday.com Label column values. We extract the full tag vocabulary from the workspace and configure a Label column on each destination Board with the relevant values pre-populated. Tag hierarchy (if present in Taskworld) is flattened to a single-level label set since monday.com Label columns do not support hierarchy.

Taskworld workspace members map to monday.com Team Members. We resolve by email match against the destination workspace's member list. Guest collaborators (up to 30 on Taskworld Business) migrate as Team Members on monday.com; if the destination plan tier has a guest limit, we flag the count during scoping and the customer resolves seat allocation before migration. Inactive Taskworld users are imported as inactive Team Members to preserve historical assignment references.

Taskworld automations trigger actions based on task events (status change, due date, assignment, checklist completion). monday.com automations are recipe-based with different trigger and action semantics. We do not migrate automations as code because the trigger logic, conditions, and actions do not map directly between platforms. We deliver a written inventory of every active Taskworld automation with its trigger type, conditions, and action steps, plus a recommended monday.com automation equivalent and the specific steps to rebuild it. The customer's admin completes the rebuild post-migration.