Migrate from WakaTime to AtoAxis

Moving has two independent parts. Live tracking takes two lines in the settings file of the WakaTime plugin you already use. Your history moves separately, as a WakaTime data export you import into the dashboard. You can do either one first, and nothing in your WakaTime account is deleted by either.

• Your editor with its WakaTime plugin, left installed exactly as it is
• An AtoAxis account and API key. During Early Access, keys are issued to people on the list
• Optional: your WakaTime history as a data export that contains raw heartbeats

One AtoAxis key replaces your WakaTime key in the plugin. The same key also covers every other editor and AI hook on your account.

• Open Settings in the dashboard and find the API key panel
• Choose Generate key and copy it
• Regenerating later replaces the old key at once, so update every machine when you do

Every WakaTime plugin reads the same settings file in your home folder: ~/.wakatime.cfg on macOS and Linux, %USERPROFILE%\.wakatime.cfg on Windows. Set two values and save it.

[settings]
api_url = https://api.atoaxis.com/api/v1
api_key = your_atoaxis_api_key

• No AtoAxis extension is needed for this editor. AtoAxis implements the WakaTime heartbeat API, so the plugin keeps working as before
• A plugin sends to one server, so from now on new activity goes to AtoAxis instead of WakaTime
• Some plugins cache their settings until the editor restarts. If nothing arrives, restart the editor once
• VS Code users can also switch to the first-party AtoAxis extension, which adds AI hook setup

Edit and save a file in any project, then open Import WakaTime history in the dashboard and choose Check heartbeat and project. It shows today’s heartbeat count, the time of the latest heartbeat and the projects seen today.

• If the latest heartbeat is older than your test edit, check the plugin log and restart the editor
• Reading code without editing, saving or switching files produces no heartbeat by design
• The Overview page shows the same total once the first heartbeat has landed

Create the export at wakatime.com/settings, or through the WakaTime API. Choose the export of heartbeats, not daily summaries: a summary cannot be turned back into a timeline, so the importer rejects it.

POST https://wakatime.com/api/v1/users/current/data_dumps
{ "type": "heartbeats" }

WakaTime prepares the file in the background and gives each export an expiry date, so download it once it is ready. Keep the JSON file as it is; there is no need to edit or split it yourself.

Open Import WakaTime history in the dashboard, choose the JSON file and select Review and import history. The browser splits a large export into chunks, strips fields the import does not use, and uploads the chunks in order.

• Interrupted? Select the same file again and the import resumes from the chunks already received
• Importing the same file twice does not count its time twice: already imported heartbeats are skipped
• When it finishes, the page shows your all-time total before and after, plus how many records were skipped and why
• A small export, up to 1 MiB and 10,000 heartbeats, can also go through Settings → Maintenance

Your old and new activity now sit on one timeline, and every account keeps its complete history rather than a recent window. A few things behave differently from WakaTime, and it is better to know them before you compare totals.

• Imported AI work stays AI but has no agent name: a WakaTime export shows that AI was involved, not which tool, so AtoAxis does not guess one
• Two checkouts of one repository may appear as two projects; join them under Settings with project rules or a manual merge
• AI hooks for Claude Code, Codex CLI, Gemini CLI, Kilo Code and Kimi Code CLI are set up separately from the WakaTime plugin
• To go back, delete the api_url line and put your WakaTime key back in api_key. Nothing in either account is lost