Sage 100

I'm performing my first 4.4 to 2018 upgrade soon. I am copying the procedure of @BillPfahnl and zipped up a 2017 install to download to the customer's server. From there I intend to run 2017 without fully installing so that the Crystal DLL issues don't appear. Since I won't print anything from 2017 that shouldn't present a problem. Has anyone run into any other issues with this method for these multi-step upgrades which are required for upgrading from any version earlier than 4.5 PU8 because of Sage 100 2018 requiring at least 4.5 PU8 to migrate from?

Good luck. Is PR or JC in the mix?

I am working on one that is finally coming up from 3.04! Fortunately I'm a bit of a hoarder so I had two old servers with 3.71, 4.30, 4.50 and on. I didn't see what Bill's method was however I'd like to see it. What worked for me is to rebuild the data in current level and convert it to 3.71, then I ran rebuilds in 3.71 and onto 4.30 and jumped into 2017. I took it all the way to 2017 and everything is fine outside of some minor historical transactions that they will never use. This client also has BOM, WO to make it more fun! We will be going live in a few weeks after my testing but it seemed to work out!

Basically what @BillPfahnl is recommending is to COPY a vanilla folder of Sage 100 vxxxx to clients server (do NOT install). Create a Sage Vxxxx icon to launch the copied version so you can migrate the data to the intermediate stop. Then you can migrate from this level to the client's installed v2018. Very simple and easy to do.

Thank you Jeff! If this data wasn't so old, I would definitely try it but since it's taken me nearly 17 years to convince them they need to upgrade, I was climbing up the chain since I had the resources to do it. Good to know for any future 4x's!

The problem I ran into recently using a non vanilla systems is that the UDF's (if any) from non vanilla system are created in the migrated company version. Be careful.

Good point @JeffSchwenk - I expect to be testing this soon and I'll shortly update any issues that I encounter. I zipped a v2017 and threw it in Dropbox then instructed IT to download and unzip to the new server. Hopefully, I don't run into many more who are on versions prior to 4.50.