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
  • 0

    If you watch the conversion process, you'll see the data get converted to each Sage 100 version, on it's way to your current version.

    They are represented by 5.1, 5.2 etc....onward to 7.###

    So during our current Sage 2014 to Sage 2023 conversion runs, we see several loops through the code that updates each version, then the code repeats

    for each additional version until it ends on your final selected Sage 100 upgrade edition.

    Our conversion takes about 10 hours to complete. But it works.

Reply
  • 0

    If you watch the conversion process, you'll see the data get converted to each Sage 100 version, on it's way to your current version.

    They are represented by 5.1, 5.2 etc....onward to 7.###

    So during our current Sage 2014 to Sage 2023 conversion runs, we see several loops through the code that updates each version, then the code repeats

    for each additional version until it ends on your final selected Sage 100 upgrade edition.

    Our conversion takes about 10 hours to complete. But it works.

Children
No Data