Migrate between editions

Moving between editions, or getting off Ideafy entirely. Ideafy has two editions — Public and Team — so migration is straightforward in either direction.

Public → Team

See Data portability. Short version: export from Public, import into Team, link the project to a team if you want pool sync.

Why migrate:

• You're hiring teammates and want them to see the work
• You want the pool, my-queue, notifications, and the rest of the team features
• You want cloud sync as a backup for work that's currently local-only

Your cards, conversations, screenshots, and plan/test/opinion content come across intact. Pool links are dropped (they didn't exist in Public) — you re-link the project to a team on the Team side.

Team → Public

Less common, but supported. Export from Team, import into Public. Team-only fields (pool links, team assignment) are dropped; everything else survives.

Why migrate:

• The team dissolved and you want a local-only version of your work
• You're scaling down to a solo workflow
• You want a free-tier backup of cards you created inside a paid edition

Anything → uninstall

1. Quit Ideafy
2. Drag Ideafy.app to the Trash
3. Remove local data: rm -rf ~/Library/Application\ Support/ideafy
4. Optional: remove per-project Ideafy installs by deleting .claude/skills/ideafy.md, .claude/skills/human-test.md, .claude/skills/product-narrative.md, and the ideafy entry in each project's .claude/settings.json (or .mcp.json)

If you were signed in to the Team edition and want to delete your cloud account as well, do it before uninstalling — the account deletion flow needs a working app. Settings → Account → Delete account (7-day grace, cancelable during that window).

Keeping cards when switching machines

If you're moving from one Mac to another, the easiest path:

• Public: export from the old Mac, import on the new Mac
• Team: sign in on the new Mac. Cards on team-linked projects carry across automatically through Supabase. For unlinked (solo) projects, use the export/import flow per project

In both cases, remember to also bring your project folders (the git repos) across — Ideafy exports card metadata, not source code.

Data directory map

Useful to know when debugging migrations:

Prev: Data portability Next: Team overview Up: User guide index