We have other deployments that are migrating from ledger-based systems to Mifos. (IIRM, for example).
The answers below are a little more vague than I'd like to provide, but I'll try to come up with something more complete. In brief, though: 1) Some portion of the GK tools may be useful to you (it looks like some files may have been taken down-I'll see if I can find them or re-post them). However, ass you are going to 1.1, the schema changes and additions will mean you'll need different processes. The most important step-and you may be well into this portion-is getting the data mapping and data clean-up correct. In my experience, the mechanics of the SQL are not nearly as difficult as mapping and cleaning the data, whether you write custom scripts or use an existing ETL tool. Mapping requires a pretty thorough understanding of how both the legacy and new systems are used. It sounds like you already have some good ETL ideas, but perhaps others can chime in? 2) You can import historical data into the system. a. Again, the mapping is the key in this area-i.e. understanding how you will use the historical data for reporting. If the data will truly be used for reporting and decision-making, it's worth keeping. If you find-as can often be the case in data migration scenarios-that you can report adequately off archived data and/or the data will not be used frequently, the extra effort may not be worthwhile. If your goal is to use loan history for evaluation of future loans for existing clients, then you will want to investigate migrating the results of previous loans into Mifos. b. My assumption would be that you want to migrate all active loans into the system. This process is possible, and looking at GK mapping may be extremely helpful. 3) We have been discussing this process. I think now that 1.1 is coming out and Mifos will be more stable and better built, the processes will get more repeatable. As always (like GK has done), we'd love the successes and non-successes to be documented for the community. Again-these answers are quick. I'll see what other information I (or others!) can provide. Thanks --aB ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Soham Dhakal Sent: Monday, December 24, 2007 11:27 AM To: 'Mifos functional discussions'; 'Developer' Subject: [Mifos-developer] Questions around data migration/ initial setup ofmifos Hi All, As part of our detailed gap analysis, we are trying to figure out ways to get the existing data (manual) into mifos. I searched on the website and also the mailing list to get some ideas. I found a link http://mifos.org/knowledge/deployment-project-pages/grameen-koota/data-m igration but it does not have anything listed. Are there some other documentation with regards to this. I am looking at Kettle to see how to integrate it but i am not too familiar with it. Here are some things we are trying to address, please provide your input as to how these are being accomplished by others.. 1. We would like to import all the client information from a csv file (client demographics, Group information, Center information, Branch information), or something similar, has anyone written scripts to do this? 2. How to import existing loans into the system a. Old loans that have been completed. - Do we import all the previous loan cycles (does mifos even allow this, I mean how will all of the different transactions related to a loan be updated)? b. Loans that are ongoing but have installments remaining. 3. Should we have a standard process for migration into Mifos? What i mean is that regardless of the existing system, we have standard formats (csv, xml?) that can be imported into mifos through import scripts. So the only thing MFIs would have to consider is dumping out their existing data in the format recognized by mifos. Thanks Soham
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
