Epicor Kinetic Innovation Moves to the Cloud: On-Premises Development Ends in 2028

Chris_Conn · January 6, 2026, 1:19pm

Wow, who would think Epicor would mislead their customers and then spit in their face, particularly after the events over the last 4+ years.

Totally out of character

Doug.C · January 6, 2026, 1:28pm

I’m not at all concerned about moving to cloud. It is inevitable. What I am concerned about is the track record they have of support. The other cloud instances I have had dealings with have had support teams that were able to actually fix/troubleshoot issues. There are some good ones at Epicor, but they are unicorns. Taking that away from my team means our business will suffer waiting on support to fix issues (reporting is the most recent issue).

chaddb · January 6, 2026, 1:29pm

This is my biggest concern. We will be stuck waiting for Epicor to fix something.

Daniel_White · January 6, 2026, 1:31pm

That is mine as well.

aosemwengie1 · January 6, 2026, 1:35pm

What, you want to be able to run your stock status report or something?

JMPCONJ · January 6, 2026, 1:41pm

We already moved to the cloud. We’ve seen issues already with outages and support. With more users heading in that direction it’ll probably get worse. This past monthend was the first stumbling block with a failed scheduled SSRS report - the Stock Status Report no less - for one of our four sites. Hid the error text below. Good thing we rigged up an Access/ODBC run to capture the inventory as well.

SSRS error text

Program Ice.Services.Lib.RunTask when executing task 2703770 raised an unexpected exception with the following message: RunTask:
Ice.Core.SsrsReporting.SsrsCaller.SsrsException
at Ice.Core.SsrsReporting.SsrsCaller.RestReportingService.ThrowIfNotSuccess(HttpResponseMessage responseMessage) in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsCaller\RestReportingService.cs:line 351
at Ice.Core.SsrsReporting.SsrsCaller.RestReportingService.ListChildren(String itemPath, Boolean recursive) in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsCaller\RestReportingService.cs:line 225
at Ice.Core.SsrsReporting.ReportProcessorBase.IsLatestVersionDeployed(IReportingService reportingService, String itemPath, String contentHashForLatestVersion) in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 368
at Ice.Core.SsrsReporting.ReportProcessorBase.DeployReportIfNeeded(String printProgram, String fullReportPath, SsrsConfigurationInformation configurationInfo, Func1 reportingServiceCreator) in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 458
at Ice.Core.SsrsReporting.ReportProcessorBase.RenderReport_HttpClient(String ssrsRenderFormat, String printProgram, Boolean ignorePageSettings) in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 335
at Ice.Core.SsrsReporting.ReportProcessorBase.RenderReport(String ssrsRenderFormat, String printProgram, Boolean ignorePageSettings) in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 242
at Ice.Core.SsrsReporting.ReportProcessorBase.RenderReportForPrintOrEmailReport(RenderedSsrsReport renderedReport, Boolean serverSidePrint, Boolean ignorePageSettings) in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 685
at Ice.Core.SsrsReporting.ReportProcessorBase.ProcessReportPart(String reportLocation) in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 149
at Ice.Core.SsrsReporting.StandardReportProcessor.ProcessReportParts() in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\SsrsReporting\StandardReportProcessor.cs:line 31
at Ice.Core.RoutingAndBreaking.ReportPersister.Persist(ReportInstanceInformation reportInstance, Func2 reportsRenderer, Action1 fillSysRptLstRow, Action2 processReport, Func3 filterTableAttachmentsFunc)
at Ice.Core.RptBase.ReportSsrsDatabaseBuilder.RenderUnroutedSsrsReport() in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\RptBase\ReportSsrsDatabaseBuilder.cs:line 355
at Ice.Core.RptTaskBase1.XMLClose() in F:_Releases\12.0.100\Current\Source\Server\Internal\Lib\TaskLib\RptBase\RptTaskBase.cs:line 219
at Erp.Internal.IM.IMR40.XMLClose() in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\IM\IMR40\IMR40.cs:line 1256
at Erp.Internal.IM.IMR40.PrintReport() in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\IM\IMR40\IMR40.cs:line 3239
at Erp.Internal.IM.IMR40.InternalRunProcess() in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\IM\IMR40\IMR40.cs:line 1534
at Erp.Internal.IM.IMR40.RunProcess(Int64 instanceTaskNum, String outputFileName) in C:_releases\ERP\ERP12.0.100.11\Source\Server\Internal\IM\IMR40\IMR40.cs:line 1411
at Ice.Hosting.TaskCaller.InnerExecuteTask(IceDataContext newContext) in C:_releases\ICE\ICE5.0.100.11\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 70
at Ice.Hosting.TaskCaller.ExecuteTask() in C:_releases\ICE\ICE5.0.100.11\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 61
at Ice.Lib.RunTask.BpmFriendlyTaskLauncher.Run(String sessionIdPrefix, IceContext db, Action taskRunner) in C:_releases\ICE\ICE5.0.100.11\Source\Server\Services\Lib\RunTask\BpmFriendlyTaskLauncher.cs:line 57
at Ice.Services.Lib.RunTaskSvc.InnerRunTask(Int64 ipTaskNum, Boolean suppressTransaction) in C:_releases\ICE\ICE5.0.100.11\Source\Server\Services\Lib\RunTask\RunTask.cs:line 411

Chris_Conn · January 6, 2026, 1:42pm

When you put it like that…Ouch!

Even worse, we’re paying for our own demise.

Doug.C · January 6, 2026, 1:42pm

We have the added fun of needing it to be HIPAA compliant!

chaddb · January 6, 2026, 1:44pm

There’s a lot of on-prem customers with very strict compliance requirements.

bderuvo · January 6, 2026, 1:46pm

I’ll add some perspective here as both a customer and someone who’s been very public about our cloud transition.

We made the decision to move to Epicor Cloud well before any of these recent announcements. For us, it wasn’t about marketing buzzwords or “innovation” — it was driven by very practical internal reasons: scale, growth, and access across multiple geographic locations. Those needs weren’t going away, and on-prem was increasingly becoming friction instead of an enabler.

I’ve presented at Insights on our transition and tried to be very open about what that experience was actually like:

What was relatively easy

Database migration
The core upgrade itself

What was hard (at the time)

SSRS report migration
Client deployment

What’s objectively better now

Our aging on-prem app server and database space issues are gone
Restores are simple and fast
The Cloud Management Portal is genuinely a solid tool
Cloud support has been very responsive in our experience
Replication database solves a few integration issues for us
System performance across 12 sites.

From a platform operations standpoint, cloud has absolutely delivered value for us. I am a happy cloud customer — for our needs.

I’ve seen some estimates on cloud hosting costs, they are actually cheaper than you would guess.

That said… we all hear the same thing, over and over, and it’s not noise:

Upgrades are breaking things that should not be breaking. EpiUsers should not be Epicor’s QA team. They have to improve the QA process to be a cloud only option. Epicor’s QA team uses this site for customer feedback and gauging the temperature of the community. This must improve.

We flex our upgrades, initially due to timing. Fortunately for us, this means most issues are worked out before we upgrade about two months after the initial release.

@timshuwy and team, thanks for communicating this clearly.

jkane · January 6, 2026, 1:51pm

Came into quite the announcement from @Vaibhav_Vohra this morning.

Do people think this will move companies away from Epicor?

Or will most jump to the cloud?

JMPCONJ · January 6, 2026, 1:52pm

We jumped in Sep25. Generally satisfied with performance - when it’s up. Too many outages and problems for my liking but I’m persnickety and expect five-9’s uptime.

JasonMcD · January 6, 2026, 1:52pm

This is my concern. We are hearing a lot of the opposite lately. What is your secret? Are you an “Enterprise” SaaS customer?

Also, really well said. I want to have the same optimism.

jkane · January 6, 2026, 1:53pm

I am currently on prem, but generally have not had issues when I worked at places on the Cloud. I actually prefer the web interface.

chaddb · January 6, 2026, 1:56pm

As a on-prem customer the reliability would be killer. Going from 100% uptime for years to whatever Epicor has.

JMPCONJ · January 6, 2026, 1:56pm

Same…we had a 3p-hosted-onprem and made the cloud leap. Browser’s been nice except for the monkeywrench called Edge Agent.
And our prior ERP was running in the cloud too - an IBM i/System-i/iSeries/AS400 or whatever nomenclature it now carries.

JMPCONJ · January 6, 2026, 1:57pm

It’s never been 100% regardless of plaform or location…but closer to five-9s would be nice.

chaddb · January 6, 2026, 1:58pm

Guess that depends on your on-prem environment.

Daniel_White · January 6, 2026, 1:59pm

On Prem here and the Uptime and timely resolving of issues is a massive issue for me going to the cloud. We have a lot of in-house apps that rely on data from our Kinetic system and having to migrate all of that to a cloud environment will be a huge undertaking. You only have to look at recent posts on here about Cloud issues to see that it is currently not a reliable QA’d system

utaylor · January 6, 2026, 2:00pm

Love seeing this version number… takes me back