Who this is for
IT managers, operations managers, and business owners running Epicor ERP (E9, E10, or earlier) who need to plan their upgrade to Kinetic or evaluate alternatives.
Question this answers
What does upgrading Epicor involve, and what should we plan for?
What you'll leave with
- Epicor version history and support timelines
- Upgrade paths to Kinetic and cloud options
- How to handle customisations and integrations during upgrades
- Key risks and planning considerations
Platform overview
Epicor is a major ERP vendor with a strong presence in manufacturing and distribution. In Australia, you'll find Epicor across discrete manufacturing, make-to-order businesses, automotive suppliers, and industrial distributors.
The product history is layered. What's now called Epicor Kinetic has been through Vantage, E9, E10, and several rebrands along the way. Each major version introduced architecture changes, and many Australian Epicor users are running versions that are one or two generations behind current.
Epicor offers both on-premises and cloud deployment, with the cloud option becoming the default for new implementations and the target for upgrades from older versions.
Common version & support issues
Version sprawl. Epicor's naming history (Vantage → E9 → E10 → Kinetic) can be confusing. The key thing to know: if you're on E9 or earlier, you're running an architecturally older version. E10 is closer to Kinetic but still needs upgrading.
End-of-support timelines. Epicor has been announcing end-of-support dates for older versions. E9 is effectively end-of-life. E10 support is being phased out as Epicor pushes customers to Kinetic.
Australian localisation gaps. Epicor is a US-headquartered product. Australian features (BAS reporting, STP, multi-currency with AUD specifics, local tax handling) are often delivered through add-ons or partner-built solutions rather than core functionality. These add-ons have their own version compatibility issues.
Thick client dependency. Older Epicor versions use a Windows thick client. Kinetic offers a web client (browser-based), but the transition from thick to web client changes the user experience significantly.
Upgrade and migration paths
Upgrade to Kinetic (on-premises). Move to the latest Kinetic version while keeping your on-premises infrastructure. This preserves your data and most configuration but requires customisation re-engineering and user retraining on the web client.
Upgrade to Kinetic (cloud). Move to Epicor's cloud-hosted Kinetic. Adds cloud benefits (managed infrastructure, automatic updates) but introduces customisation restrictions. Not all on-premises customisations work in the cloud version.
Staged upgrade. If you're on E9, you may need to upgrade to E10 first, then to Kinetic. Direct jumps from very old versions can be technically challenging.
Alternative platform. If the Epicor upgrade cost is excessive or the platform no longer fits your business, evaluate alternatives. Common alternatives for Epicor manufacturing users include SAP Business One, Dynamics 365, and SYSPRO.
Customisation & integration challenges
BPM and BAQ customisations. Business Process Management (BPM) rules and Business Activity Queries (BAQs) are Epicor's supported customisation tools. These generally upgrade more cleanly than direct code modifications, but still need testing against the target version.
Customisation (screen/form changes). Screen-level customisations in older versions used C# code-behind. In Kinetic, the customisation model has shifted to a more declarative approach. Complex C# customisations need rewriting.
Integration approaches. Epicor supports REST APIs (in Kinetic), SOAP web services (in E10), and direct database connections (not recommended). Common integration needs:
- EDI: Trading partner data exchange for manufacturing and distribution
- Shipping/logistics: Integration with freight and warehouse systems
- Accounting: Connections to external accounting or tax systems
- MES (Manufacturing Execution Systems): Shop floor data collection
- E-commerce: Online ordering and catalogue management
Reporting. Epicor uses SSRS for standard reporting. Custom SSRS reports need testing against the upgraded database schema. Many businesses also use Crystal Reports or BI tools — these need connection updates.
Risks and decision points
Key risks
- C# customisation volume
Heavy C# code-behind means expensive rewriting for Kinetic.
- Cloud restrictions
Cloud Kinetic limits some customisation options. Test your requirements against cloud capabilities.
- Australian localisation
Verify that BAS, STP, and local compliance add-ons are compatible with the target version.
- User adoption
The web client is very different from the thick client. Plan retraining.
- EDI and supply chain integrations
Manufacturing integrations are complex and high-stakes. Test thoroughly.
How HELLO PEOPLE can help
- Customisation audit: Review all BPMs, BAQs, and C# customisations with upgrade risk ratings
- Integration modernisation: Replace SOAP and direct database integrations with REST APIs
- Custom application development: Build customer portals, dashboards, and mobile apps that connect to Epicor
- Data migration: Handle data extraction, transformation, and validation for version upgrades
- Reporting modernisation: Move from SSRS/Crystal Reports to Power BI or custom dashboards
Frequently asked questions
Which Epicor product am I running?
Epicor has multiple products. The most common in Australia are Epicor Kinetic (formerly Epicor ERP/E10/E9), Epicor Prophet 21 (distribution), and Epicor Eclipse (electrical/plumbing distribution). The upgrade path depends on which product you're on.
What is Epicor Kinetic?
Kinetic is the current name for Epicor's manufacturing ERP (previously called Epicor ERP, E10, E9, and Vantage before that). It includes a modern web client, cloud hosting options, and a current feature set. If you're on E9 or E10, Kinetic is your upgrade target.
Can we stay on Epicor E10 forever?
No. Epicor has announced end-of-support timelines for older versions. E10 support is being phased out in favour of Kinetic. The longer you wait, the bigger the version gap and the more expensive the upgrade becomes.
How long does an Epicor Kinetic upgrade take?
Typically 4-9 months depending on your current version, customisation volume, and data complexity. E10 to Kinetic is more straightforward than E9 to Kinetic. Cloud migration adds additional planning requirements.
Does Epicor work well for Australian businesses?
Epicor does well for manufacturing and distribution but doesn't have the same depth of Australian-specific features as locally developed ERPs. BAS, STP, and local compliance often need add-ons or customisations. Consider this when evaluating upgrade or migration options.
Key takeaways
- Epicor Kinetic is the target — E9/E10 support is being phased out
- Customisations built with Epicor's BPM and BAQ tools generally upgrade better than deep code mods
- The cloud version of Kinetic limits some customisation options — test before committing
- Australian localisation (BAS, STP) often relies on add-ons that need separate upgrade testing
- Plan for user retraining — Kinetic's web interface is different from the classic thick client