> ## Documentation Index
> Fetch the complete documentation index at: https://docs.recallium.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Recallium Community

> 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.

## Before you begin

* A running Recallium Community instance with access to its dashboard
* Recallium Cloud access. Sign in at [app.recallium.ai](https://app.recallium.ai).
* Node.js 22 or later, to run the installer in the last step

<Note>
  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.
</Note>

## Export from Recallium Community

<Steps>
  <Step title="Open Import/Export in the Community dashboard">
    Open your Community dashboard, by default at `http://localhost:9001`. Go to **Projects** and click **Import/Export** at the top right.

    <Frame caption="The Community dashboard: the Projects page with the Import/Export button at the top right.">
      <img src="https://mintcdn.com/recallium/XUHdkSySAqfhmg73/images/migrate-from-community/export-step-1.jpg?fit=max&auto=format&n=XUHdkSySAqfhmg73&q=85&s=7684cbde94840b41981e7c36c6ba404f" alt="The Recallium Community dashboard on the Projects page, with the Import/Export button highlighted at the top right" className="w-full" width="2603" height="1153" data-path="images/migrate-from-community/export-step-1.jpg" />
    </Frame>
  </Step>

  <Step title="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.

    <Frame caption="The Data Management dialog on the Export tab: scope All Projects, empty dates, and the export preview.">
      <img src="https://mintcdn.com/recallium/XUHdkSySAqfhmg73/images/migrate-from-community/export-step-2.jpg?fit=max&auto=format&n=XUHdkSySAqfhmg73&q=85&s=3b72d54ac1dc106214be6f2bacc8171f" alt="The Data Management dialog on the Export tab, showing the All Projects scope, empty From and To dates, a preview of record counts and size, and the Export button" className="w-full" width="909" height="989" data-path="images/migrate-from-community/export-step-2.jpg" />
    </Frame>

    <Tip>
      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.
    </Tip>
  </Step>
</Steps>

## Import into Recallium Cloud

<Steps>
  <Step title="Open Import/Export in Recallium Cloud">
    Sign in at [app.recallium.ai](https://app.recallium.ai). Go to **Projects** and click **Import/Export**.

    <Frame caption="Recallium Cloud: the Projects page with the Import/Export button at the top right.">
      <img src="https://mintcdn.com/recallium/XUHdkSySAqfhmg73/images/migrate-from-community/import-step-3.jpg?fit=max&auto=format&n=XUHdkSySAqfhmg73&q=85&s=12de848bb7ffc28e3929629a1d52e9d0" alt="The Recallium Cloud Projects page, with the Import/Export button highlighted at the top right" className="w-full" width="1794" height="903" data-path="images/migrate-from-community/import-step-3.jpg" />
    </Frame>
  </Step>

  <Step title="Import the zip file">
    On the **Import** tab, click **Select ZIP File to Import**, choose the file you exported, and click **Import**.

    <Frame caption="The Data Management dialog on the Import tab with the Select ZIP File to Import control.">
      <img src="https://mintcdn.com/recallium/XUHdkSySAqfhmg73/images/migrate-from-community/import-step-4.jpg?fit=max&auto=format&n=XUHdkSySAqfhmg73&q=85&s=f0a4c4251289cb14ac58e3143a3dd7c4" alt="The Data Management dialog on the Import tab, showing the Select ZIP File to Import button and the Import button" className="w-full" width="1185" height="360" data-path="images/migrate-from-community/import-step-4.jpg" />
    </Frame>

    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.
  </Step>
</Steps>

## Connect your agents to Recallium Cloud

<Steps>
  <Step title="Run the installer">
    The installer finds the coding agents on your computer, signs you in to Recallium Cloud once, and connects each agent.

    ```bash theme={null}
    npx -y recallium@latest install
    ```

    For each screen of the installer, see the [Quickstart](/quickstart). To connect Claude Desktop or ChatGPT, see [Configure Recallium for chat apps](/guides/configure-chat-apps).
  </Step>

  <Step title="Check that your agents find the imported projects">
    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:

    ```text theme={null}
    Where did we leave off?
    ```

    If a repository's name differs from the imported project name, map it once:

    ```bash theme={null}
    git config --local recallium.projectName <project-name>
    ```

    See [Map a repository to an existing project](/concepts/projects-and-workstreams#map-a-repository-to-an-existing-project).
  </Step>

  <Step title="Remove the Community connection">
    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:

    ```bash theme={null}
    npx -y recallium@latest status
    ```
  </Step>
</Steps>

## What moves and what does not

| Moves to Recallium Cloud | Stays on Recallium Community |
| - | - |
| Projects and project links | Uploaded documents |
| Memories, with their tags and relationships | Tasks |
| Thinking sequences | Links between memories and code files |
| Sessions | |
| Rules | |

Upload your documents again in Recallium Cloud after the import. Imported memories count toward your plan's memory allowance.

## Troubleshooting

### The import fails with a file size error

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.

### My agent still saves to the Community server

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.

### My repository shows up as a new, empty project

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](mailto:support@recallium.ai).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.