[GNC] QIF upload ends abruptly at import step, last message "Transaction with no or only one associated account"

[Kalpesh Patel]

Few years back I imported about 20+ years' worth of Quicken data that had
been accumulated over time that was in Quicken 2017 on Windows. There were
number of lessons I had learned and shared here for others in the past
(google search terms: "site:lists.gnucash.org quicken"). 

While I do not know particulars about Quicken 2002 (is that a typo?), here
are general guidelines I recommend following which is what I formulated for
Quicken 2017:

- Clean up the Quicken file first --- In Quicken validate first followed by
create copy, followed by validation of that copied file and continue doing
so until no errors are in the file for at least two rounds.
- Don't try to export/import anything other than transactions from Quicken
(exception below).
- Reset your security price history if you can as event (buy, sell, etc.)
related prices will come over no problem. You can always import historical
prices into GNC by other means afterwards.
- Create your account hierarchy manually in GNC or by other means before
importing (I did not go with the method of account list export from Quicken
and import it into GNC so YMMV).
- Import securities as part of the import as-is, bulk create them during
import  and then modify after all transactions have imported correctly.
- Order of export/import to maintain: largest to smallest account size with
investment account first, banking accounts second, and lastly credit card
and/or loan accounts. If you can break it up into smaller chunks (one year
worth then better, or best is to create a year-end file in Quicken and then
perform import from that new year file with this stated order)
- Export one account at a time from Quicken then import that single account
into Quicken; never export all accounts in one qif file!  Follow Liz's
divide-&-conquer (binary split) approach on fixing a qif file if it errors
out but don't change the order from what is mentions in the previous step.
- Make a backup copy every time an import has worked. This will allow you to
go back if there is large set of incorrect import on the next account
without the loss of work up to the point it has worked. This will let you
build upon it until all have been moved over.
- Don't expect everything to look correctly after import is completed. In
GNC transactions, account and many other things can be moved around and
re-parented without much complex work that otherwise would be needed in
Quicken so get transactions over into an accounts in GNC and move on to
importing/exporting next account.
- Pay attention to the way dates are formatted for years before 2000, and
years 2000 and after if you are on Windows Quicken. Make them consistent
(programmatically) before importing them if you see them differently
formatted. GNC likes only one and consistent format throughout qif file.

 Hope this helps.


------------------------------

Message: 10
Date: Sun, 22 Jan 2023 10:22:10 -0500
From: jhoeter at googlemail.com
To: <gnucash-user at gnucash.org>
Subject: Re: [GNC] QIF upload ends abruptly at import step, last
	message "Transaction with no or only one associated account"
Message-ID: <077d01d92e75$4c72bee0$e5583ca0$@gmail.com>
Content-Type: text/plain;	charset="us-ascii"

Good idea! Thanks, Jan

-----Original Message-----
From: gnucash-user <gnucash-user-bounces+jhoeter=googlemail.com at gnucash.org>
On Behalf Of Liz Dodd
Sent: Saturday, January 21, 2023 4:14 PM
To: gnucash-user at gnucash.org
Subject: Re: [GNC] QIF upload ends abruptly at import step, last message
"Transaction with no or only one associated account"

On Sat, 21 Jan 2023 09:12:23 -0500
Jan via gnucash-user <gnucash-user at gnucash.org> wrote:

> I do have 20+ years of Quicken 2002 data (German Version), but only 
> tried to upload 2022 to GnuCash via a QIF down-/upload. It ends 
> abruptly (program vanishes completely) at the import step. The last 
> message I see on the screen is "Transaction with no or only one 
> associated account".

One method of approaching this is the binary split method.
Instead of all 2022, split it into two parts, try importing one.
If it fails, ignore it, and try the other one.
Split the one that fails...

Repeat until you find the problem, then deal with the problem.


We do suggest importing small files sequentially to train the importer, so
you may choose to stick with small files until 2022 is finished.


Liz
_______________________________________________
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.



------------------------------