Sage 100

It's been my standard upgrade procedure when upgrading from SAGE 100 STD v4.xx to v2013, v2014 or v2015 to install the v201x software on the client's server along side the v4.xx system. I perform a test upgrade and re-create custom UDFs, forms, etc. in the new version. The client continues to run on the v4.xx system until I'm done and ready for ""final"" upgrade. Can I follow these same procedures when upgrading from v2013 to v2015 or 2016? TIA

Yes. That is how I have been doing mine.

I do this all the time. Remember to copy our PL logs over a final time. I did have to take extra steps with the logs coming from a v43 to v2015 which I just went live with. No real issues....... yet!

I agree, that's the way I've been doing it. I would add one extra step, make a copy of your 5.x MAS90 directory as soon as you apply the PU so if your migration blows up (and subsequently takes your system files south with it) you can just restore that from backup. Otherwise you end up uninstalling and reinstalled. Word of warning, though: I have now done about 5 MAS 200 SQL to Sage 100 Premium upgrades and in each one I have found very unusual, and tricky to resolve, issues that (surprise) were not written up by Sage.

Been there done that also @CullenLowe - Always make a copy of the initial install prior to the first migration. A painful lesson to learn.

Thanks for the help Everyone!