Community mailing list archives

Re: Best way to learn how to import legacy data into odoo

Ion Cebotari
- 07/21/2015 15:12:29
Hi, Michael

I have used the openupgrade project to import an OpenERP 6 database to Odoo.
Of course it is not ideal, but the most important data has been properly 

On 07/21/2015 09:47 PM, Michael Elso wrote:
> 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
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe:


Best Regards, / Cu respect,

Ion Cebotari
IT Security Consultant

ÎCS "Cyssea International"
Republica Moldova, MD-2012, str. A.Puskin 22, of.516.
tel. serv.:_(+373)22 234345