Database migration from 4.1.0 to 5.2.0 Issues

We’re leveraging the Migrator in the hapi-fhir-jpaserver-migrate project to migrate a HAPI FHIR version 4.1.0 database to a 5.2.0 database. There are a few tasks that need to be skipped in order to complete the conversion successfully. We made no modifications to the 4.1.0 schema. It looks to be related to dropping constraints. In all the cases the original constraint (create unique index …) was mapping to one or a set of columns on the table. The new constraint of the same name added a column or columns.

For us, the following tasks had to be skipped:


Any insights would be appreciated.


You might want to raise this on the HAPI stream on (