Migrate your Toggl Plan data
Visual timeline-based project planner from the Toggl family. Tasks, teams, and projects on a shared calendar with a Kanban option—but the product is being phased out in favor of Toggl Focus.
In its favor
Why people choose Toggl Plan
The signal that keeps Toggl Plan on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Teams already using Toggl Track for time tracking adopt Toggl Plan for its drag-and-drop timeline view and minimal learning curve, keeping both tools in the same ecosystem.
The free tier permits unlimited projects and clients with up to five users, making it attractive to small agencies and freelance teams validating their workflow.
The Kanban board view for project-level task management gives non-planning-oriented teams a familiar interface without forcing them onto a Gantt-style timeline.
Users cite the Toggl brand's reputation for simplicity and low administrative overhead as a reason to stay within the product family.
Built-in task assignment, due dates, and recurrence rules cover basic project tracking needs without requiring a complex setup or paid integrations.
Toggl Plan lacks native financial visibility—users cannot view per-member billing rates or project-level finances within the product itself, forcing them to export data or use a separate tool.
The lack of synergy between Toggl Plan and Toggl Track frustrates users; projects created in one product do not automatically appear in the other, making them feel like separate disconnected tools.
Users migrating to Toggl Focus report that recurring tasks are not yet supported in the new platform, creating friction for teams that rely on repeating work.
Toggl Plan is being actively deprecated in favor of Toggl Focus, which has different data structures and feature parity gaps, pushing customers toward a migration whether they want one or not.
Advanced reporting, custom fields, and enterprise-grade permissions are limited or absent, driving larger teams to tools like monday.com or Wrike that offer deeper customization.
Reasons to switch
Why people leave Toggl Plan
The recurring reasons buyers give for replacing Toggl Plan. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Toggl Plan fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Toggl Plan pricing overview
Toggl Plan uses per-user pricing aligned with the Toggl Track ecosystem. The Free plan is free forever for up to five users. Paid plans start at $9/user/month on annual billing for Starter, $18/user/month for Premium, and custom pricing for Enterprise, which also unlocks higher API rate limits and SSO capabilities.
Free
Tier 1 of 4
$0
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Toggl Plan's schedule — see our quote-based pricing →
What gets migrated
Toggl Plan object support
Object-by-object support for Toggl Plan migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are top-level containers for tasks in both timeline and board views. We migrate Projects 1:1 including their name, client association, archived status, and segment. Active and archived projects are exported separately to preserve workspace cleanliness.
Tasks
Fully supportedTasks are the core record type in Toggl Plan. We map task name, status (todo/in-progress/done), due dates, recurrence rules, estimates in minutes, and start/end timestamps from the CSV export or API V5. Recurrence rules are preserved as pattern metadata.
Teams
Fully supportedTeams are groupings of users whose schedules appear together on the same timeline. We preserve team membership and map each team to the destination as a group or team object, keeping the schedule-view relationship intact.
Users
Mapping requiredUsers are identified by name and email in Toggl Plan. We map Users to the destination platform's user/team-member object. Role differences (Workspace Owner, Admin, User) may not map directly to every destination and are flagged for manual review.
Tags
Fully supportedTags are flat labels applied to tasks across the workspace. We preserve tag names and apply them as labels or tags in the destination. Tag color metadata is carried over if the destination supports it.
Segments
Mapping requiredSegments are workspace-level categorization of tasks or projects. The concept does not exist in most destination PM tools, so we map Segment values to labels, tags, or custom fields depending on destination capability.
Clients
Fully supportedClients are associated with projects in Toggl Plan. We map Client name and contact information where present and link them to their associated Projects in the destination.
Milestones
Fully supportedMilestones are deadline markers within a project. We migrate milestone names and target dates, mapping them to the destination's milestone or phase object if available, otherwise converting them to flagged tasks.
Recurrence
Mapping requiredRecurrence rules on tasks describe repeating patterns. Not all destination platforms support native recurrence, so we flag recurring tasks and either convert them to individual task instances or map to a supported recurrence field.
Time Estimates
Mapping requiredToggl Plan stores task estimates in minutes (daily estimates are multiplied by task length in days). We preserve the numeric estimate but note that the destination may not display it in the same unit or location within the UI.
Taskbox
Not in this platformThe Taskbox is a 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 work not yet committed to project structure.
Attachments
Not in this platformToggl Plan does not expose an attachment export path in its public data export or API V5. Files attached to tasks are not included in the CSV export and are not accessible via standard API calls. We flag this gap and recommend users export attachments manually.
Comments
Not in this platformTask 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 and recommend exporting them as linked text exports if needed.
Custom Fields
Mapping requiredToggl Plan does not have a first-class custom fields concept in its data model. Any pseudo-custom data stored in task attributes (e.g., text fields used as custom values) is migrated as standard text properties and flagged for mapping review.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are top-level containers for tasks in both timeline and board views. We migrate Projects 1:1 including their name, client association, archived status, and segment. Active and archived projects are exported separately to preserve workspace cleanliness. |
| Tasks | Fully supported | Tasks are the core record type in Toggl Plan. We map task name, status (todo/in-progress/done), due dates, recurrence rules, estimates in minutes, and start/end timestamps from the CSV export or API V5. Recurrence rules are preserved as pattern metadata. |
| Teams | Fully supported | Teams are groupings of users whose schedules appear together on the same timeline. We preserve team membership and map each team to the destination as a group or team object, keeping the schedule-view relationship intact. |
| Users | Mapping required | Users are identified by name and email in Toggl Plan. We map Users to the destination platform's user/team-member object. Role differences (Workspace Owner, Admin, User) may not map directly to every destination and are flagged for manual review. |
| Tags | Fully supported | Tags are flat labels applied to tasks across the workspace. We preserve tag names and apply them as labels or tags in the destination. Tag color metadata is carried over if the destination supports it. |
| Segments | Mapping required | Segments are workspace-level categorization of tasks or projects. The concept does not exist in most destination PM tools, so we map Segment values to labels, tags, or custom fields depending on destination capability. |
| Clients | Fully supported | Clients are associated with projects in Toggl Plan. We map Client name and contact information where present and link them to their associated Projects in the destination. |
| Milestones | Fully supported | Milestones are deadline markers within a project. We migrate milestone names and target dates, mapping them to the destination's milestone or phase object if available, otherwise converting them to flagged tasks. |
| Recurrence | Mapping required | Recurrence rules on tasks describe repeating patterns. Not all destination platforms support native recurrence, so we flag recurring tasks and either convert them to individual task instances or map to a supported recurrence field. |
| Time Estimates | Mapping required | Toggl Plan stores task estimates in minutes (daily estimates are multiplied by task length in days). We preserve the numeric estimate but note that the destination may not display it in the same unit or location within the UI. |
| Taskbox | Not in this platform | The Taskbox is a 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 work not yet committed to project structure. |
| Attachments | Not in this platform | Toggl Plan does not expose an attachment export path in its public data export or API V5. Files attached to tasks are not included in the CSV export and are not accessible via standard API calls. We flag this gap and recommend users export attachments manually. |
| Comments | Not in this platform | 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 and recommend exporting them as linked text exports if needed. |
| Custom Fields | Mapping required | Toggl Plan does not have a first-class custom fields concept in its data model. Any pseudo-custom data stored in task attributes (e.g., text fields used as custom values) is migrated as standard text properties and flagged for mapping review. |
Gotchas
What to watch for in Toggl Plan migrations
Issues we've hit on past Toggl Plan migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Toggl Plan is actively being sunset into Toggl Focus
Data export restricted to workspace Owners and Admins
CSV export omits comments, attachments, and custom field metadata
Recurrence export is pattern-level, not instance-level
| Severity | Issue |
|---|---|
| High | Toggl Plan is actively being sunset into Toggl Focus |
| Medium | Data export restricted to workspace Owners and Admins |
| Medium | CSV export omits comments, attachments, and custom field metadata |
| Low | Recurrence export is pattern-level, not instance-level |
Leaving Toggl Plan?
Where Toggl Plan customers move next
5 destinations Toggl Plan can migrate to.
How a Toggl Plan migration works
Four steps, Toggl Plan-specific
Connect
API key or OAuth into Toggl Plan. Scopes limited to read-only on the data we move.
Map
We translate Toggl Plan-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Toggl Plan quirks before production.
Migrate
Full migration with Toggl Plan rate-limit handling. Rollback available throughout.
FAQ
Toggl Plan migration FAQ
Answers to the questions buyers ask most during Toggl Plan migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Toggl Plan migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Toggl Plan.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Toggl Plan setup and destination — written quote back within a business day.