Update on “Target: next week” items (work in progress)
Time for an update. @JenTrifty and I promised an update on some of your questions after a week (see post 383 on EpiUsers: (Epicor Kinetic Innovation Moves to the Cloud) … well, we just realized we got busy, and after all the 679 posts and 13 days… we are late… but we did not forget. We’re consolidating inputs across Product, Cloud Ops, Support, and Security/Compliance so we can respond consistently and avoid creating new confusion.
1) Customization & integration “what changes in SaaS” matrix
We’re building a practical matrix that spells out what works as-is, what typically needs refactor, what’s restricted in managed SaaS, and the recommended patterns going forward (BPMs/Functions, BAQs/Reports, REST/integrations, UI/personalizations, printing/labels, file movement, and anything reliant on direct DB access/writes).
Reminder: Kinetic is the same product line on-prem and SaaS. This is not a reimplementation—but some access/ops patterns do change.
2) Upgrades, hotfixes, and escalation (incl. CI/CD cadence)
We’re documenting how we classify hotfix vs patch vs release, what to expect for timing/comms, and the escalation path for business-critical issues (including what info speeds resolution). As we move further into a monthly CI/CD delivery model, along with the Cloud Management portal, we’ll also clarify how we balance faster delivery with stability, validation, and safe rollout.
3) Data ownership & options (including hybrid exploration)
We’re outlining available export options (data + attachments), what can be automated via APIs/reporting vs what requires assistance, and what a structured transition plan looks like. Also, as Kerrie Jordan mentioned on the podcast with @josecgomez and Eric Kimberlin on LinkedIn SMB ERP at a Crossroads; on-Premise, SaaS, and the Real Tradeoffs , we’re investigating hybrid cloud options for scenarios where SaaS isn’t a straight fit… we will share more on this in the coming weeks as that analysis matures.
Compliance note (regulated/A&D): If Epicor SaaS doesn’t yet support a required regulation, we’ll work with the customer on options. This may include continued Active Support availability for on-prem while compliance alignment is evaluated, achieved, and validated for cloud readiness. Also see @Vaibhav’s direct communication on this subject here: Vaibhav’s EpiUsers Post & Comments
We will continue to share more information as it is gathered. We know that these (and more) will be great discussion topics at Insights 2026.