So im wondering if perhaps the way we have our environments setup is wrong because our live version is constantly not the same as either pilot or third. That makes it impossible for our dev team to be able to export tested solutions to live due to version differences. Obviously we can’t have our team testing new functionality in live as they could break functionality in our day to day.
Am i correct in assuming at least 1 of our secondary environments should align with live or is this just a character flaw of epicor?
You will want to set yourself up with CMP (Cloud Management Portal) access, if you search for that within the help in Epicor there’s a user guide.
From CMP, set whichever environments you don’t want ahead of live to user-controlled on the upgrade page. Then you can upgrade it on your own schedule (until Live upgrades, at which point it is forced)
Right now we’re in an upgrade transition window. Epicor released the new version 2026.100 a couple of weeks ago, and Cloud customers have had their PILOT and THIRD environments upgraded to that version so they can test their processes and customizations PRIOR to having their LIVE environments upgraded, so PILOT and THIRD are on 2026.100 while LIVE is still on 2025.2. The schedule for upgrading can be found at the Kinetic In The Cloud link on Epicweb.
The company name in your profile indicates you are probably on the US Central datacenter, so your LIVE environment is scheduled to be upgraded on the weekend of July 10-12.
Within this upgrade transition window, I might recommend that your dev team do much more process and data testing to make that LIVE transition smoother.