Hi Kaushal, Data archiving is not a simple task, and no community solution exists at present.
It is possible, but it would require a custom approach: You might move data to another database or export it into files Depends on whether you want to move out data from LIVE database or you have maintenance window Depends on whether you need a way to “move back” data if needed etc. You could handle it internally or consult a Fineract vendor or DevOps specialist for guidance. The current (develop) branch uses Postgres 18, but I see no reason not to use 17 or 16 (maybe earlier…). Regards, Adam S > On Sep 13, 2026, at 6:44 PM, Kaushal Shriyan <[email protected]> wrote: > > Hi All, > > We would like to seek your guidance regarding PostgreSQL database > configuration and data archiving for Apache Fineract. > > We would also like to understand which PostgreSQL version is recommended for > running Apache Fineract, particularly based on the currently supported > PostgreSQL versions documented in the official PostgreSQL documentation > https://www.postgresql.org/docs/ > > We are planning to archive data that is older than one year from the primary > Fineract database to manage database size and maintain optimal performance. > > Could you please advise on the recommended approach for archiving data older > than one year in Apache Fineract? In particular, we would appreciate your > guidance on the following: > > - Which tables or types of data can be safely archived. > - Whether Apache Fineract provides any built-in functionality or recommended > configuration for data archiving. > - Any dependencies or referential integrity considerations that need to be > taken into account before moving historical data. > - Whether PostgreSQL partitioning or another database-level approach is > recommended. > - Which PostgreSQL version is recommended and supported for our Fineract > deployment. > - Any official guidelines, best practices, or existing implementations that > we can refer to. > > We would appreciate any recommendations from the Fineract community regarding > the safest and most suitable approach for a production environment. > > Best regards, > > Kaushal
