A conversation next week

Hi All,
Thank you all for your feedback. I’ve read every comment that has been posted in the last few days. Im looking to have a constructive conversations with a few of you next week to discuss your concerns (agency, compliance, etc). I will have my leadership team join as well. Thank you
Vaibhav

23 Likes

Looking forward to hearing the outcome. Hoping for a productive conversation. Hopefully there’s a compromise in the middle somewhere.

7 Likes

Thank you Vaibhav.
For us as a government agency working with National Security, the lack of an on-premises fully supported ERP offering would mean that we need to find a new supplier. After 20 years of using and investing in Epicor products, that’s really disappointing.

6 Likes

This decision would have benefited from earlier discussion prior to the press release. While Epicor has consistently emphasized listening to its customers, I have not personally had an opportunity to provide input, such as through a survey or formal feedback, before this direction was communicated.

That said, I am hopeful for a constructive dialogue on how we can rebuild confidence, restore trust, and explore ways to reconsider or refine this decision.

Respectfully,
A long time customer who has experienced several Epicor C-suite and leadership transitions

19 Likes

Looking forward to the free flight, beer, and bbq.

11 Likes

Hey @Vaibhav_Vohra ! I want to say I really appreciate you joining in on the discussion. It does help. Since is seems like you’re up for a little bit of having some discussion about difficult topics can I throw a question out there?

Given the past couple years of the direction that we’ve seen with Epicor. Starting with the move the browser, then the announcement to browser only. Then the second big announcement of maintenance costs increasing up to 10% per year, and now this announcement that epicor will be a cloud only company going forward from 2028 on. All 3 of these moves will force very time/labor/investment heavy time periods for any long time customers of your product. It also shows a willingness to change directions and strategies that can cost customers large sums of time, money and productivity in a relatively short (in the manufacturing world) amount of time. The first move to browser can invalidate years of development and engineering for working with the shop floor. The move the cloud functionally gives the keys to the kingdom to Epicor as the customer is forced to pay for any maintenance increase or simply have their ERP service cut off with the flip of a switch. They can’t even walk away without a fight since Epicor can make it difficult to get the data they need to move to a competitor. Plus, implementation takes time, and they will have to pay for 2 systems while the transition to someone else. Those decisions make confidence in business erode.

On top of these, we have always seen you can also see in the other thread an obscurity of what we are even paying for. Modules that must be bundled with other modules. Modules that once are turned on can’t be turned off. Concurrent licensing with opaque clarity on how rules of when licenses are used or not used. I know that anyone here has looked through an epicor invoice and been confused because it’s never been clear, and it’s not getting any clearer. Epicor billing has never been something that was clear and concise. We always felt that we were getting something slipped by us by design, hoping we wouldn’t notice and keep paying for something we didn’t need. That’s not getting any better either.

What are Epicors plans to be able to build trust? And it can’t be a pinky promise. You’ve burned all of those up. We don’t believe it any more. What happens when a something happens that costs a company real money, real time, real effort? What’s their recourse? What kind of guarantees can you put in place so that the customer can hold you accountable?

I hope that’s not too hard hitting, but I think it’s a valid question. You want customers to trust you as a partner. We want you to put some skin in the game. Not just take it all from us.

22 Likes

A saw the announcement today on the EpicWeb home page. Although we moved to the cloud earlier this year I immediately thought of the impact on customers that have invested in an on-prem infrastructure to support Epicor ERP. I think at a miniumum there should have been a 5-year notice.

4 Likes

Even if you are cloud. Having the ability to pull the rip cord and move to on prem if the need arises IS a selling point. This goes back to customer control and disaster planning.

9 Likes

Do we have any details on this conversation yet? Not sure if I missed something

12 Likes

The problem isn’t just about the notice period though. It’s that some Epicor customers/industries can’t switch to the cloud, period. Whether it’s 10 days or 10 years of notice, it’s still not viable.

3 Likes

And if you don’t upgrade (which if your version number your profile is correct, doesn’t seem like a problem) then you don’t have to. You can stay on your version as long as you want on sustaining support.

2 Likes

Hi All – the conversations continue (thank you for those of you involved this week). The focus is control, ROI, certifications (like in A&D), stability. Focus groups for each specific area to have constructive conversations are critical.

Epicor is committed to supporting customer’s compliance with applicable industry and government regulations in Epicor SaaS solutions running in the Epicor Cloud. If Epicor SaaS does not yet support compliance with a specific regulation that a customer is responsible for running their business, Epicor will work with the customer to assess available options. This may include continued Active Support availability for on-premises solutions to that customer while compliance alignment is evaluated, achieved, and validated for cloud readiness.

8 Likes

Respectfully, if compliance was the only roadblock identified in these meetings, Epicor is missing the point. And clearly the attendees weren’t representative of the on-prem community. There are several other very well explained roadblocks and concerns in the other post. This doesn’t make it feel like Epicor is listening to what the on-prem users are saying.

Hopefully there is more to be said about control.

9 Likes

If stability of Epicor Cloud SaaS is one of the focus groups we’re interested to help as current Epicor Cloud SaaS customer.

3 Likes

Chad he said “control” (which is the on premise control we’ve all been taking about

“Roi” (value money cost finance)

“compliance” (certifications etc)

And Stability

I think all those points are being considered and talked about. We (the community) has certainly brought all these up and I know the leadership at Epicor is well aware of them

7 Likes

I hope they are. But the only elaboration was on compliance. So it makes it seem like the others may have taken a back seat.

8 Likes

Yes all areas – i realize that by going into 1 specific area that may have created the wrong impression.

8 Likes

It does give me, and possibly others, the impression that was the only area out of the four you were focusing on. I’m glad that’s not the case.

5 Likes

I can confirm that all areas are being examined by our teams. Vaibhav simply dove deep into the compliance topic since it is a vital business concern of just about everyone.
Thank you all for the continued discussions. We look forward to all the input as we continue to meet.

4 Likes

Long overdue study-up on Docker for just this reason has been initiated.

4 Likes