No, once you have the data in skrooge, and are sure that it has imported properly, skrooge can export it as a kmymoney file, which KMM can simply open. So once in skrooge, forget about QIF altogether.<br><br>One thing you will find is that on the migration you are likely to have to tweak your scheduled payments, but it's not too big a job.<br>
<br><div class="gmail_quote">On 20 May 2011 09:43, timothy <span dir="ltr"><<a href="mailto:timboyle@afrihost.co.za">timboyle@afrihost.co.za</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, 2011-05-20 at 09:13 +0100, Ian Millington wrote:<br>
> When I first tried to migrate from Quicken to Kmymoney my files were<br>
> reported as too old, and that I needed an older version of KMM. That was<br>
> the KDE3 version - I don't know whether that has got any better so when<br>
> I came to migrate I didn't try it.<br>
><br>
> What worked a treat for me (and I know it's not the ideal answer) was to<br>
> import the QIF files into skrooge (with over 12 years transactions on<br>
> multiple accounts only 2 adjustments were needed).I played around with<br>
> skrooge for a while but found it not so user-friendly. What I was able<br>
> to do, importantly, was to export as a kmymoney file which Kmymoney was<br>
> then able to use.<br>
><br>
> So, my take on it was that skrooge currently has the edge on import and<br>
> export (at least so far as QIF is concerned) whereas KMM currently has<br>
> the edge on function. Rather than continue to struggle it might be best<br>
> to use the above way to get you up and running a lot quicker<br>
><br>
> HTH<br>
><br>
> Ian<br>
><br>
</div>Thanks. That is definitely worth a try. It might mean that I would<br>
download a PDF file, convert it to QIF, import to skrooge, export to QIF<br>
again and then import to KMM. At the very least I might get some insight<br>
into what sort of format is acceptable in kmymoney and what is different<br>
in my files. Does skrooge handle OFX export?<br>
<font color="#888888"><br>
Timothy<br>
</font><div><div></div><div class="h5"><br>
><br>
><br>
><br>
> On 20/05/11 08:18, timothy wrote:<br>
> > Hi<br>
> ><br>
> > I wondered if you could confirm that the problems I have been experiencing<br>
> > are due to the way KMM handles QIF or that there is something wrong with my files.<br>
> ><br>
> > I have tried importing old QIFs from when I migrated from MsMoney and I get similar<br>
> > results. At that time so many things were new and unknown that I can not remember<br>
> > these being specific problems. I do remember that I had to do considerable manual<br>
> > reconfiguring of accounts and categories.<br>
> ><br>
> > Be that as it may, I really want to know whether I should give up on the QIF import<br>
> > and start looking into OFX import of investment transactions.<br>
> ><br>
> > If anyone has examples of investment files (both QIF and OFX) that have successfully<br>
> > imported into KMM. I would very much like to use them in my further endeavours.<br>
> > My investments sites merely give web page output of transactions which I can download<br>
> > in various formats from PDF, XLS, CSV, HTML and even text. These I have been converting<br>
> > to QIF for import. My bank and credit card go directly with OFX into KMM.<br>
> ><br>
> > Ar first glance OFX investing appears not to cater for categories and sub-categories and does<br>
> > not appear to be able to transfer the proceeds of Sells or Dividends to another (cheque)<br>
> > account?<br>
> ><br>
> > Sample files that actually worked would be of tremendous help.<br>
> ><br>
> > PREVIOUS MESSAGE TO KMM MAILING LIST<br>
> > ------------------------------------<br>
> ><br>
> > Hi<br>
> ><br>
> > I am running KMM 1.0.5 on KDE 3.5.10 on Ubuntu Maverick.<br>
> ><br>
> > I have been testing out QIF investment files imported into KMM and have<br>
> > run into a few problems.<br>
> ><br>
> > The QIF spec gives the L option as 1)category:subcategory or 2)[transfer<br>
> > to account] depending on the N option having an X or not i.e. NSellX or<br>
> > NDivX.<br>
> ><br>
> > However in my testing:<br>
> > 1) KMM fails to recognise the colon: and creates a new category called<br>
> > "category:subcategory" as if the whole string was a new category name.<br>
> ><br>
> > 2) the transfer account given as [parent-account:sub-account] is not<br>
> > recognised and although imported OK shows a yellow triangle /exclamation<br>
> > with the account field being blank in the ledger. If I reduce the string<br>
> > to just [sub-account], a new investment account is created with that<br>
> > name at top level even though the same-name account exists as a<br>
> > sub-account.<br>
> ><br>
> > Perhaps I should explain that I have organised my account structure with<br>
> > generic top level asset "dummy"accounts such as Banks Accounts; Money<br>
> > Markets; Retirement etc. Each one of these may contain several relevant<br>
> > investment or checking accounts with their corresponding investments.<br>
> ><br>
> > Any light on this matter would be appreciated.<br>
> ><br>
> > Timothy<br>
> ><br>
> > _______________________________________________<br>
> > KMyMoney mailing list<br>
> > <a href="mailto:KMyMoney@kde.org">KMyMoney@kde.org</a><br>
> > <a href="https://mail.kde.org/mailman/listinfo/kmymoney" target="_blank">https://mail.kde.org/mailman/listinfo/kmymoney</a><br>
<br>
<br>
_______________________________________________<br>
KMyMoney mailing list<br>
<a href="mailto:KMyMoney@kde.org">KMyMoney@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kmymoney" target="_blank">https://mail.kde.org/mailman/listinfo/kmymoney</a><br>
</div></div></blockquote></div><br>