# Memory MCP Migration Tool
Migrate knowledge graph data between JSONL and SQLite storage formats for the Memory MCP server.
## Overview
This standalone tool allows you to convert your existing JSONL knowledge graph to SQLite format (or vice versa) when upgrading to SQLite storage for improved performance with large datasets.
## Installation
```bash
cd tools/migrate-from-jsonl-to-sqlite
npm install
```
## Usage
### Using Node.js
```bash
# Build TypeScript first
npm run build:ts
# Run with Node.js
node dist/migrate-from-jsonl-to-sqlite.js --from memory.jsonl --to memory.db
# Or use npm start
npm start -- --from memory.jsonl --to memory.db
```
### Build Executable
```bash
# Build executable using pkg (smaller binary than bun)
npm run build
# Creates migrate-from-jsonl-to-sqlite.exe
./migrate-from-jsonl-to-sqlite.exe --from memory.jsonl --to memory.db
```
## Arguments
| Argument | Short | Description |
|----------|-------|-------------|
| `--from` | `-f` | Source file path (JSONL or SQLite) |
| `--to` | `-t` | Target file path (JSONL or SQLite) |
| `--verbose` | `-v` | Show detailed progress |
| `--help` | `-h` | Show help message |
## File Extensions
The tool automatically detects the storage format based on file extension:
| Format | Extensions |
|--------|------------|
| JSONL | `.jsonl`, `.json` |
| SQLite | `.db`, `.sqlite`, `.sqlite3` |
## Examples
```bash
# Basic migration
./migrate-from-jsonl-to-sqlite.exe memory.jsonl memory.db
# Using named arguments
./migrate-from-jsonl-to-sqlite.exe --from /path/to/memory.jsonl --to /path/to/memory.db
# Verbose output shows detailed progress
./migrate-from-jsonl-to-sqlite.exe -f memory.jsonl -t memory.db -v
```
## Output
```
š Loading source data...
Found 150 entities and 75 relations
š¾ Writing to target...
ā
Verifying migration...
āØ Migration completed successfully!
Migrated 150 entities and 75 relations
From: memory.jsonl (jsonl)
To: memory.db (sqlite)
```
## Notes
- **Data Preserved**: All entities, relations, and metadata are fully preserved during migration
- **Verification**: The tool automatically verifies data integrity after migration
- **Overwrite**: If the target file exists, it will be overwritten
- **Separate Files**: Saved searches and tag aliases are stored in separate files and are NOT migrated by this tool
## When to Use SQLite
| Use Case | Recommendation |
|----------|----------------|
| Small graphs (<1000 entities) | JSONL (default) |
| Large graphs (10k+ entities) | SQLite |
| Need ACID transactions | SQLite |
| Want to inspect data manually | JSONL |
| Debugging | JSONL |
## Configuring Memory MCP for SQLite
After migrating, configure the Memory MCP server to use SQLite:
```json
{
"mcpServers": {
"memory": {
"command": "node",
"args": ["/path/to/memory-mcp/src/memory/dist/index.js"],
"env": {
"MEMORY_STORAGE_TYPE": "sqlite",
"MEMORY_FILE_PATH": "/path/to/memory.db"
}
}
}
}
```
## Development
```bash
# Install dependencies
npm install
# Build TypeScript
npm run build:ts
# Run with Node.js
node dist/migrate-from-jsonl-to-sqlite.js --help
# Build executable (uses pkg for smaller binaries)
npm run build
```
