A practical guide to identifying risky BPMs, inefficient queries, and outdated integrations.
Epicor upgrades should be straightforward: new features, better performance, stronger security, and cleaner user experience. But for many manufacturers, upgrades turn into multi‑week fire drills, not because Epicor is unstable, but because customizations built years ago quietly break the moment the system moves forward.
If your organization has been on Epicor for more than one upgrade cycle, chances are you are carrying technical debt in the form of old BPMs, inefficient BAQs, outdated integrations, or UI customizations that no longer align with modern Epicor architecture.
This article breaks down the most common Epicor customizations that fail during upgrades, why they fail, and how manufacturers can proactively identify and fix them before they impact production.
- BPMs That Rely on Deprecated Fields or Methods
Business Process Management (BPM) directives are powerful, but they are also one of the biggest sources of upgrade pain.
Why they break
- Epicor removes or renames fields in new versions
- Methods change or consolidate
- Hard‑coded logic references outdated tables
- Custom code blocks rely on legacy DLLs
Symptoms
- Screens fail to load
- Transactions error out
- Custom workflows stop mid‑process
- Users see cryptic “method not found” messages
High‑risk BPM types
- Method directives with custom C#
- Data directives tied to legacy tables
- BPMs created before Kinetic’s modern UI
How to prevent issues
Audit BPMs annually and flag any that:
- Reference deprecated fields
- Include custom code
- Modify core Epicor logic
- Were built before your last major upgrade
- Inefficient BAQs That Collapse Under Modern Performance Standards
BAQs are often created quickly to solve a reporting need — but over time, they become bloated, inefficient, or dependent on outdated table relationships.
Why they break
- Epicor changes table structures
- Joins become invalid
- Subqueries slow down dramatically
- BAQs reference custom fields that no longer exist
Symptoms
- Reports time out
- Dashboards fail to load
- Users complain about slow screens
- SQL server performance drops after upgrade
High‑risk BAQs
- BAQs with more than 10 joins
- BAQs using subqueries instead of CTEs
- BAQs built for legacy Crystal Reports
- BAQs feeding dashboards with real‑time refresh
How to prevent issues
- Review BAQs for unnecessary joins
- Replace subqueries with modern techniques
- Validate BAQs against Epicor’s current schema
- Archive unused BAQs to reduce clutter
- Customizations Built on Classic Screens (Now Deprecated)
Epicor’s move to Kinetic means classic screens are disappearing — and any customization tied to them is at risk.
Why they break
- Classic forms are removed or replaced
- UI customizations do not migrate cleanly
- Event handlers tied to old controls fail
- Kinetic requires new customization patterns
Symptoms
- Custom screens disappear after upgrade
- Buttons, fields, or scripts stop working
- Users lose access to custom workflows
- Kinetic forms behave differently than expected
High‑risk customizations
- Classic UI scripts
- Custom forms built before Kinetic
- Personalizations tied to old controls
- Screens modified with embedded code
How to prevent issues
- Convert classic customizations to Kinetic now
- Rebuild UI logic using Kinetic’s low‑code tools
- Document all custom screens before upgrading
- Integrations Using Outdated APIs or Direct SQL Calls
Integrations are essential but older ones often bypass Epicor’s modern API layer.
Why they break
- Direct SQL calls no longer match Epicor’s schema
- Legacy REST endpoints are deprecated
- Custom middleware cannot manage new authentication
- Hard‑coded credentials fail after security updates
Symptoms
- Data stops syncing
- EDI or eCommerce orders fail
- MES or shop‑floor systems lose connectivity
- Scheduled tasks silently stop running
High‑risk integrations
- Direct SQL writes
- Legacy REST v1 endpoints
- Custom .NET apps built years ago
- Integrations without logging or error handling
How to prevent issues
- Move integrations to Epicor REST v2
- Replace SQL writes with business objects
- Modernize authentication
- Add monitoring and logging
- Custom Reports That Depend on Legacy Data Models
Reports built years ago often rely on data structures that have changed.
Why they break
- Fields are renamed or removed
- BAQs feeding reports become invalid
- SSRS or Crystal templates reference outdated datasets
Symptoms
- Reports fail to render
- Data appears incomplete or incorrect
- Formatting breaks
- Users receive blank PDFs
High‑risk reports
- Crystal Reports (legacy)
- Reports using custom BAQs
- Reports tied to deprecated tables
How to prevent issues
- Migrate Crystal to SSRS
- Validate BAQs before upgrading
- Rebuild reports using modern datasets
- Hard‑Coded Logic That Does Not Adapt to New Epicor Behavior
Any customization with hard‑coded values is a ticking time bomb.
Examples
- Hard‑coded part classes
- Hard‑coded GL accounts
- Hard‑coded user IDs
- Hard‑coded plant or warehouse codes
Why they break
Epicor upgrades often introduce:
- New fields
- New validation rules
- New workflows
- New required data
Hard‑coded logic does not adapt, it simply fails.
How Manufacturers Can Get Ahead of Upgrade‑Breaking Customizations
- Perform a customization inventory
Document BPMs, BAQs, dashboards, reports, UI customizations, and integrations.
- Score each customization by risk level
High‑risk = custom code, deprecated fields, classic screens, SQL writes.
- Modernize before upgrading
Convert classic screens, rewrite old BPMs, optimize BAQs, update integrations.
- Test customizations in a sandbox
Validate everything in a non‑production environment.
- Build a long‑term customization strategy
Reduce technical debt and move toward standard Epicor functionality where possible.
How 2W Tech Can Help
2W Tech helps manufacturers upgrade Epicor without the headaches caused by legacy customizations. Our team audits your BPMs, BAQs, dashboards, reports, and integrations to identify high‑risk items before they break. We modernize outdated logic, rebuild classic customizations for Kinetic, optimize performance, and ensure your entire Epicor environment is ready for a smooth upgrade. With 2W Tech as your partner, you move forward confidently without unexpected downtime, broken workflows, or production delays.
Read More: