Hi @dougmcbride79 

It is going to depend on a few things:

1. What customizations do you have in your instance? Such as ISV solutions and internal customizations. 
2. Are there any bugs that need to be addressed and a newer build has the fix for those?
3. What current version are you on? Acumatica retires versions yearly and you need to upgrade then. 

Here is another article with some key advice you can review. https://community.acumatica.com/everything-else-119/upgrade-suggestions-7345

Hi @dougmcbride79.

Adding to what @kbeatty21 said. More recently, we have found it is critical to let builds age and read the latest Known Issues document before deciding on which build to go to. The known issues document is great because it groups issues by workspace. It is easy to find issues that may affect you, and which you can just skip right over. Builds used to be a non-event to move to, but unfortunately not recently. It very much depends on which workspaces you use.

Thank you.  We have no third party plug-in programs.  And no significant customizations.  

Also, if you have someone technical on your staff, get accustomed to setting up your own local instance of Acumatica and doing the upgrade on that instance first. If everything runs ok on the test, then you are probably ok to do the production upgrade. This isn’t a small lift, but will pay dividends if you have someone in your org learn how to do it.

Great idea. Thank you.