Migrate from Toggl to OpenTickly

You can bring your Toggl Track account over without recreating anything by hand. It takes two steps: import the account export ZIP to get your workspaces, projects, clients, tags, and members, then import time-entry CSVs to get the actual time records.

Before you migrateCopy Anchor Link

1. Create or sign in to the destination OpenTickly account.
2. If you self-host, make sure the server has enough disk space.
3. Pick a switch-over time and stop tracking in Toggl, so you don't end up with entries in both places.
4. Note which workspace and date range each CSV covers.

Step 1: export your Toggl account archiveCopy Anchor Link

Open Toggl Track settings and request a data export. Download the ZIP and don't change anything inside it.

Importing it creates a new organization in OpenTickly. In the OpenTickly web app:

1. Open Import.
2. Enter a name for the imported organization.
3. Select the Toggl export ZIP.
4. Start the import and wait until it says it succeeded or failed.

The import runs in the background. Don't upload the same ZIP again while it's still running.

Step 2: import detailed time entriesCopy Anchor Link

In Toggl, export the detailed time-entry report as CSV for the date ranges you need. Then, back in Import:

1. Pick the organization and workspace to import into.
2. Choose one or more CSV files.
3. Upload them and wait for each one to finish.
4. Before importing for another workspace, double-check that the right workspace is selected.

Naming files by workspace and date range, like consulting-2025-q4.csv, makes it easy to spot gaps or duplicates.

Check the resultCopy Anchor Link

Before you start tracking in OpenTickly for real:

• Compare organization and workspace names.
• Spot-check a few clients, projects, tags, and members.
• Compare the totals for a day, a week, and a month in Reports against Toggl.
• Check running entries and entries that cross midnight.
• On a few entries, check billable, duration, description, project, user, and tags.
• If an import fails, copy the error message before retrying or opening an issue.

Comparing report totals is the quickest way to catch problems: missing date ranges, entries in the wrong workspace, or the same CSV imported twice.

Switch overCopy Anchor Link

Once the numbers match, tell your team to track in OpenTickly from now on. Keep the Toggl export files and a backup of the OpenTickly database for a while, in case you need to go back.

Next: Getting started for day-to-day use, or API compatibility to move your scripts and integrations over.

Before switching over, follow Backups, restore, and upgrades so you can restore your OpenTickly instance if needed. To move records back to Toggl, read Export your data for the CSV conversion steps and limits.