Wish me luck — I just downloaded the install files today. LETS GO!!!
No test environment. No sandbox. No pilot group. Straight to prod, baby. Isn’t this the CI/CD way?
Rollback plan? You’re looking at it (crossing my fingers).
Change advisory board? Told them about it at the coffee maker this morning.
Backups? I’m sure somebody’s got that covered.
Read the release notes? That’s what Monday morning is for.
Go-live is next week. Users have not been notified. Training deck is still blank. Honestly might just wing the whole thing and see what breaks.
If you don’t hear from me by Tuesday, let me know if you have job openings.
Any of you guys have any helpful hints to make the weekend a success? Asking for a friend (me).
Not Quite… CICD releases are all minor upgrades… going from 2023.2 to 2025.2 is upgrading through 4 major upgrades. we always encourage testing for major upgrades… of course, you CAN skip direcly from 23.2 to 25.2, but you should test in a test account before going into production.
I mean, *I* wouldn’t do it, but in 8 years of doing upgrades, I don’t know that I could tell you a thing that happened in testing that I couldn’t have tackled over an upgrade weekend.
Except for a custom AR invoice that broke every year until it was done right a few years back, and now that never breaks either.
Depends on how customized you are, I guess.
Also, the users usually do not do the testing we ask them to, so you only really find out after the upgrade anyway.
The fastest upgrade cycle for me was two years ago. We were on 2022.2 in browser only. It was a disaster; server kept crashing. Jumped to 2023.2 three months later with very minimal testing - because seriously anything was better than the “I’m going to lose my job” feeling for the 3 months on 2022.2.
Upgrade was started and finished on a Friday evening after work. And the system was fine for the 18 months till we decided to go to 2024.2.
But… then other random things do happen, like the backup service goes down that very evening… like this past October. (We had to push back to Saturday.)
It’s an on prem thing Mr cloudy I think Mike is referring to the Epicor data folder on the app servers.
I’d just rename the old then let then let the install create a new one.
I did a fresh install of 2025.2 the other day and I noticed it added a file to the Epicor data folder I have never seen before, contents seemed to be encrypted.
We went from 2023 → 2025.2. Biggest headache was the Classic → Kinetic migrations. The Kinetic-> Kinetic screens were mostly Ok just a but jumbled. No issues go live with the accounts and mostly seamless. Beyond “we don’t like this new interface” and Classic to Kinetic things we missed.
Yes… Make sure Accounting has posted everything, and run a COS/WIP Capture prior to you starting the upgrade. There should be no open “Groups” (i.e. AP, AR, Bank Recs, etcetera) and nothing showing in the review journal.
This is especially true when crossing major version upgrades, as the posting rules are likely to change slightly and anything not yet posted could get stuck in limbo, generated from one group of posting rules, and then trying to complete under a modified set of posting rules.
Always make sure the “Prerequisites” for each version you are passing through are done.
Also review each major version for specific Post-Upgrade requirements to ensure you perform all that are necessary (i.e. for 2024.1, 2024.2, 2025.1, and 2025.2).
I would also make sure there are no active entries in MES if you use it… Check Shop Tracker: Who Is Here and end all activity that shows and clock them out. Do that prior to Finance running the COS/WIP Capture.
Quick update on this weekends “strategic deployment initiative”:
Install files: still downloaded
Release notes: still unread
Backups: Dave said he’s “pretty sure” they ran
Test environment: I renamed prod to “test” so technically yes
Management approval: got a thumbs up in Teams, counting it
Training materials: users learn best by doing
Going in hot this weekend. The database has been blessed by a priest, a rabbi, and one guy from accounting who said he “had a good feeling.”
I did finally crack open the release notes. Turns out there’s a “recommended upgrade path” document. 847 pages. I scrolled to the end, it just says “good luck.” Close enough.
Management asked if we have a rollback plan. Told them yes, then Googled “how to rollback Epicor” in the same meeting. The autocomplete was not reassuring.
Any of you ever restored from a backup you weren’t 100% sure existed? Asking for prayer requests.
If anyone wants to place bets on which module breaks first, Venmo me. Current line has MRP at -140 and Financials at +220.
For me it’s an on prem thing because we’re still using the full client and it’s where the cache is actually located. Cloud users can ignore many of my gripes, because they pay$$ to do so.
I think Mike is referring to the Epicor data folder on the app servers.
