Hi Folks,
Partha and Chandan, at SunGard, are working with us to develop a data
migration tool for Mifos. Below is a quick high level overview on their
approach, and then a question.
High level overview (I'm not technical, so apologies to SunGard if I
miss some technical nuances):
SunGard is developing a simplified data model into which data from other
systems (legacy systems, excel spreadsheets, etc) can be migrated. They
will then build migration scripts that will port data from this interim
database into Mifos (these scripts will be replaced by APIs once Mifos
has those available). The idea is that the work to migrate data from
the interim database into Mifos only has to be done once. The work
from the MFIs data sources into the interim database will need to happen
every time (unless we're doing multiple migrations from the same legacy
system)-but it will be a much easier task since the interim database
will be much simpler than the Mifos database.
Approach:
SunGard is assuming that they will do a *complete* migration of all data
from the interim database into Mifos-including things that would be
quite easy to manually type into Mifos-ie, offices, users, products,
etc. Basically all configuration items would be stored in the interim
database and migrated over.
My Question:
What do people think of this approach? I had always assumed that we
(the deployment team working at the customer site) would first configure
Mifos and manually enter entities like offices and that the migration
would be limited only to the entities that can't be handled by manual
entry (ie, centers, groups, clients and accounts). Not sure why I
assumed that-I suppose because I didn't see the need to build migration
scripts for items that can easily be manually entered. Besides the
general concern, I have two specific questions:
(*) Will this approach make it difficult to accommodate changes at the
MFI during the data migration process. Ie, if the MFI adds a new user
during the migration process-they can't add it directly into Mifos-they
need to communicate back to the data migration team to make a new entry,
right? Will this cause a lot of churn?
(*) How will this approach handle doing a staged roll-out, where they're
migrating a few branches at a time?
Partha: Any comments on this?
Ryan: especially interested in your take. J
Emily
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mifos-users mailing list
Mifos-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-users
