How to migrate data from Bahmni version 0.93 (non-docker) to Bahmni-lite v.1.0.0 (docker)?

Currently, we are using Bahmni (version 0.93) in a medical center. We have reviewed the new Bahmni-lite v.1.0.0 (with docker) and are very impressed with it. However, we haven’t come across any documentation on how to perform the migration of configurations and data. Is it possible to carry out this migration? If so, how is it done?

Thank you.

Hi Pablo,

Glad to hear you liked the Bahmni LITE release! :slight_smile:

The Bahmni LITE is not a full replacement for Legacy Bahmni v0.93, since LITE doesn’t contain OpenELIS/Odoo/DCM4chee. That will come as part of Bahmni Standard Release, which hasn’t yet happened. A development version of Bahmni-standard is packaged in the docker (bahmni-standard subfolder), which people can try.

But if all you need is the EMR component of V0.93 to be migrated over to Bahmni Lite (no Odoo, no ELIS, no DCM4chee), then you should just be able to point the new Bahmni LITE to a clone of the older DB, and on process of coming up, Bahmni LITE will run liquibase changes on the DB. We have done this at one facility which upgraded just the EMR portion to use LITE binaries, while leaving OpenELIS/Odoo untouched.

There isn’t any documentation on migration because we will test that aspect when we perform a Bahmni Standard (docker) release. The LITE release is currently targetted towards new adopters, who don’t have significant migrations to be done.

Please try out, and provide us feedback. Will be helpful to know. Thanks!

cc: @mohant @soorya @angshuonline

Also, to point your existing bahmni-config to be picked by docker, you will need to follow these steps: Using Implementation specific Configuration (docker) - Bahmni Wiki - Confluence

So, DB needs to be your v93 one. Config needs to be your v93 one. Try this out first with a TEST setup and see how things look.

few other things - clinical forms (Forms2) and uploaded files directory - those need to be backed up and put on a mounted volume. @mohant any inputs here?

The docker backup/restore script can give you guidance on right locations within docker (for Databases and documents sub-folder):