Our timeline for Go Live is conspiring against us with respect to version 2025.2 deployment on LIVE.
We have been working in THIRD on customizations among other things as we prepare for a Go Live for the new year. We had hoped to populate LIVE at the beginning of December and implement our customizations. This would give our teams time to start populating live transactional data that will not post until 2026 into the new environment over the course of December. However now that the update for LIVE has been delayed until mid-December I worry about being able to install the customizations into a different version.
If I have solutions for BAQs, Application Studio Layers, and reports in 2025.2 can I install those into 2025.1? Does anyone know?
BAQs you can kind of fudge and move backward (there is a thread here about it) but I don’t know of anyway to get Solutions, Layers, etc to back-port to older versions.
I am in a similar boat; I was planning on refreshing third with a copy of live early next week in an effort to do some additional testing for go live and now I won’t be able to do it for multiple weeks. I am not trying to be dramatic, but I see this having an impact on our ability to hit our go live date.
Wow! Similar here, this stinks like poo poo.
I contacted my Epicor Project manager, I recommend you see if you can do the same. Let’s try to push and see if they make some adjustments.
We were also planning on refreshing our Pilot DB but that’s also on hold I guess. 
We also planned on updating our Pilot with the Linux changes coming. Hopefully they push that update back until after 2025.2 releases in Production.
My project manager recommended I put in a ticket explaining my situation and requesting an early upgrade. We shall see how this goes.
I would also encourage you to talk to support, they seemed willing to help me out with a refresh of a non-production database with live data in light of recent delays.
Contact Support!
They upgraded my LIVE database for us so I am all good now!!!
Support for the WIN!