Why am I forced to convert test company data after an upgrade?

SOLVED

Note: this is more of a "why" question, not related to this thread (which was an enhancement conversion bug).

When upgrading a customer system (currently v2020 Premium to v2022.2 Premium), we bring along test company codes so user permissions (to their correct test company) are retained.  After the upgrade, I converted all the Live company data, which took HOURS to process, and skipped converting the test company data... planning to just refresh them with fresh copies of the converted Live data.

However, I am blocked from refreshing test company data without converting.

Why?  This seems like a complete waste of time, since I am about to wipe out everything in the test company codes.  Yes, I could remove a bunch of modules and decrease the processing time, but I have about a dozen test companies to go through, and the GL module (mandatory) is often the biggest data set... not to mention rushing through a series of module removals is not something I want to do routinely.

Obviously this error (checking conversion status before copying) was purposefully programmed for a reason.  I'm just curious what that reason is.

(BTW, I really like the company type filters on the bulk conversions... a big help for sure.)

Parents Reply Children
  • +1 in reply to Kevin M
    verified answer

    FYI, I've exchanged emails with Sage, and their reasoning is that you can Copy individual modules, causing problems if the starting data doesn't have the new table / column structure... which makes perfect sense.

    My own thought (after posting) is that, for a migration from Standard / Advanced, the initial company conversion is what creates the MAS_### database in SQL, so checking for company conversion status will prevent issues with that scenario too.

    A couple thoughts came out of the email exchange, and I'll post an Idea with details when I have time to think it through properly.  When done I will post a link here so anyone interested can vote.