The Customer running on IBM BPM needed new functionality. However, the project estimation clearly showed that the quick and qualitative project realization within a reasonable budget was impossible.

• The implemented system had an incorrect architecture, in which it was difficult to add anything new without affecting some of the workflows
• The IBM BPM developers are expensive; therefore, the system updating cost like the system development from scratch
• There are few skillful developers; therefore, it was necessary to wait for a long time before the specialists could start work

In addition, IBM BPM has the following disadvantages:

• High license cost: an increase in the number of users requires to enlarge the budget
• High cost of the access to software documentation and technical support; this makes the system support more complicated and more expensive

The complex problem could be solved only by migration.

As an optimal variant the Flowable BPM was chosen:

• It is an open source system and a client does not have to pay for an increase in the number of users
• The support is much cheaper due to the presence of software documentation and large developer community in open source
• Developers are less expensive, which considerably decreases the support of the system operation and updating

We determined active processes in the database and received the data on the processes through REST-requests to IBM BPM. However, we could not receive all the data in that way; therefore some data were received through direct requests to the database.

As a result, all the data and active processes were migrated into a new system without losses and a client received a significant economic effect.

• The expenditures for the purchase of new licenses were reduced by 100%
• The cost of the system support was decreased by 34%
• The expenses on developers were decreased by 28%

IBM BPM, Flowable BPM