Move your projects and memories from a self-hosted Recallium Community instance to Recallium Cloud with one export and one import
Your projects and memories move from Recallium Community to Recallium Cloud as one zip file. Export from the Community dashboard, import in Recallium Cloud, then point your agents at Cloud. Nothing is deleted from your Community instance. It keeps running until you stop it.
Node.js 22 or later, to run the installer in the last step
Recallium Cloud accepts uploads of up to 100 MB. The export dialog shows the estimated size before you export. If your export is larger, use the date range to export in parts and import each part in turn.
Open your Community dashboard, by default at http://localhost:9001. Go to Projects and click Import/Export at the top right.
The Community dashboard: the Projects page with the Import/Export button at the top right.
2
Export all projects
On the Export tab, keep the scope at All Projects and leave both dates empty to export everything. The preview shows how many projects, memories, and sessions the export contains, and its estimated size.Click Export and save the zip file.
The Data Management dialog on the Export tab: scope All Projects, empty dates, and the export preview.
To move one project at a time, change the scope to that project. Each export is a separate zip file that you import on its own.
Sign in at app.recallium.ai. Go to Projects and click Import/Export.
Recallium Cloud: the Projects page with the Import/Export button at the top right.
2
Import the zip file
On the Import tab, click Select ZIP File to Import, choose the file you exported, and click Import.
The Data Management dialog on the Import tab with the Select ZIP File to Import control.
Your projects appear in Recallium Cloud under the same names. If a project with the same name already exists in your Cloud account, the imported memories are added to it. Importing the same file twice does not create duplicate projects.A large import takes a few minutes to finish indexing. Memories become searchable as indexing completes.
Recallium derives the project name from the Git repository, so your agents find the imported projects the same way they did before. Open a repository in your agent and ask:
Where did we leave off?
If a repository’s name differs from the imported project name, map it once:
Each agent now has two Recallium connections: the Community server and Recallium Cloud. Remove the Community entry from each agent so that new memories go to Cloud. You can keep both connected while you compare, but your agents then save to whichever server they pick.To see which server each agent uses, run:
Recallium Cloud accepts uploads of up to 100 MB. Export in parts by setting a From Date and To Date in the export dialog, then import each part. Each import adds to the projects that are already there.
The agent still has the Community MCP entry, and it picked that one. Remove the Community entry from the agent’s MCP configuration, then restart the agent. Run npx -y recallium@latest doctor to confirm that only the Cloud connection remains.
The repository name does not match the imported project name. Map the repository to the imported project with git config --local recallium.projectName <project-name>, then ask your agent to search again.Questions about a migration: support@recallium.ai.
