Skip to main content
RedisGraph reached end-of-life on January 31, 2025. It is no longer maintained, no new patches are released, and RedisGraph commands are disabled on Redis Enterprise Cloud. FalkorDB is the direct successor to RedisGraph, built and maintained by the engineers behind the original RedisGraph project. It keeps the same sparse-matrix and GraphBLAS architecture, the same GRAPH.* command API over the Redis protocol, and reads your existing RedisGraph RDB files as-is — so moving your data off a deprecated RedisGraph deployment is a restore, not a conversion.
Looking for the fastest path off RedisGraph? Jump straight to the migration steps. Your dump.rdb loads into FalkorDB without conversion.

​
Why FalkorDB Is the RedisGraph Alternative

  • Same team, same lineage. FalkorDB continues the RedisGraph codebase and its linear-algebra query engine, led by the people who created it.
  • Same command API. GRAPH.QUERY, GRAPH.RO_QUERY, GRAPH.EXPLAIN, GRAPH.PROFILE, GRAPH.DELETE, and GRAPH.LIST behave as they did in RedisGraph. See the command reference, and check Cypher support and known limitations for the clauses you rely on.
  • Zero-conversion data migration. FalkorDB loads RedisGraph RDB snapshots directly. There is no export/import pipeline, no CSV round-trip, and no ETL job.
  • Little to no application rewrite. Code that issues GRAPH.QUERY and GRAPH.RO_QUERY over the Redis protocol generally works as-is. The community clients originally built for RedisGraph are not officially tested or supported, so plan to move to the official FalkorDB clients for Python, JavaScript, Java, Go, Rust, PHP, and C#.
  • Actively developed. Ongoing releases add capabilities RedisGraph never shipped, including vector indexes, centrality, community and flow algorithms, UDFs, and GraphRAG tooling.

​
RedisGraph vs. FalkorDB

​
Migration Steps

FalkorDB is fully compatible with RedisGraph RDB (Redis Database) files, making migration straightforward.

​
Step 1: Create RDB Snapshot from RedisGraph

Create a snapshot of your RedisGraph database using the SAVE or BGSAVE command:
This creates a dump.rdb file in your Redis data directory.

​
Step 2: Load RDB File into FalkorDB

​
Using Docker

When using the FalkorDB Docker image, mount your RDB file and configure Redis to load it:
Make sure to place the RDB file in the directory mapped to the Docker volume. For FalkorDB Cloud, follow the cloud provider’s instructions for uploading and restoring from an RDB file. Important: Ensure your dump.rdb file is placed in the directory mapped to the Docker volume ($(pwd) in the example above).

​
Using FalkorDB Cloud

For FalkorDB Cloud deployments, follow the cloud provider’s instructions for uploading and restoring from an RDB file.

​
Verification

After loading the RDB file, verify your data:

​
Best Practices

  • Verify RDB Integrity: Check the RDB file integrity before and after transfer
  • Plan for Downtime: Consider downtime requirements and data consistency during migration
  • Test First: Always test the migration in a staging environment before production
  • Backup: Keep backups of both the source RedisGraph data and the RDB file
  • Monitor: After migration, monitor FalkorDB performance and verify queries work correctly

​
After You Migrate

Once your graphs are running on FalkorDB, these are the capabilities to pick up next — most of them have no RedisGraph equivalent:

​
Frequently Asked Questions

Yes. Redis announced the RedisGraph end-of-life in July 2023. End of support was January 31, 2025, the GitHub repository is no longer maintained, and RedisGraph commands are disabled on Redis Enterprise Cloud. See the official EOL announcement.
FalkorDB. It is the successor to RedisGraph, built by the engineers behind the original project on the same GraphBLAS sparse-matrix engine. It keeps the GRAPH.* command API and the Cypher dialect you already use, reads your existing RDB files, and is actively developed — so migrating needs no data conversion, and in the vast majority of cases no query changes. Review Cypher support and known limitations for the clauses you rely on.
In practice, at the Redis protocol and RDB level, yes: FalkorDB exposes the same GRAPH.QUERY and GRAPH.RO_QUERY commands and loads RedisGraph RDB snapshots directly. Most deployments can change the connection endpoint, but RedisGraph-derived client libraries are not officially tested or supported; use the official FalkorDB clients. Review Cypher support and known limitations if you rely on unusual clauses.
Yes. FalkorDB is fully compatible with RedisGraph RDB files. Simply load your existing dump.rdb into FalkorDB and your graphs will be available immediately.
For a consistent snapshot, use BGSAVE which creates a background snapshot without blocking the server. For absolute consistency, use SAVE which blocks but ensures no writes during the snapshot.
Yes. Export an RDB file from your RedisGraph Cloud instance, then follow your FalkorDB Cloud provider instructions for uploading and restoring from the RDB file.
In most cases, yes. FalkorDB exposes the same GRAPH.QUERY and GRAPH.RO_QUERY commands over the Redis protocol, so application code written against them generally needs no changes. The community client libraries originally built for RedisGraph may keep working through that protocol compatibility, but they are not officially tested or supported — use the official FalkorDB clients, which are actively maintained.
Usually not. FalkorDB implements the same openCypher dialect RedisGraph did, plus extensions, so queries written for RedisGraph run unchanged in the vast majority of cases. Check Cypher support and known limitations if you depend on unusual clauses.
You can, but it is unsupported, unpatched software: no security fixes, no bug fixes, and no compatibility work for newer Redis versions. Migrating to FalkorDB restores an actively maintained path without changing your data or queries.