Migration
The Migration section provides comprehensive guides for migrating your data to FalkorDB from other systems. Whether you’re moving from RedisGraph, 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
- RedisGraph to FalkorDB: Migrate seamlessly from RedisGraph to FalkorDB using RDB files.
- Neo4j to FalkorDB: Export data from Neo4j and import it into FalkorDB using CSV files.
- Kuzu to FalkorDB: Transfer your Kuzu database to FalkorDB with automated schema discovery.
- RDF to FalkorDB: Migrate RDF (TTL) data to FalkorDB with schema extraction and CSV export.
- SQL Sources to FalkorDB (Online Migration): Online migration and incremental sync from SQL sources (PostgreSQL, Snowflake, Databricks) into FalkorDB.
Frequently Asked Questions 4
Which migration path should I choose for my existing database?
Use the RedisGraph guide for RDB file migration, 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.
Will my queries work the same after migration?
FalkorDB uses Cypher query language. Queries from Neo4j and RedisGraph should work with minimal changes. For SQL and RDF sources, you will need to write new Cypher queries suited to the graph model.
Can I migrate incrementally without downtime?
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.
What tool should I use for loading large datasets?
Use the FalkorDB Rust Loader for best performance. It uses async operations, batch processing, and memory-efficient streaming from CSV files.