Sage 100

Sage FAS upgrade question. We have been told by two Sage FAS support staff that 2013 to 2017 requires Sage professional services to convert or incremental upgrades through each version. Another, stated to just backup out of 2013 and restore in 2017. We tested, reports match, but are nervous when things are too easy and too good to be true. Experience and input is appreciated.

As long as everything matches, you should be good! Did you totally uninstall the old client and install the new one?

I have done upgrades and I still do them version by version, not sure why Prof Services would be needed. Is there a limit as to what version you can backup and restore to and skip the version to version steps?

We have not uninstalled the workstations. They indicated if you point to the new install, it will recognize and upgrade. As for the professional services, I am not sure it was not just merely you-are-not-worthy mentality. As far as how many version that backup restore will work, I was looking for an answer from someone with experience.

I did a FAS UG not too long ago and my memory was that the old version-by-version is no longer needed and you can upgrade straight from 2013. Make a backup and dive in...

Is FAS 2017 compatible with Sage 100 2016?

I have recently confirmed with Sage FA support about the path for upgrading. Have a client going from 2009. here is the scoop: UPGRADING FROM OLDER VERSIONS OF SYBASE SAGE FIXED ASSETS MUST GO IN ORDER UNTIL 2013 AND THEN AND JUMP TO MOST CURRENT DESIRED UP TO 2017 2009.1=>2010.1=>2011.1=>2012.1=>2013.1 =>(2016.1 OR 2017)

@JaneCavanaugh the integration chart on the portal is showing FAS 2016.1 for both Sage 100 2016 and Sage 100 2017 as of October 28

Thanks so much @RonGouveia

I also heard both stories from FAS support. But the more knowledgeable tech stated that 2013.1 can go directly to 2016.1 or 2017.1. However, earlier versions needed to be incrementally upgraded.

I'm looking at this for an end user who says they are on version 12 (I'm guessing that means 2012). I wonder if the reason for the PSG warning is that Sage does not openly distribute these older versions so an end user would likely not have ready access to the older releases needed to upgrade incrementally until the hit 2013.1 which I think can be updated directly to 2017? : _Note: Databases from 2012.1 and prior will not convert directly to 2017.1 and will require a PSG engagement to update._