Toggl says there are no forced migrations to Toggl 2.0. Count your Track hours before you import anyway.

Toggl's announcement for Track users answers the migration question in one line: "No — there are no forced migrations." Track keeps running, pricing carries over, and if you import, "the structure carries over so it matches what you have today." In September, on the same forum, a user opened a thread with "Subsequent to mandatory upgrade and import to Toggl 2.0 from Toggl Track," and went on to say their iPhone entries had stopped arriving. Whichever way you end up moving, the import is a copy, and Toggl's own docs list what the copy leaves behind. This post covers what those pages say, what users ran into, and how to count your Track hours so you know what arrived.

What Toggl says

The announcement went up on June 16, 2026, from Toggl's Support account. It says "Toggl Track continues, and we have not set a sunset date." It says "For existing Toggl Track users, pricing will carry over." And it says "Nothing is moved or deleted without your say-so."

That last line is the useful one. Your Track workspace is still there after you import. That makes it the record you check the import against, and it stays that way until the numbers match.

What the import leaves out, by Toggl's own docs

Toggl's admin guide for Track users calls the import "a one-time copy of your Toggl Track data — clients, projects, tasks, tags, time entries, and members." The import page adds: "This is not a live sync." Then it lists the exceptions:

• "All time data is imported to Toggl 2.0 up to the first 30-month gap."
• "Task-level rates aren't imported — Toggl has no task-level rate concept, so these are skipped with a warning."
• "Only the project's current fixed fee is imported — historical fixed-fee changes are not brought over."
• "Import is available at Workspace level only. You cannot choose specific projects."
• For Track, you "Choose whether to import data for your entire workspace or just for your user account."

Read the gap rule twice. The page's example says: "if your workspace has three years of data, a two-year gap with no data prior, and another year of data before that, only the first three years would be imported in this scenario." A two-year gap is 24 months, not 30. The rule and its example don't agree, and the page doesn't say which one the importer follows. If your workspace went quiet for a year or two, a count by year is how you find out.

The rate items change money, not hours. Rates set on tasks are skipped. A project whose fixed fee changed arrives with today's fee only. In a full-workspace import, rates set on the workspace, members, projects and project members come across with their history. So on some projects the hours can match while the billable amounts don't, and that's by design.

What users on Toggl's forum ran into

• June 9: "I've imported all the data from Toggl Track, but in 2.0 (Focus) I have now days when I've worked 40+ hours." The poster adds: "It looks like, in Focus all records of all organisation members are assigned to me." The only reply is labeled "AI-generated response" and says "the knowledge base does not contain specific details" about how the import handles a multi-member workspace.
• August 18: "I have a Toggl Track Starter Plan license, but cannot access Starter Plan features in Toggl 2.0." Support answered the next day: "We’re still setting this up on our end to happen automatically. The ETA is end of August."
• September 3: a user on Track's free plan says tags on projects need a paid plan in 2.0, "forcing us to upgrade for the features we had on the previous version."
• September 9: the iPhone thread. The user found a way back to Track and wrote: "I opted to go back to Track and I still see all my historical entries, plus the new ones coming in from iphone app." The same day, on the announcement thread, another user wrote of the two desktop apps: "track continues to track my activity, 2.0 isn’t."
• September 19: a user says the Default Project feature "did not come over to Toggl 2.0."
• October 12, on Toggl's billable rates thread: "My Project Manager can't view the billable amount when running a report… why is that?" In March, Support had said on that thread: "Currently you cannot sync rates with Track or add Fixed Fee in Focus."

Only the first of these is a total that came out wrong, and it came out high, not low. The iPhone thread and the desktop comment are about entries made after the import. A count catches both: the first on the day you import, the second within a week.

Count in Track before you import

Do this as a workspace admin, before you press Import data. Track's Summary report shows Total Hours, Billable Hours and Revenue, which Toggl defines as billable hours multiplied by your billable rate. Set it up once and change only the dates.

• Turn rounding off. The Summary report has a Rounding button, and a rounded total won't match an unrounded one. You want the raw number on both sides.
• Count by year, back to your first entry. Write down total hours, billable hours and revenue for each calendar year. This is the count that shows where a gap cut your history.
• Count by member, for each year. If one person's hours land on someone else, the workspace total still matches and the member totals don't. That's the 40-hour day.
• Count by project, across all years. Mark the projects with task-level rates or a fixed fee that changed. Their hours should match. Their revenue may not.
• If you're importing only your own user account, filter the report to yourself and count that. The workspace total isn't the number you're checking.
• Save it. Toggl's export page says "on Toggl Track the Free plan only supports PDF exports," and the Summary report page says "CSV and Excel exports are a paid plan feature." A PDF for each year is enough. It's a record of the totals, not a copy of the data.