How to migrate from Toggl Track to TrackTimer

Bring the structure you already use into TrackTimer: clients, active projects, and the people who need access to them. This guide is published by TrackTimer and covers our Toggl Track setup importer.

Open the Toggl Track importer

Toggl Track and Toggl 2.0 are different import sources

This importer connects to Toggl Track. It does not connect to Toggl 2.0. You do not need to move your data into Toggl 2.0 first.

Toggl's own migration guide describes additional planning features and changes to tasks and filtering in its newer product. If your team wants to focus on tracking client work, reviewing a simpler setup can be a useful point to consider switching. There is no need to rush because of a shutdown: Toggl states that Track has no forced migration or announced sunset date. Toggl's migration guide, reviewed September 12, 2026.

What imports

Toggl Track setup	TrackTimer destination
Clients	Create a client or match an existing client
Active projects	Create a project under its mapped client, match an existing project, or skip it
Projects without a client	Map to an Internal client or choose another client
Workspace members	Match existing members by email or select people to invite
Project access	Review assignments for matched members and selected invitees

TrackTimer keeps its own client, project, and member model. This is a one-time setup import, not a continuing sync. Import one Toggl Track workspace at a time into the currently selected TrackTimer workspace. This version supports up to 1,000 clients (including an Internal client when needed) and 1,000 active projects, and 1,000 active members per preview. Archived clients are included as active clients only when an active project needs them; the preview calls this out. Inactive members and unaccepted Toggl invitations are excluded.

Historical time entries do not import. Neither do tasks, tags, rates, budgets, invoices, or archived projects. Historical import may be considered later; it is not available in this workflow. Keep the records you need in Toggl Track or export them there before changing your subscription or access.

Before you start

• Sign in to TrackTimer and select the workspace that should receive the setup. You must be its owner or an admin.
• Use a Toggl Track account with workspace administrator access so the importer can read the workspace setup and project membership.
• Decide who needs access to TrackTimer and what their TrackTimer hourly rates should be. Toggl rates and permissions are not copied.
• Review existing TrackTimer clients and projects so you can reuse them where appropriate.

1. Copy your Toggl Track API token

Open your Toggl Track profile, find the API token near the bottom, and copy it. You use the token already provided by Toggl Track; you do not need to write code or create an integration application. Toggl documents the location and how to reset it in Where is my API key located?.

Treat the token like a password. Paste it only into the importer, not into a support message, screenshot, or shared document. The importer uses it temporarily for the connection and does not save it as a workspace integration credential. Resetting it in Toggl later also affects any other integrations using that token.

2. Connect and choose a workspace

Open the Toggl Track importer, enter the token, and connect. Select the Toggl Track workspace to read. Check that the destination is the intended TrackTimer workspace before proceeding.

The importer only reads from Toggl Track. It does not change or delete your source data.

3. Review clients and projects

Review the preview before importing. Match a source client to an existing TrackTimer client or create one. For each active project, choose an existing project, create a project under the mapped client, or skip it. Review projects without a client under the Internal mapping.

For example, a Toggl Track client called Northstar with a Website refresh project can become the same client and project in TrackTimer. A project called Administration with no client can sit under Internal. These are illustrative names; use your own preview to decide what belongs together.

Do not merge similarly named items unless they represent the same work. Skipping a project leaves it out of this import and does not remove it from Toggl Track. Retries recognize clients and projects previously created from the same source workspace in the same TrackTimer workspace. Existing names and settings are preserved. A repeated import does not update or sync them. Review existing matches if your chosen mappings change; archived or differently mapped targets require review before retrying.

4. Review members, rates, and access

Match people to existing TrackTimer members by email. For new people, explicitly select the invitations you want to prepare. New invitees default to the contractor role; Toggl administrator privileges do not carry over. Choose TrackTimer rates in USD instead of assuming Toggl billing or labor rates will be reused.

Check project assignments carefully. A public Toggl Track project can be available to the whole source workspace. TrackTimer represents that access through member assignments, so its preview can include more people than a list of explicit Toggl project members would suggest. Private project assignments must also be reviewed against the people you are bringing over.

Importing clients and projects does not send invitation emails. Review the selected recipients and assignments before choosing Add selected access and send invitations. If a matching invitation is already pending, the importer reports that status without sending another email. New people need to accept their invitation before they can work in the workspace. You can leave people out and invite them later.

5. Start tracking new work

After importing, open a client and project and check the names, member access, and rates. Confirm your own project access before starting a timer. Agree on a switch date with your team so new work is recorded consistently and historical reporting stays understandable across the two tools.

Troubleshooting

• The token is rejected: copy the current token from your Toggl Track profile. A Toggl 2.0 token will not work here.
• A workspace or its members cannot be read: check your source workspace administrator access. Do not treat an incomplete preview as a complete migration.
• A project is absent: only active projects are in scope. Check the selected source workspace and any skipped rows.
• Toggl is limiting requests: wait for its rate limit or API quota to reset, then reconnect. The importer reports an error rather than importing a partial preview.
• A name is too long: shorten it in the preview to 200 characters or fewer. Names are not silently truncated.
• A teammate cannot see a project: check their TrackTimer membership, invitation status, assignment, and rate setup.
• You need old time records: this importer does not transfer historical time. Keep your source records and exports available for reporting.

For agent-controlled tracking after setup, see Connect through MCP. For a personal integration, start with API authentication.