Import Supermemory memories into Remnic

What The Importer Accepts

The Supermemory importer accepts JSON. The top level can be a flat array of memory objects, or an object with a memoryEntries, memories, results, or data array.

For each record, Remnic looks for memory text in content, memory, summary, or title. It preserves IDs, timestamps, container tags, source metadata, and the source file path when those fields are available.

Install The Optional Importer

The importer is separate from the base CLI so normal Remnic installs stay small. Install it beside the CLI you already use.

npm install -g @remnic/cli
npm install -g @remnic/import-supermemory

If you run Remnic from a project instead of globally, install both packages in the same project.

pnpm add @remnic/cli @remnic/import-supermemory

Prepare The Export

If your Supermemory export spans multiple API pages, combine the pages into one JSON file before importing. A flat array works, or you can wrap the array in a memories key.

{
  "memories": [
    {
      "id": "mem_123",
      "content": "The user prefers short release notes.",
      "updatedAt": "2026-05-05T12:00:00Z",
      "containerTags": ["product"]
    }
  ]
}

Dry Run First

Run the importer in dry-run mode before writing memories. This checks that the export parses and reports how many records Remnic can import.

remnic import --adapter supermemory \
  --file ./supermemory-memories.json \
  --dry-run

Run The Import

When the dry-run count looks right, run the same command without --dry-run.

remnic import --adapter supermemory \
  --file ./supermemory-memories.json

Imported records are marked with sourceLabel: "supermemory" and metadata.kind: "supermemory_memory", so you can audit or filter migrated memories later.

Check The Result

After importing, query for a known memory from the export and inspect the local store if you want to confirm provenance.

remnic recall "short release notes"
remnic recall "short release notes" --explain

Remnic stores memories locally under the configured memory directory. The exact path depends on your Remnic config, but the records remain plain files with structured metadata.

Privacy Notes

Parsing and import happen locally. If your Remnic extraction, consolidation, or summarization settings use a remote model provider, imported content may be processed by that provider during normal Remnic memory workflows. Use local model routing or your OpenClaw gateway configuration if the full migration path needs to stay local.

Troubleshooting

• If Remnic says the export has no recognized memory key, wrap the records in { "memories": [...] } or pass a flat JSON array.
• If a record is skipped, confirm it has a non-empty content, memory, summary, or title field.
• If the CLI cannot load the adapter, install @remnic/import-supermemory in the same global or project environment as @remnic/cli.