Sorry about the delay on this.
On Thu, Sep 25, 2014 at 10:58 AM, Louis <[email protected]> wrote:
>
>
> Ok, I'll gird my loins and give it a go.
>
>
>
> As for writing it yourself, I don't think it would be too difficult.
>> There are some important questions to ask before going into it though:
>> 1. Do you have inventory? If so, how do you want to value the inventory
>> for import purposes? For example you could export/import each item at
>> current value. You could import current onhand at current average cost,
>> etc.
>>
>
> We have inventory in the form of used and rare books. Each book is unique
> and cost will be the original purchase price, which can be $0.
>
Ok so what I would look at doing is this:
1. COA tables can be dumped and loaded as is:
account_header, account, account_link, account_link_description
Note they need to be in that order.
2. Entities tables (customers/vendors) can be dumped and reloaded as is:
entity, company, person, entity_credit_account, location, eca_to_contact,
eca_to_location, users
3. Parts can be dumped and imported as is
4. Where it gets complex is in the ar/ap/gl tables. My recommendation
would be to create a $0 value AP invoice (in the db) and then import those
records attached to AP in 1.3 where they link to an old AP entry and qty +
allocated <> 0
5. Enter a GL transaction with initial balances.
You may want to take a look at how our upgrade scripts work for inspiration
and portions of the sql queries you can use. What we do is move the old
data to another schema (rename schema public) and then populate a new db
schema. This is similar to what you are doing so you may be best off
taking our upgrade scripts as a template and modifying them to suit your
needs.
Best Wishes,
Chris Travers
>
>
> 2. Besides inventory, customers, vendors, parts, and balances, what else
>> do you need to import?
>>
>
> Import:
>
> 2014 transactions
>
> vendors with transactions since 2010-01-01
> customers with transactions since 2010-01-01
>
>
> Re-enter, re-create:
>
> COA to get rid of accounts unused in the last few years.
>
> Sales taxes (Colorado is always messy)
>
> I think that would do it.
>
>
> I would be happy to provide a basic overview of how I would go about such
>> a process on the -devel list. Chances are the tools used are likely to be
>> SQL, the PostgreSQL COPY statement, a spreadsheet of your choice, and
>> pg_dump. I think for the most part, it is likely to be relatively easy.
>>
>
>
> I suspect, as is often the case, the hard part will be making up my mind.
>
> Louis
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Ledger-smb-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
>
>
--
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
