Exactly what I'm looking for. I assumed it would be straightforward! I have exported budget and register to CSV, but can't see the point of doing that if we can't import it.
I started a new budget a year ago, called "2018", intending to do the same for "2019" and so on thereafter - to keep reports and things clean and straightforward to compare year on year. Also to keep things from slowing up as there gets to be lots of history.
But it looks like we must enter every account and category manually, which seems ridiculous. In YNAB 4, we'd have been able to copy and rename the budget file(s) then delete all old transactions in one go. Yet another thing that's less simple in the web app.Reply
No. This is a glaring weakness of nYNAB. Until there is a "save as" or "restore from backup" or functional "import from exported CSV" function, I will need to keep a parallel budget in YNAB 4 as the backup plan for user error when/if I mangle chopping down my working nYNAB budget to eliminate old data, unused accounts, unused categories. I just hope that the YNAB organization gets around to fixing this before Windows or IOS makes YNAB 4 non-functional.Reply
It's as I thought, but it's so ridiculous to have an export function but no import function, that I assumed I was missing something. Come on, YNAB, please prioritise this, it's is a basic essential.
I have given up my intention of having a separate budget for each year, and while I can see it's nice to have longer-term average spends (and so on) available to view, I must hope the thing doesn't become unusably unwieldy as time goes on. My system is slow, my internet is rural and appallingly slow, and everything is already ridiculously slow so anything that loads it further is very unwelcome. It's already inconvenient with not enough keyboard shortcuts and most of them working only intermittently.
I suppose I should be glad that we have the CSV export, at least - for when I end up researching and choosing an alternative to YNAB. It looks certain that I shall sooner or later. But having glanced at the CSVs - they aren't at all friendly, either.Reply
My interest in the import export topic is about SPLITTING the 2018 file into 2 so that each of us (me and partner) would take responsibility for some of the accounts and some of the categories. If others are interested in doing this, let me know and I what describe what actually worked for me.
Also remember - the bank only provides the date, payee and amount for each transaction - we decide and record the categories that are important to us for each transaction as they come in. The fact is that YNAB is a very big help in simplifying this decision making process thru payee history, recurring transaction info, and a bunch of importing and reporting features. I suspect (as a one time developer) that it is these 'under the cover' activities that make the export then perfect import challenge very difficult. To me, the YNAB benefits more than make up for some of the deficiencies.Reply