Pages on moving between Fineract releases and database platforms under the project's release and end-of-life policy.
Moving from end-of-life Fineract 1.14 to 1.15: the three SQL injection fixes, Liquibase migrations on a write or liquibase-only instance, regression testing of products, accounting and COB, and matching the Mifos web app version.
Moving an existing Fineract tenant database from MySQL or MariaDB to PostgreSQL after FSIP-9: why the project provides no official migration tooling, how to plan schema and data transfer, UTC date checks and reconciliation.
Bringing a long-unpatched Fineract or older Mifos X backend up to the current release: stepping through Liquibase changes, the UTC date handling introduced in 1.8.0, deprecated tenant connection variables and custom code that edits core sources.
The schema migration switch in Fineract 1.7: why databases older than 1.6 must first reach the latest 1.6.x, how Liquibase takes over a Flyway-managed schema, the leftover Flyway tables and known failure cases.
Upgrading scaled Fineract on Kubernetes without migration races: disabling Liquibase on app instances, a liquibase-only job before the rollout, rollback planning and the single-threaded Liquibase limitation.
Protecting integrations during upgrades: Fineract's API backward compatibility check against a baseline OpenAPI spec, reading the breaking change report and testing generated clients and front ends.
Upgrading the front end with the backend: web app releases tagged to Fineract versions, environment variables to check, custom UI changes and testing staff workflows after a Fineract upgrade.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.