That’s another valid and safe option. The OP noted 1000+ accounts to migrate though. So even 1 transaction per account would not be fun.
On the upside, I discovered that accounts with zero transactions can have their type changed. So if the OP had some empty accounts, those could be done rather painlessly. (if slowly via GUI) I’d recommend not to retain individual A/R accounts per customer. While there are some advantages to doing so, I’m not sure GnuCash *needs* this treatment. It would be wise to investigate the ‘why’ of the individual accounts before the OP proceeds with a change. Some apps (and certainly paper books) almost necessitate sub-accounts per customer. (and per Vendor under A/P) But GnuCash does not and can handle tracking amounts owed or owed to with a single A/R and A/P account. One can always employ special or other A/R or A/P, but they may not be as necessary as one might think. Regards, Adrien > On Apr 29, 2020 w18d120, at 8:07 PM, David Carlson > <david.carlson....@gmail.com> wrote: > > If the number of transactions involved is small enough to consider fixing one > at time, one could set up the proper tree, perhaps append _bad to the > incorrect account name, then, from a transfer account change transaction s > one at a time. > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
