# Complete MySQL database to Elasticsearch

**URL:** <https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266>\
**Category:** Elasticsearch\
**Created:** [July 31, 2018, 2:30am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266 "2018-07-31T02:30:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 31, 2018, 9:20am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266/4 "2018-07-31T09:20:14Z")

</div>

I don't think you are bothering anyone here and @warkolm's answer is accurate.  
We are happy to help on any specific question you might have but we can't really answer a so generic one which is basically "how do I move from a relational model to a document oriented model?" and "how do I move from a datastore to a search engine?".

One silly answer would be: just index each table as a new index. But you will see that does not work well with the search engine and document oriented paradigm.

So, you have to ask yourself some questions that I covered at: [Which is the best way to index the data from relational database](https://discuss.elastic.co/t/which-is-the-best-way-to-index-the-data-from-relational-database/141870/2)

Then, when you know more about your use case, features, data model, etc. we can help about sizing and other stuff. Feel free to ask.

---

_[View the full topic](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266)._