Sage 100

What do you think about creating a ""white paper"" with 15 tips (or maybe we'll reduce the #) to consider before upgrading Sage 100 ERP 2013? We can either use this internally (I think it would be a big help) , within our firms or provide it on the web site. Here's the layout that I'm thinking of. I know the tips about modifying AP checks, loading LM5004-T, etc are things a lot of us have in our heads. Why not commit these to a list and distribute to our consultants so that we collectively don't all waste time solving errors that keep coming up on these upgrades. https://docs.google.com/document/d/1C8SM_qxBXgjTXd0IqXyjTJGNr0F1p6DP6uSW-dMuKzc/edit?usp=sharing

I've added #4 and #5. Feel free to edit/add to as needed.

Added #6 - need more people to add tips and to also fact check 1-6 please.

Great list... one comment on item #7.... Wikepedia is not a reliable source of information.. For Hyper-v cite: http://www.microsoft.com/en-us/server-cloud/hyper-v-server/default.aspx

Added #9

Thanks Doug - and feel free to note item # 7 as well - the more info the better.

I added some to your #9 to give what I think are the three main options (SI, BizNet, RenovoFYI).

Regarding #3: When enhancements exist, I always perform upgrades from a copy of the live system, not the original. Uninstall the enhancements from the copy, not the live system. Many times, enhancements may not function as they previously did, and without access to the original installation, troubleshooting becomes extremely difficult.

Thanks - good point and I added that (see if I edited properly). In most cases the problems I am running into are the dreaded Hightower modules which don't seem to uninstall cleanly and the customer never used but installed to test. Feel free to add more directly to the document if you think it needs clarification. Maybe we should have a whole section of how to ""stage"". Generally I upgrade from a copy on heavier used systems or those with inventory (bigger upgrade projects). For smaller systems I tend to: a. Copy the live data company to backup company code b. Migrate data when everyone is out of system (exception: Inventory when I know changes might be made then I will use a full copy of the MAS system). c. Use the live data with backup company code to compare data d. Re-migrate from the live The more I think about it the more it seems alike a ""how to stage your upgrade"" is a great question to put on here?

I just use a copy of the installation. Making backup companies is not apples to apples, as scripts, enhancements and custom forms may not work on the backup... making comparison difficult. Sometimes I have to edit sy0ctl to remove references to HTI enhancements, so upgrading from a mirror install is critical.

I added this note to #5 Disable Sage Advisor Update (SAU): UPDATE: Sounds like you may just be able to uninstall SAU via Windows Control Panel, which also removes the SAU Service.

This can be an excellent document to use as part of an upgrade campaign. Spurs thought and fear for the uneducated and educates the technically competent.

I just modified note #1.

Better Yet, when finished, this should be put on 90minds blog and the way to get it is to sign up via mailchimp or aweber. Then send the tips out once per week to keep us 'top of mind'

We need 4 more tips then we an polish and post.