Migrate from Toggl to OpenTickly

OpenTickly provides an import workflow for moving an existing Toggl Track account without rebuilding every workspace by hand. Use the account export archive for account structure, then add detailed time-entry CSV files to the target workspace.

Before you migrate

1. Create or sign in to the destination OpenTickly account.
2. Confirm the destination instance has enough storage for the uploaded files and PostgreSQL data.
3. Pick a cutover time so new entries are not created in both systems during validation.
4. Keep a record of the date range and workspace covered by every CSV export.

Step 1: export your Toggl account archive

Open Toggl Track settings and request the account data export. Download the resulting ZIP file without changing its internal files.

The archive import 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 for the success or failure message.

OpenTickly processes imports as jobs. Do not close the workflow or upload the same archive again while the first job is still running.

Step 2: import detailed time entries

Export detailed time entries from Toggl as CSV for the date ranges you need. Back in Import:

1. Select the destination organization and workspace.
2. Choose one or more CSV files.
3. Upload them and wait for each import job to finish.
4. Repeat for another workspace only after confirming the destination selector.

Naming files by workspace and date range, such as consulting-2025-q4.csv, makes missing or repeated ranges easier to spot.

Validate the result

Check the migration before treating OpenTickly as the system of record:

• Compare organization and workspace names.
• Open representative clients, projects, tags, and members.
• Compare a known day, week, and month in Reports.
• Check running entries and entries that cross midnight.
• Check billable state, duration, description, project, user, and tags on a sample of entries.
• Record any failed job message before retrying or opening an issue.

Report totals are the strongest end-to-end check because they reveal missing ranges, wrong workspace targets, and entries that were exported twice.

Cut over safely

Once validation passes, tell team members which system should receive new entries. Keep the Toggl exports and a database backup of the new OpenTickly instance for a rollback window that fits your organization.

Next, read Getting started for workspace habits or API compatibility to repoint scripts and integrations.