> ## Documentation Index
> Fetch the complete documentation index at: https://docs.falkordb.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> FalkorDB is a graph database that speaks the Redis protocol. Queries are issued as OpenCypher through the GRAPH.QUERY and GRAPH.RO_QUERY commands, not over Bolt or a SQL connection.
> FalkorDB implements a subset of OpenCypher with proprietary extensions. Do not assume Neo4j-only syntax or procedures are available — check /cypher/cypher-support and /cypher/known-limitations before using a clause.
> FalkorDB is the successor to RedisGraph, but they are separate products. Do not present RedisGraph commands, versions, or limitations as current FalkorDB behavior.
> Use the official clients listed in /getting-started/clients rather than generic Redis or Neo4j drivers, and prefer the language the user is already working in.
> Configuration parameters are set with GRAPH.CONFIG SET or at startup; cite the exact parameter name from /getting-started/configuration rather than inventing one.
> This site covers four products: FalkorDB (core), FalkorDB Cloud, FalkorDB Enterprise, and the GraphRAG SDK. Name which one an answer applies to, since setup and operations differ.

# Migration

> Migrate data to FalkorDB from RedisGraph, Neo4j, Kuzu, RDF-based systems, and online SQL sources. Step-by-step guides for seamless data and application transitions with schema discovery.

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](/operations/migration/redisgraph-to-falkordb): Migrate seamlessly from RedisGraph to FalkorDB using RDB files.
* [Neo4j to FalkorDB](/operations/migration/neo4j-to-falkordb): Export data from Neo4j and import it into FalkorDB using CSV files.
* [Kuzu to FalkorDB](/operations/migration/kuzu-to-falkordb): Transfer your Kuzu database to FalkorDB with automated schema discovery.
* [RDF to FalkorDB](/operations/migration/rdf-to-falkordb): Migrate RDF (TTL) data to FalkorDB with schema extraction and CSV export.
* [SQL Sources to FalkorDB (Online Migration)](/operations/migration/sql-to-falkordb): Online migration and incremental sync from SQL sources (PostgreSQL, Snowflake, Databricks) into FalkorDB.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="What tool should I use for loading large datasets?">
    Use the [FalkorDB Rust Loader](https://github.com/FalkorDB/FalkorDB-Loader-RS) for best performance. It uses async operations, batch processing, and memory-efficient streaming from CSV files.
  </Accordion>
</AccordionGroup>