Migrate from Toggl Plan to Jira

Toggl Plan Projects map directly to Jira Projects. We preserve the project name, archived status, and client association (where present) and create the corresponding Jira project using the Jira REST API or CSV project importer. If the customer uses Jira Software, we configure the default issue type scheme during creation so that new issues inherit the correct Epic, Story, Task hierarchy.

Toggl Plan Tasks are the core record type and map to Jira Issue types. We define the mapping during scoping: tasks with a milestone or deadline target that affects multiple team members become Jira Epics; tasks that represent deliverable work items become Stories; atomic action items become Tasks; and sub-items of a Task become Subtasks. The customer chooses the hierarchy depth based on their Jira project type. Sub-task enablement must be switched on in the Jira project settings before migration begins.

Toggl Plan Teams are user groupings whose schedules appear together on a shared timeline. Jira has no direct team-scheduling view, but Teams map to Jira Groups or Project Roles for permission scoping. We preserve team membership in a custom field toggl_team__c so that the customer's admin can filter by original Toggl Plan team in Jira filters and dashboards.

Toggl Plan users identified by name and email map to Jira Users. We match by email during migration. Any Toggl Plan user without a matching Jira account is held in a reconciliation queue; the customer's Jira admin provisions the missing accounts before the user-scoped records are imported.

Toggl Plan Tags are flat labels applied to tasks. We preserve tag names and apply them as Jira Labels on the corresponding issues. Tag color metadata, which Toggl Plan exports, has no Jira native equivalent; we write color values to a custom field toggl_tag_color__c if the customer requires that data for reporting.

Toggl Plan Segments are workspace-level task categorization that has no direct Jira equivalent. We map Segments to Jira Components (per-project, with a Component Lead) or to Labels (cross-project) based on whether the customer uses Segments for cross-workspace reporting. The customer chooses the strategy during scoping.

Toggl Plan Clients are associated with Projects. We preserve client name and contact information where present and link them to the corresponding Jira Project. If the customer uses Clients for billing attribution, we create a client__c custom field on the Project or Epic level and populate it during migration.

Toggl Plan Milestones are deadline markers within a project. We map Milestone names and target dates to Jira Fix Versions. The milestone name becomes the Fix Version name; the target date becomes the release date. Fix Versions appear in Jira's release reports and can be used to scope sprints. If the customer uses milestones for cross-project reporting, we also write a milestone__c custom field on the Epic.

Toggl Plan recurrence rules describe repeating patterns attached to tasks. Jira does not support native recurrence on issues. We offer two strategies during scoping: pattern-as-label writes a toggl_recurrence__c field on each recurring task pointing to the original recurrence rule; instance-expansion creates individual Jira issues for each occurrence within a defined window (30, 60, or 90 days) chosen by the customer.

Toggl Plan stores time estimates in minutes. Jira uses Original Estimate in seconds by default. We convert minutes to seconds during field mapping and write to Jira's Original Estimate field. If the customer uses Toggl Plan's billable rate feature, we create an estimated_hours__c custom field to carry the financial estimate separately, since Jira's native estimate field is purely for scheduling.

The Taskbox is a personal holding area in Toggl Plan for tasks not yet assigned to a project or team. It is an ephemeral workspace state rather than a persistent data object. We do not migrate Taskbox contents as they represent unorganized work-in-progress with no project affiliation.

Toggl Plan does not expose an attachment export path in its public CSV export or API V5. File attachments on tasks are not included in the migration scope. We recommend exporting attachments manually via Toggl Plan's UI before the migration window if the customer requires them.