How to Migrate from Epicor 10 to Kinetic: Full Checklist
Epicor 10 to Kinetic Migration: Prerequisites, Seven Phases and Cutover Checklist

Moving off Epicor 10 is one of the bigger projects a finance and IT team will run this decade. It touches every screen your users know, every customization built up over the years, and every integration that feeds the general ledger. Done well, it is a chance to clean up data and modernize how the business runs.
This guide is for CFOs, finance leaders, IT managers and Epicor administrators still running Epicor 10. It answers one question: how to migrate from Epicor 10 to Kinetic without disrupting operations or the month-end close. You will learn what changes, what to verify before you start, and a seven-phase checklist with an exit check for each stage. Because connected systems matter as much as the ERP, it builds on our guide to Epicor integration via REST API, Service Connect and EDI.
What Are Epicor 10 and Epicor Kinetic?
Epicor is an industry-specific ERP vendor that has served manufacturers, distributors and retailers for more than 50 years.
Epicor 10 is the earlier generation of its flagship ERP. Most companies run it on-premises, users work in the classic Windows Smart Client, and many businesses have extended it with screen customizations, BPMs, BAQs and custom reports.
Epicor Kinetic is the next generation of the same ERP. It keeps the core business logic and data, but moves users to a browser interface, replaces classic customization with Application Studio, and makes REST services the main way to integrate. It runs in the Epicor Cloud or, for now, on-premises.
Because Kinetic is the same product line, the upgrade converts your existing database and application rather than starting over. The hard parts are the edges: customizations, reports, integrations and the finance workflows that depend on them.
Why Migrate from Epicor 10 to Kinetic Now
Two Epicor decisions have made the move time-bound.
The classic Smart Client is being retired. Epicor's Smart Client retirement timeline makes 2025.2 the final release where the Smart Client is available, with browser forms replacing it from 2026.1. For an Epicor 10 company, that means a version upgrade and a new interface at once. Classic customizations and dashboards must be converted or rebuilt, and every user needs retraining.
On-premises releases have an end date. Epicor has made 2028.1 the final on-premises Kinetic feature release, with Sustaining Support from January 1, 2030, and all future innovation in the cloud.
Delay has real costs: older releases fall behind supported server software, custom code piles up, and the eventual upgrade gets bigger.
Epicor 10 vs. Kinetic: What Actually Changes
The biggest change is the interface and extension layer, not the data model.
Area | Epicor 10 | Kinetic | What it means for your migration |
User experience | Windows Smart Client | Browser forms, personal layouts and search | Role-based retraining for every user |
Screen customization | Classic customization layers | Application Studio | Convert, rebuild or retire each one |
Business logic | BPMs, BAQs, Epicor Functions | The same tools, extended | Most carry over; fix anything tied to changed fields |
Reports and dashboards | SSRS reports, classic dashboards | SSRS reports, dashboards built in Application Studio | Retest reports; rebuild dashboards |
Integrations | Service Connect, DMT, custom code | REST services alongside older methods | Check each integration against the target release |
Deployment | Mostly on-premises | Cloud, or on-premises until 2028.1 | Decide early; it shapes the whole project |
These are layers, not replacements: an older integration is not automatically broken, but it needs checking.
Before You Start: Epicor 10 to Kinetic Migration Prerequisites
Confirm these before committing to dates. Some apply to every migration; others depend on your target release or hosting model.
Prerequisite | What to verify | Applies to |
Release and upgrade path | Your exact Epicor 10 release, and whether Epicor's upgrade guide supports a direct move to the target | All migrations |
Servers and database | Windows Server and SQL Server versions supported by the target release | On-premises only |
Infrastructure and network | Server sizing, supported browsers, bandwidth and single sign-on | All; cloud depends more on connectivity |
Third-party applications | Vendor confirmation of support for the target release | All migrations |
Access, backups and test environment | Admin rights, a backup you have actually restored, and a production-sized test system | All migrations |
People and partners | Committed finance, IT and key-user time, and partner availability | All migrations |
The Seven Phases at a Glance
Assess your Epicor 10 environment and plan the upgrade.
Decide on the Kinetic deployment model.
Run the data migration checklist.
Migrate customizations and integrations from classic to Kinetic.
Validate finance and business workflows.
Test, train and cut over.
Stabilize and optimize after go-live.
Phase 1: Assess Your Epicor 10 Environment and Plan the Upgrade
Confirm release and support status. Record your exact release and build, because Epicor 10 end of support dates are release-specific.
Pick a target release. Check its Kinetic support lifecycle so you do not land on a release near the end of Active Support.
Map the environment. List servers, databases, printers, shop-floor devices and other network dependencies, and compare them with the target release's requirements.
Inventory customizations, integrations and scheduled jobs. Include screen customizations, BPMs, BAQs, reports, every connected system and overnight jobs such as MRP runs.
Estimate costs. Cover partner services, licensing or subscription, customization rebuilds, integration changes, data work, training and post-go-live support. Use Epicor Kinetic pricing and per-user costs as a licensing reference.
Choose a partner and owners. Work with Epicor or certified Epicor implementation partners, and name finance, IT and executive owners.
Exit check: a signed-off inventory, a confirmed upgrade path, an approved budget and named owners.
Phase 2: Decide on the Kinetic Deployment Model
The deployment choice shapes infrastructure, integrations and testing, so make it now rather than mid-project.
Model five-year cost both ways. Compare cloud subscription with on-premises licenses, hardware, maintenance and IT time.
Avoid a double migration. Going on-premises now means a second move before 2030 if cloud is your eventual destination.
Check cloud readiness. Identify reports and integrations that write directly to the database, since the cloud typically does not allow that, and confirm bandwidth and single sign-on for every site.
Review security and data residency with IT and compliance.
Plan for release cadence. Cloud customers take updates more often, so build a regression test you can rerun.
Exit check: an approved deployment model, with the infrastructure and integration changes it requires listed in the plan.
Phase 3: Epicor Kinetic ERP Data Migration Checklist
The upgrade transforms your Epicor 10 data rather than re-keying it, so the job is to prove it is still accurate and usable.
Clean master data. Merge duplicate suppliers and customers, close inactive records, and verify bank details and tax IDs.
Clear open items. Close stale POs, unreceived lines and unapplied cash so they do not migrate as noise.
Decide on history. Agree what stays live and what is archived, and confirm attachments still open.
Run trial upgrades on a copy. Log every error and fix, and rehearse at least twice.
Reconcile. Tie out the trial balance, AP and AR aging, open orders, inventory valuation and fixed assets to the cent.
Validate with users. Have key users run their everyday lookups and reports on the converted data.
Exit check: two clean rehearsals and signed reconciliations.
Phase 4: Epicor Classic to Kinetic Migration for Customizations and Integrations
From 2026.1, classic customizations must be converted to the browser before you can upgrade, so this is where most projects slip.
Convert, rebuild or retire. Retire customizations that standard Kinetic screens now cover. Epicor's training shows a conversion script moving classic customizations into Application Studio, but expect manual rework.
Review BPMs, BAQs and reports. Fix anything tied to changed fields, rebuild dashboards, and retest invoices, POs and checks against real documents.
Validate every connected system. Banking, tax, CRM, warehouse and e-commerce Epicor integrations each need vendor confirmation for the target release.
Replace fragile connections first. Direct database writes and integrations tied to classic screens break most often.
Test failures, not just successes. Confirm failed transactions are visible and can be fixed without duplicates.
Exit check: every customization has a final status, and every integration has passed testing in the target environment.
Phase 5: Validate Finance and Business Workflows
Every finance integration gets retested during an upgrade anyway, so this is the cheapest time to confirm that money still moves correctly.
Workflow | What to validate |
Procurement | Approvals, PO routing, receipts and the procure-to-pay chain of requisitions, receipts and AP invoices |
Accounts payable | Invoice capture, matching, tolerances, holds and GL coding |
Accruals and payments | Month-end accruals and reversals, payment runs, bank files and reconciliation |
Accounts receivable | Invoicing, cash application, credit holds and order-to-cash automation |
Financial close | Close steps, allocations, intercompany entries and reports |
AP deserves a closer look because its cost is easy to measure. Ardent Partners' 2025 benchmarks put the average cost to process an invoice at $9.40, versus $2.78 for best-in-class teams. Measure your touchless rate, cost per invoice and exceptions before cutover, ask each AP vendor how its connector handles Epicor upgrades, and compare how Epicor AP automation and Hyperbots differ for Kinetic.
Exit check: each workflow owner signs off test cases run on converted data.
Phase 6: Test, Train and Cut Over
Test in layers. Test each converted item, then full processes, then user acceptance by role with scripted scenarios and sign-off.
Parallel-run a close. Close the same period in both systems and compare the results.
Train by role, in the browser, on the test system with converted data.
Plan the cutover window. Freeze changes in advance, schedule downtime for a low-volume period, and agree manual fallbacks for shipping, receiving and urgent payments.
Prove recovery. Take a final backup and confirm it can be restored, and keep a rollback plan ready.
Decide go/no-go on written criteria. Balances reconcile, critical tests pass and integrations are confirmed. The executive sponsor decides at a fixed time, with the controller, IT lead and process owners signing off their areas.
Plan hypercare for the first two weeks.
Exit check: a documented go decision and the first live transactions confirmed in Kinetic.
Phase 7: Stabilize and Optimize After Go-Live
Validate financial reporting. Confirm the trial balance, financial statements, inventory valuation and AP and AR balances tie to cutover figures.
Monitor system health. Watch performance, and confirm scheduled jobs and integrations run on time.
Review security. Remove temporary project access and check user roles.
Act on user feedback. Use one channel for issues and turn recurring problems into fixes or training.
Capture lessons learned. Document what worked, and keep your test scripts so future upgrades take days, not weeks.
Exit check: two clean closes in Kinetic and an agreed improvement backlog.
Finance applications connected to Epicor run through every phase. The next section looks at keeping them running.
How Hyperbots Keeps Finance Automation Running Through an Epicor Upgrade: Persimmon Technology Case Study
A migration does not pause the business. Invoices keep arriving, accruals still need booking and suppliers still expect payment while the ERP is upgraded and cut over. Hyperbots adds an AI execution layer on top of Epicor ERP, which remains the system of record.
Pre-Built Epicor Connector
Hyperbots connects through a pre-built connector, one of many on its list of pre-built ERP connectors. Because the connection already exists, implementation is mostly configuration and testing, and it typically goes live in 6 to 8 weeks.
Works With Both Epicor 10 and Kinetic
As Dave Sackett, VP of Finance at Persimmon Technology, explains in a recorded interview on the Hyperbots Epicor integration, the connector uses whatever each version supports. Epicor 10 connects through Service Connect, Epicor's established integration tool. Kinetic connects through Epicor's REST APIs, including in the cloud. In both, it picks up your custom fields and business rules, so customizations keep working.
Keeps Finance Data Current in Both Systems
During the migration, Hyperbots can work in dual-write mode, posting each finance transaction it handles to both Epicor 10 and Kinetic until cutover. Both systems stay current, so nothing has to be re-entered after go-live. Every write is read back and checked. Failed posts retry automatically, then go to an exceptions queue with a Microsoft Teams alert, so nothing fails silently. Before go-live, the integration is proven with sample transactions and a 48-hour shadow run, as Sackett describes in a conversation on pre-built ERP connectors.
How Hyperbots Complements Epicor
Epicor manages the core finance transactions. Hyperbots adds AI to the work around them:
Workflow | Epicor's role | What Hyperbots adds |
Invoice processing | Records and posts AP invoices | Reads invoices in any layout and codes GL and tax |
Invoice matching | Matches invoices to POs and receipts by rule | Resolves small variances within tolerances you set |
Accruals | Holds POs, receipts and journals | Finds goods received but not invoiced and proposes entries |
Payment reconciliation | Runs payments and records clearing | Reconciles payments against bank statements |
Hyper Agents read invoices, POs, receipts and past postings, apply your tolerances, approval limits and coding patterns, and then act in Epicor. Anything outside your rules goes to people for review, accruals wait for controller approval, and every action is logged.
What Our Customer Using Epicor Say About Us
Persimmon Technology, a Wakefield, Massachusetts maker of vacuum robotics for semiconductor equipment, runs Epicor on-premises and uses Hyperbots across AP, accruals and payments. In the same interview, VP of Finance Dave Sackett describes the results.
On how the two systems fit together: "Epicor remains the system of record. Hyperbots sits on top and removes the manual keyboard work that slows down finance and supply chain teams."
On the work itself:
Invoices: the Invoice Processing Hyper Agent reads PDFs from the team's Outlook mailbox, matches them to the PO and receipt, and posts the invoice in Epicor, "about 80% straight through."
Accruals: the Accruals Hyper Agent "finds PO receipts without invoices, books month-end journal entries, and auto-reverses them once the invoice arrives."
Payments: the Payments Hyper Agent builds payment batches and reconciles them against bank statements.
On Epicor upgrades: "During an upgrade or ERP migration, we enable dual-write mode to post to both systems until cutover." When a post does fail, the team is alerted, "so nothing fails silently."
Persimmon's rollout took 3 to 5 weeks. As Sackett puts it: "The leap from OCR to AI agents is huge."
Making Your Epicor 10 Upgrade to Kinetic Pay Off
The success of an Epicor 10 to Kinetic migration is decided before go-live: by how well you confirm readiness, prove data integrity and protect the workflows that keep the business running. It is also a rare chance to modernize, because every finance workflow is retested anyway. Hyperbots adds AI-driven finance automation on top of Epicor that keeps running through the upgrade.
Planning your Epicor 10 to Kinetic migration? Request a personalized demo to see how Hyperbots keeps finance automation running through your move to Kinetic.
Frequently Asked Questions
How long does an Epicor 10 to Kinetic migration take?
A lightly customized single-site company can often finish in a few months; multi-site businesses with heavy customizations or a cloud move take longer. Your rehearsal timings are the best basis for a go-live date.
What does an Epicor 10 to Kinetic migration cost?
There is no standard price, because cost follows scope: partner services, licensing, customization rebuilds, integrations, data work, training and support. Customizations are usually the biggest variable, so get a partner estimate after the Phase 1 inventory is complete.
Will we keep our historical data?
Yes. The upgrade converts your existing database, so posted transactions and closed periods stay available. The main decision is how much to keep live versus archive.
How much downtime should we expect?
It depends on database size and your upgrade path, and rehearsals will tell you. Most teams cut over during a weekend or low-volume period with a transaction freeze beforehand.
Will our customizations, BPMs and reports carry over?
BPMs, BAQs and SSRS reports usually carry over, but anything tied to changed fields needs fixing and every report should be retested. Classic screen customizations and dashboards must be converted or rebuilt for the browser, and many can be retired because standard Kinetic screens now cover them.
Will our third-party integrations work with Kinetic?
Many will, but each one needs confirming with its vendor for your target release. Test every integration in the new environment, including failed transactions, before go-live. Integrations that write directly to the database or depend on classic screens need the most attention.
How should we test before go-live?
Test each converted item first, then full business processes, then user acceptance by role. Run a parallel month-end close and compare it with Epicor 10. Agree written go/no-go criteria in advance so the final decision rests on evidence, not deadline pressure.
What happens to our finance automation during the upgrade?
Tools tied to classic screens or direct database writes often need rework. Hyperbots works with both Epicor 10 and Kinetic and can write to both during the migration, so invoices, accruals and payments keep posting through cutover.
