[GNC] Import from Quicken to GnuCash not Working

[R Losey]

And there is always the question: Do you really NEED to import files?  I
figured that I'd just use Quicken for reference, and I just started GnuCash
cold.  I used Quicken a few times, but as time has gone on, I haven't
needed the data.

The only sticking point might be investments in which you need to track
gains. If it an account with just a few purchases, you could just enter
them manually.  If you have hundreds of such things, then... I don't know
what would work best for you.


On Sun, Sep 22, 2024 at 10:43 PM sunfish62--- via gnucash-user <
gnucash-user at gnucash.org> wrote:

> As has been mentioned before, Quicken handles data differently than
> GnuCash.
>
> In addition to the other comments concerning this issue, there is the way
> that Quicken handles years in dates. Instead of using a 4 digit year,
> someone got the idea of putting an apostrophe in to represent "20". These
> "dates" break the import, although it usually doesn't crash the program. It
> is a good place to start looking for issues that cause a Quicken import to
> fail.
>
> ⁣David T. ​
>
> On Sep 23, 2024, 3:57 AM, at 3:57 AM, Ken Farley <farleykj at gmail.com>
> wrote:
> >A suggestion that comes up many times in the past and even in some of
> >the responses you got is to break up the file and perhaps not try to
> >import the whole thing in one go.
> >
> >That being said, 14Mb is really not a very large file. The last time I
> >did this kind of thing a couple of years ago I loaded about 20 years of
> >
> >data in a year at a time. The files were maybe 3Mb max each and
> >imported
> >in minutes, not hours.
> >
> >I imported a year at a time, starting with the oldest. I found that
> >Quicken had allowed me to make some bad transactions. Also, Quicken did
> >
> >some weird stuff to account for stock splits that don't concur with the
> >
> >method Gnucash uses. So I slogged through all the years by reading a
> >year in, fixing all the messed up stuff, checking balances, saving. I'd
> >
> >copy the latest "good" file to a safe spot on my hard drive as I went
> >along, in case a catastrophe occurred.
> >
> >If you're getting the kind of failure you're seeing, my approach would
> >be to split the file into two pieces. First half of years in one file,
> >second half of years in another file. Try importing each half of the
> >data. If one fails and not the other, split the failed one into two
> >halves and try importing each of them, etc. You  should be able to zero
> >
> >in on the portion(s) of the QIF data that is "bad". You might have to
> >look into the actual QIF data (it's just a text file) and see if there
> >are any weird characters in there or something. 30 years of data
> >probably modified by dozens of different versions of Quicken might have
> >
> >some strange entries like corrupted text fields and the like.
> >
> >Once you find (and maybe fix) the bad QIF data, I'd suggest starting a
> >fresh new Gnucash file and then import all the "good" QIF file(s) into
> >that, oldest first.
> >
> >_______________________________________________
> >gnucash-user mailing list
> >gnucash-user at gnucash.org
> >To update your subscription preferences or to unsubscribe:
> >https://lists.gnucash.org/mailman/listinfo/gnucash-user
> >-----
> >Please remember to CC this list on all your replies.
> >You can do this by using Reply-To-List or Reply-All.
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>


-- 
_________________________________
Richard Losey
rlosey at gmail.com
Micah 6:8