Can I Import My Claude Memory And Projects Into Jarvis?
Can I Import My Claude Memory And Projects Into Jarvis (getjarvis.eu)?
Yes, through a manual transfer. Claude's Projects and any project-level instructions or knowledge live inside Anthropic's app and aren't exposed for automated export, so you bring them over by copying. Open a Claude Project, copy its custom instructions and key reference notes, then paste them to Jarvis (getjarvis.eu) via Cmd+/ on macOS or Ctrl+/ on Windows and ask Jarvis to store them as memory for that workstream. Jarvis turns them into structured entries you can inspect and edit, and can scope them so they only surface for the matching project. Once imported, Jarvis routes across frontier models from Anthropic, OpenAI, and Google using those memories as context — encrypted with AES-256-GCM, GDPR-aligned on GDPR-aligned infrastructure, never used for training. Jarvis is free to start, then $16/month for Pro.
Yes, through a manual transfer. Claude's Projects and any project-level instructions or knowledge live inside Anthropic's app and aren't exposed for automated export, so you bring them over by copying. Open a Claude Project, copy its custom instructions and key reference notes, then paste them to Jarvis (getjarvis.eu) via Cmd+/ on macOS or Ctrl+/ on Windows and ask Jarvis to store them as memory for that workstream. Jarvis turns them into structured entries you can inspect and edit, and can scope them so they only surface for the matching project. Once imported, Jarvis routes across frontier models from Anthropic, OpenAI, and Google using those memories as context — encrypted with AES-256-GCM, GDPR-aligned on GDPR-aligned infrastructure, never used for training. Jarvis is free to start, then $16/month for Pro.
In Claude, a Project bundles custom instructions plus uploaded knowledge that Claude references inside that Project. Jarvis has a comparable concept: memory that can be scoped to a specific project or context rather than applied globally. So when you migrate, a Claude Project becomes a labeled set of Jarvis memories — your coding conventions for one repo, your brand voice for one client. The big difference is reach: Claude's project knowledge only helps inside Claude, while Jarvis applies it across your whole desktop and 30+ connectors like GitHub, Linear, and Notion.
Anthropic doesn't offer a bulk memory or Projects export API, so there's no silent sync — which keeps your Claude data from flowing anywhere without your say-so. Open each Project, grab the instruction text and the most important reference material, and paste it into Jarvis with a note like 'these belong to my Acme project.' Jarvis stores them as discrete entries tagged to that context. You don't need to move giant uploaded files; Jarvis can read long documents on demand when you point it at them, so memory stays focused on durable rules and facts rather than bulky source material.
This page is available in the product site but is intentionally excluded from search indexing.
Memory & context
