@ScottMeisterCPA, this sounds a perfect question for you since you have Sage and QuickBooks background.
I’ve only converted two companies from Sage to QuickBooks. One was Sage 50 to QB Pro and the other was Sage 50 to QB Premier. I wouldn’t count on the tool Intuit provides for the conversion as we experienced all sorts of mapping issues. The data looked good on the surface, but the more we dug, the more we realized we needed to start over. From what I was told it’s an issue with two different database structures, and they didn’t work well together, especially when custom fields were involved. We ended up starting a QB file at the beginning of the year and loaded the balance sheet via journal entry. Certain items were posted in the new QB file for prior period (uncleared checks, open invoices, unpaid bills, etc.) This means that my clients don’t have detailed records from Sage in their QB file. Both clients were okay with this, but yours may not be okay with it. For what it's worth, both clients absolutely LOVE QuickBooks compared to Sage for ease of use, customer support, etc.
For retaining the prior year detail, you might be able to use something like Transaction Pro to populate a new QB file with prior year Sage transactions, but I don’t know how you’d get the transactions out of Sage.
Without seeing their current setup, it’d be hard to say which version of QB to use. But, based on what you’ve written, “500 cost codes” and “provide flexible report writing capability for project management,” I’d think Enterprise may be your best bet (considering Pro, Premier, or Enterprise). One of the nice parts about QB Desktop is you can try Pro or Premier and if you need to, you can easily upgrade to Enterprise.
A couple questions…
Just curious, but why 500 cost codes? For an energy engineering firm, I would’ve expected much less. What’s the product/service split on the cost codes?
Are they running payroll in house? How many employees do they have?
How detailed are they wanting the job costing? For example, do they want to know job costing per employee, per pay period? Or would job costing per month/year be adequate? I’ve had payroll companies produce job costed payroll reports for clients and they’re able to journal entry the info in as one bulk number. It’s somewhat generic, but it works for their reporting. Would something like that work in this instance?
For multiple divisions, I’m assuming they could use class tracking?
Hope this helps!
Hi Scott -
Is your client by chance a Govt contractor? For true project cost accounting, I suggest you check out PROCAS (Project Cost Accounting System). System includes Timekeeping and Expense reporting accessed by employees via any internet connection, where they can post to projects, tasks, subtasks labor categories (if needed) and cost centers (depts). That data flows into accounting system to compute Indirect rates such as Fringe, Facilities, Overhead and G&A, which can be applied as burdens on direct project costs and on billing invoices to customers. Also does all the normal accounting like AP, AR, GL, Bank recons, etc. You can see a free 30-minute demo on their website and request a free live interactive one for 90-minutes, you can also see videos on You-Tube and there is a Blog. I do not sell any systems, and I don't mean to try to sell one here, but sounds more like what you need. I have impIemented for about 20 companies and all love it and I have about a dozen ongoing clients on PROCAS, where I access all from my one same menu. you are interested after viewing online or after demos, let me know as I can help you pay even less. I have client on Sage right now and I am not liking it, so they will move soon.
No government contractors but after reading you're post, I'll be looking at PROCAS as it may be a good fit for other clients. Thanks for sharing!
Glad to help and not to take away from QB, but project accounting is not their best thing. So I think actually better to not have people on here complaining about that functionality. Just holler if I can answer any questions as I use the system every day and have for years.
@Teri, feedback is always appreciated and I always send it up the chain when I can. If we can't have open and honest conversation, then we can't have a community.