Sharding: Migration

Export is a one-time operation that dumps the current contents of the database into a .ravendbdump file.
The exported dump file of either a sharded or a non-sharded database can then be imported into a sharded database, that will distribute the data between its shard.

• Exporting can be done via code or Studio.
• Importing can be done via code or Studio.

• Read about export and import in a sharded database here.

• Data can also be imported from backup files.
  A backup of a non-sharded database can be imported into an existing sharded database.
  The imported data will be added to the sharded database and distributed between the shards.
  

  Note that this opposes restoring a non-sharded database, which can only create a new non-sharded database but not create a sharded database or add its data to an existing database.
  

RavenDB backups are periodic operations, implemented by ongoing tasks that routinely save either a full copy of the database or an incremental delta of data changes made since the last backup.

To migrate data from a non-sharded database to a sharded one, backup files made for a non-sharded database can be imported into a new or an existing sharded database.

External replication is an ongoing task that keeps a live replica of its database's data on another database.
The task keeps the two databases in sync by updating the destination database with any deletion, addition, or modification made in the origin database's data.

An external replication task can run on a non-sharded database, and create a live replica of its data on a sharded database.
The destination (sharded) database will distribute incoming data among its shards.
The sharded database can be kept and tested in a controlled environment as long as necessary, as the original database keeps on serving its users. When all is ready, the new database can be moved into production.