Community mailing list archives
Re: Best way to learn how to import legacy data into odooby
From my experience (50K+ users)
write conversion scripts to create conversion tables for the many2one relation tables only.
Then show the prospect your new solution in Odoo with the naming conventions they are familiar with.
Only then you bring up the migration of only the ref data.
My 2 cents.
Thank you for the reply RonaldI think in some instances (especially where cost is involved!) it's probably an easy sell to just move forward in a new system. I have a specific client in mind (or potential employer) that would need to have access to the old data in the new system given that the legacy system may become unavailable in the near-term. As far a moving to odoo, they are using a traditional, two-tiered, windows-based system that is expense to maintain and access (using Citrix). I think a web client based application like odoo is an easy sell, I just want to set realistic expectations of the migration results.I kind of feel like I'm looking for the Holy Grail of ERP migration, but I'm just wondering if anyone has performed such a full (automated?) migration before, and perhaps what such an effort might entail.- MikeOn Tue, Jul 21, 2015 at 4:12 PM, Ronald Wopereis <firstname.lastname@example.org> wrote:hi Michael,unless there is a specific need to have the data in Odoo,why not leave the data where it is, and start fresh?leaving the legacy system available for a while (six to twelve months) for those times when someone needs to look up something.i mean, it is either way: or the legacy system doesn't fit the business logic anymore, and then the mapping from old to new model is a pain in the as* ; or the model is still valid, and then the question arises why move to odoo?remember that being able to go back to the legacy system is an essential part of the mourning process for some of your customer's users. best is if you can make the data read-only in the legacy system.hope this helps.best regards, Ron2015-07-21 20:47 GMT+02:00 Michael Elso <email@example.com>:Hello Odoo Community,I've been working with odoo and learning how to import data with the plan to support odoo in the future and help customers/clients/employers migrate legacy data into a new instance of odoo. While it's easy enough to import fairly static data (user, partners, products, etc,), I'm having a hard time finding information on how to import transactional data. I can get Sales Orders and Purchase Orders into the system, but I haven't found a description or method of getting order documents validated, invoiced, etc. Even entering backdated information manually is difficult (or not supported at all!).So here's my question; Does odoo assume that all new customers will not import legacy data beyond simple lists, or are there closely guarded methods that odoo implementer's use that are proprietary, or have I missed a forum, some documentation or tutorial that details the best practices for getting data from a legacy system into odoo?I've spent a reasonable amount of time researching this (several months), and have found a number of 'import' articles, videos, etc., but nothing that seems to address how to get old or archival data into odoo, even if it's a small number of backdated transactions. If I had a team of people keying in the data, I don't see a way to allow them to backdate and post historical transactions as part of an initial setup.Am I naive in believing this can be done, or that there is a need for it to be done? How do members of this community advise or set the expectations of customers that would like to have/need their old data available in the new system. I'm fairly well versed in ETL tools (Talend, specifically), and have worked on SQL databases for more than a decade, but I know it's a 'dangerous' thing to do outside of the system.Sorry for the long-winded explanation, but I feel like I've reached a dead-end researching this on my own and thought I'd reach out to the community for advice or to point me in the right direction.Thanks!- Michael Elso