Hi Hakon/GnuCash users, https://wiki.gnucash.org/wiki/FAQ#Importing.2FExporting_Data - have you read this section of the GnuCash Wiki on importing and exporting data?
What version of GnuCash are you using? The current version is 5.10 - https://www.gnucash.org/download.phtml What operating system are you using? --- Thanks, Brad - https://www.facebook.com/brad.morrison.12327/ & https://norcal.social/@BradMorrison On 2025-01-08 15:28, Michael or Penny Novack via gnucash-user wrote: > On 1/8/2025 5:52 PM, ha...@finne.net wrote: > >> I am a new GnuCash user. I have several problems when trying to import an >> account tree from an accounting program (Mamut Datax) I have used before. >> One of these problems can be described as follows. >> >> I export the account structure from my MD system to a csv file. I then use >> MS Excel to restructure the information to fit the input requirements for a >> csv file that will define a GnuCash account tree. During the import to >> GnuCash, I assign my MB Account Type field to the Type field of GnuCash. >> Once imported, the account tree looks ok, except that the Type field for >> each account is empty. It does not matter whether I use the original US Type >> typology or the built-in Norwegian Type typology. I understand that a >> subaccount cannot be assigned a Type that is not compatible with the account >> above it in the tree, all the way up to the five fundamental account types. >> And I make sure the sequence of accounts in the csv file defines the >> hierarchy top-down (should it matter). Please help me sort this out. >> Assigning account Types manually after the import is possible, but I would >> rather solve this in a more automatic manner. >> >> -- Håkon > > I've done this sort of thing several times in my working days, so can see you > are leaving out a critical step (when migrating between databases) > > a) FIRST do an export from your DESTINATION and make sure you can import that > back in (in this case to another instance of gnucash books) > > b) DID that work? Did everything you expected to see appear where it should? > > NOTE: These first two steps are to isolate potential problems. If an issue > shows up doing "a" and "b" it would show up going data source to data > destination no matter how perfect you did the rest and you'd be looking for > the problem in the wrong place. In other words, skipping those first two > steps only looks like it saves time. In practice, will save much more head > scratching time later. > > c) OK, you NOW look at the format (of that export from gnucash) using your > favorite editor? See where all the fields are? All .cvs means the fields are > delineated by commas, NOT that their order is correct. Now you look at your > export from MB. Not likely in the same order. You'll possibly need to write > something to fix if no "reorder tool" available <<here I'd always be doing > that, roll my own, then leave that in a department library as a tool >> > > NOTE: If there is SOMETHING in the gnucash export you can't find in the MB > export may have to fill in manually. > > Michael D Novack > > _______________________________________________ > 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.
