Epicor’s shift to cloud-first delivery for Kinetic ERP creates both opportunities and significant challenges for organizations still running on-premises or older versions. With the Classic (Smart Client) UI retiring in May 2026 (Kinetic 2026.1), on-premises feature development ending in 2028.1, and active support concluding December 31, 2029, companies must modernize or face limited Sustaining Support. This guide provides a one-stop, step-by-step roadmap for migrating to Kinetic Cloud (SaaS or Public Cloud), addressing deprecating satellite/bolt-on tools, custom code, and downstream integrations. Drawing from official Epicor resources, independent analyses, and real user experiences on epiusers.help, it outlines the logical order of activities, why each step matters, real-world examples of pitfalls and successes, and practical tools/documentation. The goal is to help mid-sized manufacturers and distributors minimize disruption, control costs, and prepare for a sustainable cloud future.
Table of Contents
- Introduction
- The Modernization Landscape and Critical Timelines
- Stage 1: Pre-Migration Assessment and Planning (3–6 months recommended)
- Stage 2: Data Preparation, Cleansing, and Migration
- Stage 3: Modernizing Customizations and Custom Tools
- Stage 4: Handling Satellite/Bolt-on Tools and Deprecations
- Stage 5: Rebuilding and Testing Integrations and Downstream Systems
- Stage 6: Environment Setup, Training, and Change Management
- Stage 7: Go-Live, Hypercare, and Post-Migration Optimization
- Common Risks, Costs, and Decision Framework
- Conclusion and Recommendations
References
1. Introduction
Epicor Kinetic is evolving into a cloud-native platform. Innovation now lives primarily in the cloud, with on-premises customers facing hard deadlines. Migrating is not just a technical lift-and-shift; it requires rethinking custom code, third-party tools, data strategies, and operations. For heavily customized environments—common in manufacturing—this can feel overwhelming, but a structured approach turns it into a manageable, value-creating project. This document walks through the full process in the exact order most successful migrations follow, with clear “why” explanations and real-world cases drawn from 2024–2026 user reports and partner guidance.
2. The Modernization Landscape and Critical Timelines
Epicor’s roadmap is clear and accelerating:
- May 2026 (Kinetic 2026.1 release): Classic Smart Client UI is fully retired. Only the browser-based Kinetic UI remains. All Classic customizations, forms, and logic must be rebuilt or replaced.
- January 2028 (tentative 2028.1): Final on-premises feature release. No new capabilities after this.
- December 31, 2029: End of Active Support for on-premises. Security patches and critical fixes stop.
- January 1, 2030 onward: Sustaining Support only—limited, lower-priority help with no new features or non-critical fixes.
Why these dates matter: Delaying past 2026 forces rushed UI rebuilds during go-live. Staying on-premises past 2029 increases security and obsolescence risks while Epicor support and partner expertise shift to cloud. Cloud migration (via Ascend program) gives access to continuous innovation, including AI, without manual upgrades.
Real-world example: A mid-sized manufacturer on E10 on-prem (single IT person) delayed assessment until late 2025 and now faces simultaneous Classic-to-Kinetic UI conversion and Linux container changes in 2026—doubling testing effort (epiusers.help thread, 2025).
3. Stage 1: Pre-Migration Assessment and Planning (Start 12–24 Months Before Target Go-Live)
Why first? You cannot fix what you do not know. A thorough inventory prevents surprise costs and scope creep.
Steps and tools:
- Inventory every customization: BPMs, C# scripts, UD tables/fields, BAQs, dashboards, SSRS reports, configurators, and server-side assemblies (use Epicor’s Compatibility Report and Application Studio readiness tools).
- Map all integrations and satellite tools: EDI, BarTender, QuickShip, DocStar/ECM, MES scanners, freight carriers, HR/payroll, e-commerce, Salesforce, etc.
- Assess data volume, quality, and compliance needs (Archon Analyzer or Epicor DMT).
- Calculate 10-year TCO using Elevatiq framework (includes 47%+ first-year subscription increase, 3–5% annual escalations).
- Engage Epicor Professional Services for an Ascend readiness assessment (AI-powered customization scan).
- Form a cross-functional team (IT, operations, finance) and define success metrics.
Real-world example: One company discovered 200+ undocumented BPMs and 15 bolt-ons only during testing—adding three months and $150k (Elevatiq case patterns, 2026). Another minimized customizations early, cutting migration cost by 40% (epiusers.help success story, March 2025).
Documentation: Epicor Cloud Migrations page; Elevatiq “Epicor Cloud Migration Decision Framework” (2026).
4. Stage 2: Data Preparation, Cleansing, and Migration
Why now? Clean data is the foundation; migrating junk bloats the new system and hurts performance.
Steps:
- Classify data: active/current vs. historical (archive 5–20+ years of transactions).
- Clean and validate: remove duplicates, fix UOM/GL mismatches, reconcile relationships (use Archon ETL or Epicor Data Migration Tool).
- Archive historical data in a searchable, compliant repository (Archon Data Store recommended).
- Migrate only active records to Kinetic Cloud via DMT or Epicor Professional Services.
Real-world example: A firm migrating 20+ years of financials and attachments to Kinetic saw MRP runtimes drop from 9+ hours to minutes after archiving history (Archon case, 2026). Another left old system online for a month post-cutover to catch missed UD fields (epiusers.help, 2025).
Documentation: Archon “Epicor Data Migration” blog; Epicor PTW Data Migration Tool page.
5. Stage 3: Modernizing Customizations and Custom Tools
Why before integrations? Custom logic often underpins integrations.
Steps:
- Rebuild Classic custom forms/screens in Application Studio (low-code visual tools).
- Move business logic to server-side: Epicor Functions, UBAQs, BPM directives.
- Convert configurators: Classic → CPQ; Inspection → Application Studio grids.
- Update SSRS reports (path-length bugs, permissions); prepare for Bold Reports transition (expected 2027 overlap).
- Test deprecated methods and field changes (e.g., removed custID in JobHead).
Real-world example: A user with complex labeling customizations (built over days to bypass BarTender FTP issues) realized Studio cannot fully replicate without Functions—requiring extra C# work before the 2026 deadline (epiusers.help Classic sunset thread, 2024–2025). Early adopters using Application Studio reported 50% faster development times (Progressive Technology Limited case).
6. Stage 4: Handling Satellite/Bolt-on Tools and Deprecations
Why parallel with customizations? Many bolt-ons depend on file shares or Classic components.
Key deprecations and fixes (2025–2026):
- BarTender labels: Azure File Share “permission denied” on Linux containers; repoint to FTP or use ServerFolder.FileShare override.
- EDI (EDIHQ/EDA, TPCx): Document mapping rework; migrate to native Epicor EDI by Dec 2026.
- Epicor Handheld → Kinetic Warehouse (EKW) full migration.
- SSRS → Bold Reports (RDL compatibility high; coexistence planned).
- QuickShip, Smart/IP&O, DocStar: Test “hiccups” during upgrade passes; some need vendor updates.
Real-world example: Linux container rollout (Pilot Jan/Feb 2026, Prod Mar/Apr) broke BarTender and EDI for many; Epicor added path-handling methods that were later deprecated—causing weeks of troubleshooting (epiusers.help “Linux Container Chaos” thread, Feb 2026). One company fixed bolt-ons in Pass 3 go-live weekend with quick vendor patches (epiusers.help opinions thread).
7. Stage 5: Rebuilding and Testing Integrations and Downstream Systems
Why after customs? Custom endpoints often feed integrations.
Steps:
- Shift from direct DB access to REST/ODBC read-only + whitelisting.
- Update API calls (v1 deprecations, field changes).
- Test file I/O, middleware, and external systems (Salesforce, freight, GL exports).
- Validate RODB/hybrid reporting performance.
Real-world example: DMT uploads failed to trigger downstream Salesforce pricing recipes until BPMs were rebuilt (common 2025 cloud issue). EDI middleware broke on “/” in part numbers after Linux path changes (epiusers.help API thread, Feb 2026).
8. Stage 6: Environment Setup, Training, and Change Management
Steps:
- Provision Pilot, Test, and Prod environments in Kinetic Cloud.
- Use Epicor Learning Center + role-based workshops.
- Run parallel testing for high-impact processes (MRP, order entry).
- Manage user expectations around browser UI and forced upgrades (2x/year in SaaS).
Real-world example: Companies that started Kinetic UI training in 2025 reported smoother go-lives; one with 70 users globally saw 20% productivity gain post-cloud (epiusers.help, 2025).
9. Stage 7: Go-Live, Hypercare, and Post-Migration Optimization
Steps:
- Phased cutover with rollback plan.
- 30–90 days hypercare with Epicor support.
- Monitor performance, tune, and adopt new cloud features (AI, MRP improvements).
Real-world example: Sterling Supply (Prophet 21 cloud) scaled without added headcount; Enjet Aero set up a new company in two days with full data sharing (Epicor customer stories, 2024–2025).
10. Common Risks, Costs, and Decision Framework
Costs (Elevatiq 10-year TCO for 100 users): Cloud migration $2.2M–$3.5M (custom conversion often $50k–$300k); staying on-prem cheaper short-term but risks obsolescence.
Risks: Under-testing customs/integrations, poor data quality, Linux surprises, sole-IT overload.
Framework (Elevatiq): Assess current state → TCO → strategic fit → due diligence. Consider alternatives only if Epicor gaps are severe.
Mitigation: Use Ascend program, independent advisors, and thorough testing.
11. Conclusion and Recommendations
Modernizing to Epicor Kinetic Cloud is a journey, not an event. Following the stages in order—starting with assessment—minimizes surprises and maximizes ROI. Begin now: inventory everything, engage Epicor Ascend, and archive history early. Organizations that treat this as strategic transformation (not just migration) report scalability, real-time data, and innovation gains that outweigh initial pain. For vanilla or lightly customized setups the path is smoother; heavy custom users should budget extra time and expertise.
Act before the 2026.1 deadline to avoid forced, costly rushes. This guide equips you with everything needed to succeed.
References (all accessed February 2026)
- Epicor.com: Cloud Migrations, Ascend Program, On-Premises Final Releases (Jan 6, 2026).
- Elevatiq.com: “Epicor Cloud Migration Decision Framework” and “On-Premise Sunset” (Jan 2026).
- Archondatastore.com: “Epicor Data Migration” blog.
- Epicforcetech.com: Cloud Migration Support journey stages.
- epiusers.help: Threads on Kinetic Cloud experiences (Mar 2025), Classic Sunset (Nov 2024–2026), Linux Container Chaos (Feb 2026), SSRS/Bold (2025–2026), Opinions on Cloud (Oct 2025).
- Mayantechs.com: “Epicor’s Migration to Kinetic UI” (Sep 2025).