Randall, It depends on how in-depth you use QB; if you just use QB for bank accounts, expenses, and run "Cost of Goods Sold" on a per order basis (no inventory), it will be straight forward. In fact, if you do a quick search on the web, you'll find some converters already available for free.
If you also use QB for inventory, it will be somewhat more difficult - and actually was very time consuming for me as we track every material and software item via serial number. I asked Dieter for a quote on this, and not receiving it timely, I rewrote parts of sql-ledger to allow us to track every individual piece of material that came in - with serial numbers where it applied. I also had to change the way assemblies occurred, because, you got it - each assembly had it's own serial number and needed to have links to all the serial numbers of the individual components. I'm not satisfied with my work, however, and would love to see this type of capability come from the "master." Finally, we used QB for payroll, also - something that sql-ldeger does not do at all. In this case, I developed my own postgresql database specific to the payroll. That was a real pain in the ass - I'm no accountant, so it took a week just to spin up on all the terms and the quasi-retarded way accountants have standardized books. A payroll module in sql-ledger will not only need the ability to track the standard payroll parameters, but allow for journal entries as a means of data entry for each pay period. Without the journal entry ability, you'll be getting round pegs from your accountant/CFO, and be attempting to shove the data into a square hole - if you catch my drift. Journal entries do not behave like simple register entries. I started this whole migration a couple of weeks ago . . . and plan on using QB side-by-side with sql-ledger well into 2003 to see if things like the following end up in sql-ledger: 1) ability to track each individual item via serial number, and assemblies tracked with serial number, with component serial number linkage; 2) payroll (a really needed component if sql-ledger is going to make it primetime). There you have it. -- Stonie R. Cooper Planetary Data, Incorporated ph. (402) 782-6611 "Growth for the sake of growth is the ideology of the cancer cell." - Edward Abbey On Monday 11 November 2002 02:49, Randall Burns wrote: > What has been folks experience with this? I've heard > it is pretty straightforward to convert customers, > chart of accounts. I've seen mixed things on the > actual conversion of transactions. One person said > they did their business in 6 hours or so, another said > they thought it would take a good SQL programmer a > couple weeks to get this right. > > RJB --
