Plan a migration
What to decide before moving a MongoDB database to TeselaDB.
Moving from MongoDB to TeselaDB means copying the data with MongoDB's tools and changing the connection string. Before you start, decide how and when you copy the data. Have the way back planned as well.
How it works
You can migrate in three ways, and the one you choose depends above all on how long you can stop your application's
writes while you copy the data from MongoDB to TeselaDB with mongodump and mongorestore, which are the tools of all
three.
With downtime
You stop writes, copy with mongodump and mongorestore and change the string. It is the simplest.
Without downtime
You copy with --oplog and apply at the end the operations that happened during the copy with --oplogReplay.
In parts
You move one database or one application at a time with its own connection string, so what you have not moved yet keeps working against MongoDB while you copy the next part.
What it means for your application
Your application does not change its code. Its behaviour does change in what Differences with MongoDB lists. Check that list before moving the traffic, above all the order of a find without sort.
Limits
What is deprecated in MongoDB 9.0 does not exist in TeselaDB. If your application uses something deprecated, change it before migrating.