When the command-line utility and the GUI client stop being enough

MongoToFile » Use cases » MongoToFile or mongoexport

Download MongoToFile Free Trial »     Buy MongoToFile Now »

The situation

There are two free ways to get data out of MongoDB, and both are good at what they do. The official mongoexport utility is right there in the shell and handles JSON and CSV. The GUI client's own export button writes a file from whatever is on screen.

They stop being convenient at the same set of edges: a format that is not JSON or CSV, a document that has to be flattened before it is readable, dozens of collections, a task that has to run by itself at night, or a machine where the shell and the client are simply not part of the plan.

Where the line is

The export dialog of a MongoDB GUI client, one of the alternatives

Both routes keep the data on your machine, and neither needs a cloud service or a copy of the data somewhere else. Choosing between them is about formats, repetition and who is doing the work - not about where the data goes.

What it will not do

Related

The exports themselves: collection to file, query to file, collections to files. Nested documents: flat files from nested fields. Repeating it: on a schedule, command line. The other direction: FileToMongo.