Transporter Gets MongoDB Data Into Elasticsearch

Note: Since this article was written, the hosted version of the Transporter has been taken offline while we re-engineer it to better suit the workloads it was given. The open source version of Transporter is available if you want to use the same technology in the cloud.

If you've been wondering how to move your data in your Compose MongoDB databases into our new hosted Elasticsearch service, then stop wondering as the next stage in our Elasticsearch development has just arrived. We've just brought online, in beta, the first Compose Transporter.


Transporter is a new element in the Compose stack which can transport your data from MongoDB to Elasticsearch from the Compose dashboard. You simply point the Transporter at the MongoDB database and collection you want to transport from, and the ElasticSearch index and type you want to import to, select how you want it to be mapped and start it up.

An optional step is the transformation. You can add a JavaScript transformation function to your Transporter configuration. Each transported document is then fed to this transformation function which creates the document to be inserted into Elasticsearch. We automatically define this function to copy over all elements of the MongoDB document for importing into Elasticsearch, in the same way the Transporter copies data with no function set. You can then override it with your own definition allowing you to remap, filter and perform other changes to the data ready for your Elasticsearch analytics. We'll have an article covering the more details of Transporter transformation next week.

Transporter Screenshot

The Transporter has been created to solve a transitional issue for Elasticsearch users. Traditionally, Elasticsearch has used river-plugins to import data but these are not only insecure, running arbitrary code within the database instance, but can also degrade performance, as that arbitrary code doesn't work in tight synchronization with the database code. Elasticsearch is getting rid of river support and plan to move data import over to Logstash. At Compose, we don't want you to wait and have been developing a solution to the data import issue as part of our Elasticsearch engineering. Thats why we are able to bring you an beta release of Transporter now.

The first iteration of Transporter is a bulk transfer tool and we charge only $0.0125 per hour of run time per run, rounding up to the hour on each run. That makes it economical as well as easy. This pricing is based on the capabilities of our current Transporter. Future iterations will support continuous data streaming and MongoDB to MongoDB transportation.

If you want to start using the Transporter now, head over to your Elasticsearch dashboard, and select Transporter from the menu of options. If you have any questions about how to use Transporter, drop a mail to

Dj Walker-Morgan
Dj Walker-Morgan was Compose's resident Content Curator, and has been both a developer and writer since Apples came in II flavors and Commodores had Pets. Love this article? Head over to Dj Walker-Morgan’s author page to keep reading.

Conquer the Data Layer

Spend your time developing apps, not managing databases.