Skip to main content
The Migration section provides comprehensive guides for migrating your data to FalkorDB from other systems. Whether you’re replacing an end-of-life RedisGraph deployment, moving from Neo4j, Kuzu, RDF-based data stores, or migrating and continuously syncing from SQL sources, these step-by-step guides will help you seamlessly transition your data and applications to FalkorDB.

Topics in This Section

Frequently Asked Questions

Use the RedisGraph guide if you are replacing an end-of-life RedisGraph deployment — it is an RDB file restore with no data conversion. Use the Neo4j guide for CSV-based export/import, Kuzu guide for automated schema discovery, RDF guide for TTL files, and SQL guide for online sync from relational databases.
FalkorDB uses Cypher query language. Queries written for RedisGraph run unchanged in the vast majority of cases, since FalkorDB is the RedisGraph successor and keeps the same command API. Review Cypher support and known limitations for clauses that may need changes. Queries from Neo4j should work with minimal changes. For SQL and RDF sources, you will need to write new Cypher queries suited to the graph model.
Yes, for SQL sources. The DM-SQL-to-FalkorDB loaders support daemon mode for continuous incremental sync. For other sources (Neo4j, Kuzu, RDF), migration is typically a one-time batch operation.
Use the FalkorDB Rust Loader for best performance. It uses async operations, batch processing, and memory-efficient streaming from CSV files.