Sage 100

I have an upgrade from v4.4 to v2018. 2018 will be installed on the same Windows 2008 server that v4.4 exists on. Do you have any recommendations for insuring a smooth migration so both versions can co-exist on the same server?

Isn't this a situation where you want to migrate the data to v4.5 first before making the leap to v2018 hyperspace? And I think you will have an issue with the Chillkat dll's once you get to v2018. And my final concern is the Crystal 2016 issue that v2018 introduces. BTW, is the 2008 server R2? If not, v2018 will not install on it. Why is the client not taking the opportunity to update on a new box with 2016 or at least 2012? Perfect time to, plus you can create a VM on the new install.

Version 2018 will NOT let you migrate from 4.4 (just tried last week). I installed 2016 and was able to migrate to 2018 from there. (This was a vanilla core modules only customer, BTW.)

Thanks Jeff and Therese for the great info. This is a medical office and they only use GL, AR, AP. So, no paperless office or forms other than checks. The reason they aren't upgrading the server is because, uhhh, what's the word I'm looking for.... oh yea, they are cheap. Good to know there is an intermediate upgrade necessary.

And the check form doesn't convert correctly either. It needs adjusting (at least in my customer's it did).

If I'm not mistaken, you will lose the ability to print in version 4.4 unless you install the 2018 client on all workstations that need to print. The Crystal versions are not compatible. There are several KB articles on this.

I might add that mine was an upgrade only, no parallel testing. Again, they are basic core-only so not a lot of forms, reports, etc. And the check form I mentioned above? She forgot to select the DEFAULT form that I always set up to avoid the pitfalls with the STANDARD form, e.g. check type, etc. Funny, but I was at her desk reminding them to select the correct form. We even printed out a test one so I was surprised when she emailed the next day saying the form wasn't correct. I even asked, ""You selected the correct form code?

Thanks for the info. Yes, I remembered something about copying over the .config file to the ""old"" version on the server, and all of the workstations. These are the scenarios that I am trying to defend against... installing an ""upgrade"" then the current version doesn't work.