# Elasticsearch Migration Plugin - Custom Aggregation Plugin

**URL:** <https://discuss.elastic.co/t/elasticsearch-migration-plugin-custom-aggregation-plugin/103177>\
**Category:** Elasticsearch\
**Created:** [October 9, 2017, 6:07am UTC](https://discuss.elastic.co/t/elasticsearch-migration-plugin-custom-aggregation-plugin/103177 "2017-10-09T06:07:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deb/32/46162_2.png) [@Deb](https://discuss.elastic.co/u/Deb)\
**Post date:** [October 9, 2017, 6:07am UTC](https://discuss.elastic.co/t/elasticsearch-migration-plugin-custom-aggregation-plugin/103177/1 "2017-10-09T06:07:24Z")

</div>

I am trying out the elasticsearch migration plugin to check if I can migrate from 2.3.x to 5.x. I have some custom aggregation plugin in my 2.3.x cluster.

Running "Cluster Check-up" it is showing green for "Plugins".

So my question is does the elasticsearch migration plugin verifies all the plugins including custom plugins?

---

<div class="post-metadata">

**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\
**Post date:** [October 9, 2017, 6:16am UTC](https://discuss.elastic.co/t/elasticsearch-migration-plugin-custom-aggregation-plugin/103177/2 "2017-10-09T06:16:14Z")

</div>

The plugin only verifies the plugins it knows about  
[https://www.elastic.co/guide/en/elasticsearch/reference/5.0/breaking\_50\_plugins.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/breaking_50_plugins.html)

Looking into the sources, you can see all the plugin checks it does and that does not include custom ones, unless it is a site plugin, in which case, it would warn you.

> <https://github.com/elastic/elasticsearch-migration/blob/2.x/src/migration/Plugins.js>

I would [enable deprecation logging](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/setup-configuration.html#deprecation-logging) in order to see if your custom aggregation plugin raises any red flags.

---

<div class="post-metadata">

**Author:** ![Deb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deb/32/46162_2.png) [@Deb](https://discuss.elastic.co/u/Deb)\
**Post date:** [October 9, 2017, 1:46pm UTC](https://discuss.elastic.co/t/elasticsearch-migration-plugin-custom-aggregation-plugin/103177/3 "2017-10-09T13:46:16Z")

</div>

Ohk,

Thanks @val for replying.

---

<div class="post-metadata">

**Author:** ![Vikas\_Kumar1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_kumar1/32/47867_2.png) [@Vikas\_Kumar1](https://discuss.elastic.co/u/Vikas_Kumar1)\
**Post date:** [November 1, 2017, 12:07pm UTC](https://discuss.elastic.co/t/elasticsearch-migration-plugin-custom-aggregation-plugin/103177/4 "2017-11-01T12:07:27Z")

</div>

HI @Deb

I am trying to write a custom aggregation plugin. I am just roaming around to find any help.

Can you please share something, I mean how can I do that. I am totally clueless, where to start from.

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 29, 2017, 12:07pm UTC](https://discuss.elastic.co/t/elasticsearch-migration-plugin-custom-aggregation-plugin/103177/5 "2017-11-29T12:07:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.