You could try checking the integrity of your Quicken file first by running one of the "Validate and Repair" options in the "File" menu under "File Operations". Sometimes parts of the qdf file gets corrupted and the repair procedure may point you to various issues within your data. I broke my qdf file into individual accounts by year before I imported them (30+ years and roughly 100 different accounts). That was the only way I could get gnucash to import my complete data without crashing. Unfortunately it was a few years back and I don't exactly remember what import settings and options I chose.
The only help I can offer is that you can import one year at a time and then save the file to create a backup file. Then import the next year and save the file as a new backup file. Keep up the process until one of the imports crashes. At least then you can narrow down what year of data is causing the issue and you will have a backup up file of all the prior imports. Since the qif file is a simple text file you can open the "bad" qif file in notepad and look through the file for errors. You can also skip that "bad" file and continue the process with the remaining files just to get as much imported as possible. On Mon, Sep 23, 2024 at 4:15 AM Tom R <tom.rout...@gmail.com> wrote: > Hi Ken. Thanks for the detailed suggestions. I did go ahead and try > splitting the 30 years of Quicken into two segments -- one for the > first 20 years, and another for the most recent 10 years. > Unfortunately, they both resulted in the GnuCash Import process > crashing the same way. GnuCash just aborts and closes for both > segments with no error message or other indication of why it's > crashing. > > Your suggestion though of importing things in one year at a time might > be a possible solution. As a test I tried importing just one year > like that -- 2023 by itself. And interestingly enough, GnuCash was > able to pull in that one year successfully. So I guess I could try > doing more individual years that way, one at a time. But that sure is > a long tedious process that I never thought would be necessary in > migrating to GnuCash. > > The main problem with that method is: what happens when I find > individual years that cause GnuCash to crash? Will I then need to > have to try importing that failing year one month at a time? Then one > week at a time? Then one day at a time? All in an effort to isolate > the line in the QIF file that's causing GnuCash to fail? It could > take a very long time to get 30 years of Quicken data into GnuCash > that way. > > I can understand that GnuCash handles some data differently than > Quicken does. But I would think that the Import process would be > capable of identifying any issues it detects, and then just provide a > log file at the end listing which lines in the QIF file are causing > problems and need to be corrected. The fact that a QIF file can cause > GnuCash to just crash and close seems like a major bug in the program > that needs to be fixed. Are the software developers aware that this > problem even exists? > > On Sun, Sep 22, 2024 at 6:56 PM Ken Farley <farle...@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@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@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. > -- iii _______________________________________________ gnucash-user mailing list gnucash-user@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.
