# Compass 2.2.0 to Elastic Search 7.2.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [July 4, 2019, 10:00am UTC](https://discuss.elastic.co/t/compass-2-2-0-to-elastic-search-7-2-0/188880 "2019-07-04T10:00:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![easwer](https://avatars.discourse-cdn.com/v4/letter/e/e5b9ba/32.png) [@easwer](https://discuss.elastic.co/u/easwer)\ **Post date:** [July 4, 2019, 10:00am UTC](https://discuss.elastic.co/t/compass-2-2-0-to-elastic-search-7-2-0/188880/1 "2019-07-04T10:00:32Z")
Hi, In our legacy product Compass:2.2.0 is used for searching. Now we are planning to upgrade it to Elastic Search 7.2. Can anyone provide us a few steps or links that can help our cases? We use PostgreSQL, MySQL, MSSQL and Oracle database in our product based on the customer needs. So I need to know how I can index a whole running database with elasticsearch ---
**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 4, 2019, 1:00pm UTC](https://discuss.elastic.co/t/compass-2-2-0-to-elastic-search-7-2-0/188880/2 "2019-07-04T13:00:44Z")
Welcome! I shared most of my thoughts there: [http://david.pilato.fr/blog/2015/05/09/advanced-search-for-your-legacy-application/](http://david.pilato.fr/blog/2015/05/09/advanced-search-for-your-legacy-application/) Basically, I'd recommend modifying the application layer if possible and send data to elasticsearch in the same "transaction" as you are sending your data to the database. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 1, 2019, 1:00pm UTC](https://discuss.elastic.co/t/compass-2-2-0-to-elastic-search-7-2-0/188880/3 "2019-08-01T13:00:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.