Sage 100

Looking for SAGE 100 STD best practice for upgrades. I am doing my first upgrade that involves SPS. New client to me -- running SAGE 100 STD version 4.40 and wants to go to SAGE 100 v2015. I want to perform a test upgrade in my office to look for UDFs, Crystal forms, Custom Office, etc. How do I make sure I don't mess up with the SAGE Vault. Since their live system is still at version 4.40, they should be able to continue to process credit cards the old ""fashion way"" (not using SAGE vault) with SPS no matter what I do with my test upgrade. Right?

Move their existing data to your test system, wipe the credit card data from v4.4 and then do your test upgrade. If you look in the Knowledgebase, I think there might even be a doc on how to do this when they first came out with the Vault.

Thanks @KevinWesley I've wiped CC data from other SAGE 100 upgrades where a few CCs were in their Accounts Receivable data files, but they did not have the CC Processing module installed. I will also check the KB.

This might be helpful.

I do this right on the customer system which saves having to copy/reinstall. 1, Get RDP or unattended access 2. Install Dropbox (read only) with all my files 3. Install Sage 100 4. 4 step process a, Stage (install) b. Test c. Go Live d. Post Go Live I have not done extensive testing on the SPS portion and so far have not run into any issues. Usually if the system is going to barf on credit cards it will do so during the test migration. By staging off-site IMHO you are just introducing another thing to debug (when you finally move it to their server).