Sage 100

Has anyone observed that when you migrate a Sage 100 v2016 customer from 100 to 100c the reg keys appear to dynamically change behind-the-scenes? I have a very small one that dropped IM and SO and these modules de-registered themselves which I think happened because SA grabbed the new entitlement. Not totally unexpected but caught me by surprise. I also wonder if there would be a problem re-using the perpetual keys? Will Sage just swap them back for 100c? Thought: If customer is going to migrate 100 to 100c be sure to build that into the cost of upgrade otherwise if it happens midstream it should be a paid change request.

Also, in my mind - if keys are automatically updating / de-registering modules - shouldn't the old data remain in a read only state?

This was exactly my issue with my 100-100c client with the payroll thing. The reg keys first changed themselves to 100c without payroll, then changed themselves to payroll ONLY. And yes, I tried putting it back to the old keys and it just changed itself back.

So does someone need to hack the keygen program just so we can fix it and keep our paying customers running? It's getting to the point where it would be hard to recommend this stuff even if it was free...

I think for now we need to pay more attention of any changes to the registration keys and avoid making changes during projects or upgrades.