Why are the preupgrade steps different for cloud vs on premise?

With on prem, I’ve always followed the steps in the “release upgrade guide” before upgrading - i.e., Make sure all groups are posted, finish all bank recs, review journal, etc. But for cloud I see no documentation indicating these steps are required for the upgrade this weekend which seems bizarre. Why would it be different?

On prem docs for 2023.2:

I don’t think we’ve ever done anything special for upgrades, besides testing them in Pilot ahead of time.

I’ve often thought the same. We are on prem, but we were cloud in 2017. And I always make sure on prem to do all of those steps, but right, I do not recall anyone ever telling us to when we were in the cloud.

Probably a good idea, though, to do all that…

Right that is what I am thinking but I don’t understand why there is no upgrade guide available to download for cloud customers with the steps in it. Did they just forget to post it?

I just completed an upgrade from Vantage 6 to Kinetic Cloud. Epicor provided a document with those pre-upgrade steps. I’m not sure if that’s posted to EpicWeb or if it’s provided by CAM/Project Manager. Don’t think I can share that document here because of copyrights. It was a spreadsheet titled “Epicor Upgrade Workbook”.

I’m very well aware of the document and the steps, that isn’t my question :slight_smile:

So this is the response from support:
“I just confirmed and there won’t be any changes or movements to your data. The upcoming upgrade is purely a version upgrade. In response to your question, none of your groups will be affected or posted prior to the upgrade.”

I interpret this to me we don’t need to do the pre upgrade checklist. Still confused why the preupgrade checklist would be required on prem and not for cloud.

My guess would be that since you are getting every upgrade, there is not the concern of jumping multiple releases like most on-prem installs do. Also, they are in control of the complete upgrade and can easily roll it back if something happens. For on-prem, they are just trying to mitigate as much as possible since they are only involved with support.

We moved to the cloud in June of 2022. At that time I asked about the pre-upgrade steps on future upgrades and was told we do not need to do those steps. My understanding is that now that we are in the cloud, we don’t have to migrate the data like we did before. I also wanted to point out that during our ensuing upgrades since then, we didn’t do those steps and it worked fine. Though, we did run a balance sheet to check against to make sure.

Yes but its illogical. Either its required or its not. If its not required, then it shouldn’t be in the guide for on premise customers either (or they should specify exactly which upgrade pathways its required for).

More concerning, they emailed out today that the upgrade window starts at 10pm local data center time while Epicweb has said 7pm local data center time for months. Can’t get a clear answer and there is a huge difference in those times for us. One involves shutting down early and one doesn’t.

Wow so the “final” notification we received yesterday informing us that the upgrade would start at 10pm local data center time is incorrect according to support:

"Public cloud production upgrade window: Friday, November 3, 7:00 PM - Sunday, November 5, 8:00 AM Local Datacenter Time
we will fix the notification and you will see another notification shortly.


"

Did anyone ever get something official on this? Is there any pre-upgrade work that needs to be done? Like posting batches, WIP, etc.?

1 Like