# Mapping conflict for system.process.cpu.system+user when using metricbeat-6.3.0 and 6.6.0

**URL:** <https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [April 2, 2019, 1:17pm UTC](https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999 "2019-04-02T13:17:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)\
**Post date:** [April 9, 2019, 11:24pm UTC](https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999/2 "2019-04-09T23:24:09Z")

</div>

@kaem2111 Sorry for the late response. The easiest way is to delete the existing two templates and create a fresh new one. I see in [Metricbeat 6.3.2 upgrade breaks?](https://discuss.elastic.co/t/metricbeat-6-3-2-upgrade-breaks/142241/10?u=kaiyan_sheng), there is also a way to actually preserve data if that will be more helpful.

---

_[View the full topic](https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999)._