Convert Procedure for Windows to Mac is failing
Attempting to convert QB 2009 Windows to QB 2010 Mac. Getting a "=entityForName: could not located an NSManagedObjectModel for entity name 'nextGIkey' error.
Attempting to convert QB 2009 Windows to QB 2010 Mac. Getting a "=entityForName: could not located an NSManagedObjectModel for entity name 'nextGIkey' error.

You really should update the Win 2009 file to Win 2010 and then bring it over the Mac. That's likely the problem. But I'm not 100% sure - first make sure both the Windows version you are using and the Mac version have both been updated to the latest release (QuickBooks->Check For Updates on the Mac side).
Finally, make sure the file verifies on the WIn side before bringing it over.


In fact, to add to Biscotti's last recommendation, it wouldn't hurt to go ahead and rebuild the file once or twice on the Windows side before creating the backup for Mac. And updating the two versions should occur before the backup is made (of course).
Exact same problem here. QB support now has my file and is working on the conversion.
All of the others answers are the canned responses and will not solve this issue. I have two company files. One transferred just fine with memorized reports and transactions and special characters in the memo field. The other has none of those and could not convert.
With all the time spent on the phone this probably is not a profitable upgrade for them.

This is the same bug that I reported the other day:
community.intuit.com/posts/qb-2010-r5-cannot-open-qbb-from-windows
This new bug appeared with the R5 patch. In that other thread, JFischer reports that Intuit is looking into it.
I'm glad it is not just me, since this means that they can reproduce and fix the bug more quickly. Silver lining and all of that, you know... ;-)
As a critical (as in dead-in-the-water) kind of bug, I hope a patch for this one can be made fairly quickly. But, I'm sure we'll need to be patient as all patches have to be 'regression tested' to make sure that they don't break something else...


wjo1, our answers are not "canned" responses. We're just users trying to help other users and making suggestions that we hope will help.