# Version upgrade in production environment（6.5.0 to） **URL:** \ **Category:** Flowable Engine\ **Created:** [June 8, 2021, 8:08am UTC](https://forum.flowable.org/t/version-upgrade-in-production-environment-6-5-0-to/7944 "2021-06-08T08:08:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![zeweilin](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/zeweilin/32/2420_2.png) [@zeweilin](https://forum.flowable.org/u/zeweilin)\ **Post date:** [June 8, 2021, 8:08am UTC](https://forum.flowable.org/t/version-upgrade-in-production-environment-6-5-0-to/7944/1 "2021-06-08T08:08:39Z")
Hello, colleagues We have applied Flowable version 6.5 in the production environment, modified the configuration file, connected to the local MySQL database, and generated real data in the database. For some reason, we need to upgrade the production version, upgrade the version and migrate the data. So, I tried to deploy both versions of Flowable in the local environment. The first thing I found was that after initialization, version 6.5 had 86 tables, and version 6.6 had 87 tables. In 6.6, ACT\_DMN\_Decision\_Table was deleted. The ACT\_DMN\_DECISION and ACT\_RU\_EXTERNAL\_JOB are added, and there are many operations for updating data table fields. So, would like to ask, this situation of upgrade and migration, what should I do ? Thanks ---
**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\ **Post date:** [June 14, 2021, 3:24pm UTC](https://forum.flowable.org/t/version-upgrade-in-production-environment-6-5-0-to/7944/2 "2021-06-14T15:24:53Z")
Flowable does auto-upgrade if you enable schema management. Between two major versions, it’s normal that there are database changes. These are always tested and QA’d on all supported databases.