Migrate from Toggl Plan to monday Work Management

Toggl Plan Projects map directly to monday.com Boards. We preserve the project name, client association, archived status, and segment as board-level metadata. Active and archived projects are migrated separately so that the customer can decide whether archived boards are included in the initial monday.com workspace setup. If the Toggl Plan workspace uses multiple segments per project, we map each segment to a separate monday.com board or to board Groups with segment labels depending on the customer's preference.

Toggl Plan Tasks are the core record type and map 1:1 to monday.com Items. We map task name, status (todo/in-progress/done), due dates, assignee, and time estimates in minutes. Task hierarchy (sub-tasks in Toggl Plan) maps to sub-items in monday.com, which are fully supported. Start/end timestamps become date columns on the item. The item is created in the board that corresponds to its parent Toggl Plan Project.

Toggl Plan Teams are groupings of users whose schedules appear together on the shared timeline. We map each Team to a monday.com Group within the relevant board, preserving team membership and team name. User-to-group assignment migrates by resolving the Toggl Plan user email to the corresponding monday.com team member. If a Toggl Plan user belongs to multiple teams, they are added to multiple Groups in monday.com.

Toggl Plan users are identified by name and email. We map Users to monday.com team members by email match. Toggl Plan role differences (Workspace Owner, Admin, User) do not map directly to monday.com permission levels; we assign all migrated users as Members initially and the customer's monday.com admin configures Individual, Editor, or Viewer permissions post-migration based on the destination plan tier.

Toggl Plan Tags are flat labels applied to tasks across the workspace. We preserve tag names and apply them as Labels in monday.com. Tag color metadata carries over if the destination board uses color-coded labels. Labels in monday.com are workspace-level and can be applied to items across boards, matching the cross-project scope of Toggl Plan tags.

Segments are a Toggl Plan workspace-level concept with no native monday.com equivalent. We do not drop segment data. During scoping, the customer chooses the destination strategy: segments become workspace-level Labels applied to items, a dedicated Status column with segment values, or a text-based custom column. The choice depends on how the customer uses segments for filtering and reporting.

Toggl Plan Clients are associated with projects. We map Client name and any contact information present to a monday.com Board named for the client, or to a client contact item in a dedicated contacts board. If the customer uses monday.com's Contacts feature, we link client items to Contacts records for cross-board relationship visibility.

Toggl Plan Milestones are deadline markers within a project. monday.com has no native milestone object, so we convert milestones to date columns with a milestone label applied to the item, or to automation rules that trigger notifications when the milestone date is reached. The customer chooses the strategy during scoping based on how they use milestones for project tracking and reporting.

Toggl Plan exports recurrence as a rule attached to the task, not as individual instances. monday.com has no native recurrence rule object. We flag every recurring task during scoping. For each recurring task, the customer chooses between two strategies: expand to individual monday.com items with a recurrence label (one item per instance for a defined date range), or document the recurrence pattern as a monday.com automation recipe for the admin to configure post-migration. We do not migrate recurrence as automation code.

Toggl Plan stores task estimates in minutes. We preserve the numeric estimate in a monday.com Number column. The unit context (minutes) is noted in the column name so the customer's team knows the original unit. monday.com does not natively display estimates in the same task card format as Toggl Plan; the number is visible in the item detail view and can be included in formula columns if the Pro plan is selected.

The Taskbox is Toggl Plan's personal holding area for tasks not yet assigned to a project or team. This is an ephemeral workspace state rather than a persistent data object. We do not migrate Taskbox contents as they represent unorganized, transient work items. We surface the Taskbox existence in the scoping call and advise the customer to review its contents manually and assign relevant items to projects before migration.

Toggl Plan does not expose an attachment export path in its CSV export or API V5. Files attached to tasks are not included in the data extract and are not accessible via standard API calls. We flag this gap during scoping and recommend the customer exports attachments manually from Toggl Plan and stores them in a shared location (Google Drive, SharePoint, or monday.com Docs) with a reference link added to the migrated item.

Task comments are not included in the Toggl Plan CSV export or listed as a supported API V5 object. We cannot migrate comment threads as structured data. We recommend the customer exports comments manually from Toggl Plan as a text document linked to the task name, and stores it in the migrated item's activity log or in monday.com Docs if comment context is important for onboarding.