Migrating to SurrealDB

This section describes how to move data into SurrealDB: from other databases, from older SurrealDB versions, and from files or streams (for example CSV, JSON Lines, or Kafka). Use the subsections for the path that matches your source.

In this section

Other databases, such as PostgreSQL, MySQL, MongoDB, Neo4j and Snowflake, and files and streams, such as CSV, JSON Lines and Kafka, move into SurrealDB through Surreal Sync. An older SurrealDB reaches a newer one by following the upgrade guide for each version. A database that Surreal Sync does not cover can be exported as JSON and loaded with surreal import. Other databases, such as PostgreSQL, MySQL, MongoDB, Neo4j and Snowflake, and files and streams, such as CSV, JSON Lines and Kafka, move into SurrealDB through Surreal Sync. An older SurrealDB reaches a newer one by following the upgrade guide for each version. A database that Surreal Sync does not cover can be exported as JSON and loaded with surreal import.

Upgrading - how to upgrade, and the guide for each version change: 1.x to 2.x, 2.6 to 2.7, 2.x to 3.x, 3.2 to 3.3 and 3.x to 4.0
From files and streams - load data held in files or arriving as a stream
From other databases - move across from another database engine

Moving between SurrealDB Cloud instances

A Free instance moves to a paid instance type in place, from the Compute tab of its settings, with no migration. See Scaling.

Moving from Start to Scale, or to another region, needs a new instance. Deploy it, then restore a backup or import an export into it.