# Migration from activiti-5 to flowable 6 **URL:** \ **Category:** Flowable Engine\ **Created:** [November 5, 2018, 6:55pm UTC](https://forum.flowable.org/t/migration-from-activiti-5-to-flowable-6/2854 "2018-11-05T18:55:46Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![tommy\_725](https://avatars.discourse-cdn.com/v4/letter/t/f19dbf/32.png) [@tommy\_725](https://forum.flowable.org/u/tommy_725)\ **Post date:** [November 5, 2018, 6:55pm UTC](https://forum.flowable.org/t/migration-from-activiti-5-to-flowable-6/2854/1 "2018-11-05T18:55:46Z")
Hello, after success Migration from activiti-5 (v5 compatibility is also enabled), i noticed all process defs in database from activiti5 was tagged as “activiti-5” in field ENGINE\_VERSION\_ , After redeployed some process definitions to make them available for the Flowable 6 engine, i noticed these v6 runnable process ENGINE\_VERSION\_ were just set to null, why not set to “v6” or just engine specific version? It’s on purpose or my mistake? Regards tomas ---
**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:** [November 6, 2018, 9:25am UTC](https://forum.flowable.org/t/migration-from-activiti-5-to-flowable-6/2854/2 "2018-11-06T09:25:23Z")
That is correct. ‘null’ indicates the latest version. If an upgrade is ever needed, those would be tagged with v6. We could have gone with ‘v6’, it would have been the same thing. ---
**Author:** ![tommy\_725](https://avatars.discourse-cdn.com/v4/letter/t/f19dbf/32.png) [@tommy\_725](https://forum.flowable.org/u/tommy_725)\ **Post date:** [November 6, 2018, 10:19am UTC](https://forum.flowable.org/t/migration-from-activiti-5-to-flowable-6/2854/3 "2018-11-06T10:19:55Z")
ah ok,Thank you for replying! btw. flowable forum ui/ux is way better than alfresco community…