Migrate from Toggl Plan to Asana

Toggl Plan Projects map 1:1 to Asana Projects. Project name, archived status, and client association (from the Client field) migrate. Archived projects are migrated as archived Projects in Asana; the customer's admin confirms whether archived projects are in scope during scoping. The Toggl Plan segment assigned to the project is applied as a Label on the Asana Project.

Toggl Plan Teams map directly to Asana Teams. Team membership (member list per team) migrates as Team Members in Asana. Note that Asana Teams cannot have sub-teams; if the Toggl Plan workspace has a nested team hierarchy, we flatten it to a single team level and document the original structure as a custom field on each member record.

Toggl Plan Tasks map to Asana Tasks. Task name, status (todo/in-progress/done to Asana custom status columns or completion), due dates, start dates, assignee (primary only; see gotchas on multi-assignee), time estimates in minutes, and tags migrate. Toggl Plan does not support subtasks, so any task that is conceptually a sub-item of another task is migrated as a top-level task with a custom field parent_task__c set to the name of its logical parent for manual reorganization by the admin post-migration.

Toggl Plan recurrence rules (RRULE-style patterns) do not have a native equivalent in Asana. We expand each recurring task into individual task instances using the recurrence pattern to generate task instances at a configurable frequency (daily, weekly, monthly, yearly) up to a customer-defined horizon (e.g., 12 months forward). Each generated task receives a label Recurring to distinguish it from one-off tasks. The original recurrence rule is stored in a custom field original_recurrence__c on the first instance for reference.

Toggl Plan Milestones map to Asana Milestones (a checkbox-type field on a task). Milestone name, target date, and associated project migrate. If the destination Asana project uses a custom status system rather than Asana native milestones, we convert milestones to flagged tasks with a milestone__c custom field set to true and a due date matching the original target.

Toggl Plan Tags map directly to Asana Labels. Tag names and colors migrate if the destination supports label color; otherwise tag names migrate as text labels. Tags are applied to tasks after task creation to avoid labeling orphaned records during migration.

Toggl Plan Clients are associated with Projects but have no native equivalent in Asana. We create a single-select custom field client__c on each migrated Project and populate it with the Client name from Toggl Plan. If the customer requires Client-level reporting in Asana, we discuss creating a separate Client portfolio or using Asana's Company object in a hybrid CRM setup during scoping.

Toggl Plan Segments are workspace-level categorization of tasks or projects that do not exist in Asana. We offer two migration strategies: (1) apply Segment values as task Labels for quick filtering, or (2) create a custom field segment__c (multi-select or text depending on Asana plan) and populate it per task. The customer selects the strategy during scoping. Label is the default for simplicity; custom field is preferred if cross-project segment reporting is required.

Toggl Plan Users identified by name and email map to Asana Workspace members. We match users by email address. Any Toggl Plan user who does not have a corresponding Asana account is placed in a reconciliation queue for the customer's admin to provision before task assignee migration begins. Toggl Plan role distinctions (Owner, Admin, User) do not map directly to Asana roles and are not migrated as structural permissions.

Toggl Plan stores time estimates in minutes. We map these to Asana's Estimated Time custom field (available on Advanced plan at $24.99/user/mo) or to a plain-text custom field est_minutes__c on Starter and Premium tiers where the native Estimated Time field is not available. Daily estimates stored as minutes-per-day are multiplied by task length in days before migration.

Archived Toggl Plan projects migrate as archived Asana Projects. Asana marks a project as archived by setting the archived flag via API. We include archived projects in the migration scope unless the customer explicitly excludes them during scoping. Archived projects are migrated after active projects to avoid cluttering the initial reconciliation check.

Toggl Plan task comments are not included in the CSV export and are not listed as a supported API V5 object. We cannot migrate comment threads as structured data. We flag this gap in the scoping call and recommend exporting comments manually as linked text exports for the customer's admin to re-enter post-migration if comments are business-critical.

Toggl Plan does not expose an attachment export path in its public CSV export or API V5. Files attached to tasks are not accessible via standard API calls and cannot be migrated. We flag this gap and recommend that the customer's admin download or screenshot critical attachments from Toggl Plan before the migration window.

The Taskbox is a personal holding area in Toggl Plan 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 unscheduled work-in-progress rather than durable project data.