You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Aleksandar Vidakovic (Jira)" <ji...@apache.org> on 2022/03/21 14:13:00 UTC

[jira] [Assigned] (FINERACT-1535) Migration from Mifos to Fineract

     [ https://issues.apache.org/jira/browse/FINERACT-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksandar Vidakovic reassigned FINERACT-1535:
----------------------------------------------

    Assignee: Aleksandar Vidakovic

> Migration from Mifos to Fineract
> --------------------------------
>
>                 Key: FINERACT-1535
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1535
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Database
>    Affects Versions: 1.7.0
>            Reporter: Sifiso Mtetwa
>            Assignee: Aleksandar Vidakovic
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: Migration18.03.01.sql, NewMigration16.04.01.sql
>
>
> Dear All,
>  
> Since Mifos 18.03.01 we have encountered many bugs on migrating to the Fineract Database schema. This has prohibited some long standing Mifos users to efficiently move to Fineract without facing some challenges. Some migration script has been included but most schema changes have yet to be dealt with. While some fixes have been applied to isolated instances there is need to provide official support to this bug. Therefore using schema diffs we have come up with a solution for two migration scripts,
>  # Instances that have been running since stable release 16.12.01 then upgraded to 18.03.01
>  # Instances that only started running from 18.03.01
> Most of these Instances are in production with large DBs so smooth migrations are essential to maintain a steady workflow while remaining abreast with new technology.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)