Moving from Neo4j? Start with an evaluation.

Evaluate LightningDB with a copy of your Neo4j data. Import the graph, test the queries your application uses, and plan the move before changing production.

Migration steps Discuss your migration
View the command
# One-command migration helper
./build/graphdb cutover \
  --bolt neo4j://neo4j.prod:7687 \
  --dump /backup/neo \
  --host 20.1.2.3

Import. Validate. Plan the switch.

Use the migration tools to import a copy of your graph. Validate query support and application behavior before choosing a production migration plan.

  1. Export your Neo4j data

    Export nodes and relationships in the format neo4j-admin database import natively consumes. Aura and APOC exports can be JSONL instead.

  2. Import into LightningDB

    Import the exported data and save it as a LightningDB database file:

    View the command
    ./build/graphdb migrate --from /backup/neo --out data/migrated.gdb
  3. Test your application

    Start the imported database locally. Test your Cypher queries through /v1/query and AI retrieval through /v1/rag. Check your application against the supported query subset:

    View the command
    ./build/graphdb serve --db data/migrated.gdb --port 7475

Contact our team to discuss your migration requirements.

Supported import formats.

The import tools accept the following CSV and JSONL layouts for nodes and relationships.

FORMAT nodes.csv & rels.csv

The standard layout neo4j-admin database import consumes and graphdb generate --out produces.

FORMAT nodes.csv & relationships.csv

Identical schema columns, recognizing Neo4j’s longer filename variant automatically.

FORMAT nodes.jsonl & rels.jsonl

One JSON object per line, matching the exact shape emitted by APOC and Neo4j Aura tooling.

Import from a running Neo4j database.

Use migrate --bolt to connect to Neo4j over its Bolt protocol and copy the graph into a LightningDB database file.

The source database remains available while you evaluate the imported copy.

View the command
# Stream live from Bolt server
pip install neo4j
./build/graphdb migrate --bolt bolt://127.0.0.1:7687 \
  --user neo4j --password graphdb-bench \
  --out data/migrated.gdb

Plan your migration with your team.

Review query compatibility, performance, and deployment requirements before moving production traffic.

Discuss your migration View Comparison
View the command
# Execute migration helper
bash scripts/cutover_from_neo4j.sh \
  neo4j://neo4j.prod:7687 /backup/neo GRAPHDB_HOST