Claude Sync

When a company moves its staff from personal Claude accounts to a Team or Enterprise plan, the new accounts start empty. The projects people built, the instructions they refined, and the files they uploaded all stay in the old accounts.

Claude has no way to import Projects. The official data export leaves out the contents of your knowledge files, so it cannot be used to rebuild them.

Most teams end up rebuilding by hand, or they let staff keep working in personal accounts. The second option is common, and it leaves company work sitting in accounts the company does not control.

Claude Sync does the move for you.

Security first

This is the first question most IT teams ask, so here are the answers.

• It runs only on your computer. There is no Claude Sync server. Nothing is sent to Anchor Sprint, OSS Malaysia or anyone else.
• It never sees your password. You sign in to each account on claude.ai's own login page, in a normal browser window.
• No tracking. No analytics, no usage data, no account to create.
• Your old account is only read. Nothing in it is changed or deleted. Nothing already in the new account is edited or deleted either.
• Your data stays in one folder. Everything it downloads is kept in a private folder on your computer. Delete the folder and it is gone.
• You can check all of this. The full source code is public on GitHub, and every release publishes checksums so you can confirm the file you downloaded is the one that was built.

What it moves

• Projects, with their name, description, visibility and instructions
• Knowledge documents, with their full text, and uploaded files exactly as they were
• Artifacts from your chats, added to the matching project and also saved as files on your computer
• Your own skills, with every file in them
• Memory, sent through claude.ai's own memory import

How it works

1. Download. Log in to your old account. Everything is copied to a folder on your computer.
2. Choose. Tick the projects you want to move. Anything named Personal:, Family: or Travel starts unticked.
3. Send. Log in to your new account. Projects are created one at a time.
4. Check. It compares the number of documents and files in the new account against your local copy.

You can stop at any point and carry on later without creating duplicates. After the first move, Scan & sync changes sends only what has changed, which helps when a move runs over several days while people keep working.

A command-line version is included for IT teams that want to script a large move.

What it does not move

• Chat history. claude.ai cannot recreate conversations. The artifacts from those chats are recovered instead.
• Files Claude generated by running code, such as a spreadsheet or slide deck, and published artifact pages.
• Original images. claude.ai does not keep a downloadable original, so the full-size preview is used instead.
• Files larger than 30 MB. These are skipped and listed so you know which ones.

Installing on Windows

The app is not code-signed yet, so the first time you open it Windows shows "Windows protected your PC". This appears for new apps from publishers Windows does not recognise yet. Click More info, then Run anyway. Code signing is being set up through the SignPath Foundation.

If your company blocks unsigned apps, ask IT to allow it or wait for the signed release.

Requirements

Windows 10 or 11, or macOS 10.13 or later, with Google Chrome or Microsoft Edge installed.

Who built it

Anchor Sprint helps Malaysian companies adopt Claude: setting it up, training staff, and managing it once it is running. Moving projects between accounts came up on client after client, so Anchor Sprint built this tool and released it under the MIT licence.

It is published under the OSS Malaysia organisation on GitHub so any company can use it, report problems, and contribute fixes.