# Epicor Upgrade Services: Moving From 10.2 to Kinetic Without Surprises > Source: https://netray.co/erp-help/epicor-upgrade-services-10-2-to-kinetic-parallel > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer An Epicor 10.2 to Kinetic upgrade is normally done into a new environment: you copy your production database, run the upgrade there, test, and cut over, while 10.2 stays live. Running both in parallel is routine. The work that costs time is customizations, BPMs, reports and integrations, not the database step. Use Epicor or a partner for the upgrade if you have heavy customization; a vanilla system can be done in-house. ## Kind how-to ## System epicor ## Erp Epicor Kinetic ## Module Upgrade / Deployment ## Query epicor upgrade services ## Alternate Queries - upgrade services epicor - epicor 10.2 and kinetic run parallel - epicor 1099 conversion us kinetic upgrade - epicor kinetic client installer ## Applies To Epicor ERP 10.2.x moving to a current Kinetic release, on-prem or private cloud. Cloud tenants are upgraded by Epicor on their own schedule. ## Steps ### A safe upgrade sequence **Items:** - Inventory what you have: customizations, BPMs, Epicor Functions, BAQs, SSRS and Crystal reports, EDI, integrations and Dashboards. Note which are in use. - Read the current release notes and the upgrade guide for your source and target versions. Confirm your 10.2 build is on a supported upgrade path and apply the required interim version first if not. - Build the new server environment (application, database and web tiers) next to production. Do not upgrade in place. - Restore a copy of the production database to the new environment and run the upgrade there. Time the run so you can plan the cutover window. - Test by role: quote to cash, procure to pay, job entry to shipping, month-end close and the US 1099 forms if you file them. Compare outputs with 10.2 for the same data. - Rebuild or convert customizations and BPMs that do not work, then deploy clients (browser or Windows) to a pilot group. - Cut over: freeze 10.2, take a final backup, repeat the upgrade run with a final copy, validate, and repoint users. - Keep 10.2 read-only for a defined period so people can compare history. ## Sections ### Running 10.2 and Kinetic in parallel **Body:** Because you upgrade a copy, the original production database never changes. That gives you a genuine parallel run: users keep working in 10.2 while a test group validates Kinetic against a snapshot. Parallel does not mean two live systems for the same transactions. Pick a cutover date. Data entered in 10.2 after your snapshot is not in the Kinetic copy unless you repeat the upgrade with a fresh backup, which is exactly what the final cutover run does. Use the practice upgrades to measure duration, find failing data conversions and train people. Most projects do at least two or three trial runs before the real one. ### 1099 and other compliance checks **Body:** For US companies, treat 1099 reporting as an explicit test case. Epicor has changed the 1099 forms and boxes over several releases, so verify vendor 1099 setup, the AP payment types that feed 1099 amounts and the year-end form output against the release notes for your target version. Run the 1099 report on the converted data and compare totals to the same period in 10.2. A difference is almost always a vendor flag or payment-type mapping, not lost data. Apply the same discipline to tax, intrastat or e-invoicing features you use. Anything with a legal filing deserves its own test script. ### Client installer and deployment **Body:** Kinetic is primarily a browser application, so most users need no installation. The Windows client, where you still use it, is deployed from the server client folder or packaged installer; plan how you will push it with your normal desktop tooling. Decide early which users stay on the Windows client (some customizations, certain tools) and which move to the browser, because customizations behave differently between the two. Application Studio layers are the Kinetic way to rebuild UI changes. Test the client against your proxy, SSO and certificate setup. Many go-live problems are infrastructure, not Epicor. ### DIY or partner **Body:** A lightly customized system with an experienced Epicor admin can be upgraded in-house, given enough trial runs. The risk grows with the number of customizations, integrations and bespoke reports. Epicor and its partners offer upgrade services that handle the database upgrade, customization conversion and testing. Ask for fixed scope, the number of trial runs included, and who owns the customization rewrite. Typical project length ranges from a few weeks for simple systems to several months for heavily modified ones. ## Pitfalls - Upgrading production in place; there is no fast rollback. - Discovering customizations at go-live because no one inventoried them. - Testing with a stale database copy so recent master data is missing. - Skipping 1099 or other year-end forms until the filing season. - Assuming the Windows client customizations carry over to the browser unchanged. ## Ai Angle Before an upgrade, a grounded assistant can list which customizations, BPMs and BAQs touch a given table and flag the ones likely to break, using your exported metadata. Netray runs that analysis on your own hardware so source code and schema never leave your network. ## Faq ### Can Epicor 10.2 and Kinetic run in parallel? **Answer:** Yes, as separate environments. You upgrade a copy of the 10.2 database to Kinetic and test while 10.2 remains live. You do not share one live database between them; you cut over on a chosen date. ### Do I need Epicor upgrade services or can I do it myself? **Answer:** Either can work. Simple systems with experienced admins are often upgraded in-house. Heavy customization, many integrations or limited admin time usually justify Epicor or partner services for the conversion and testing. ### How long does a 10.2 to Kinetic upgrade take? **Answer:** The database upgrade run itself may take hours. The project, including testing and customization conversion, typically runs from a few weeks to several months depending on complexity. ### Do I need to install a client for Kinetic? **Answer:** Not for the browser experience. If you keep the Windows client, deploy it from the packaged installer or client folder using your usual desktop software distribution. ## Search terms epicor upgrade services, epicor 10.2 to kinetic upgrade, epicor kinetic upgrade parallel, epicor 1099 conversion, epicor kinetic client installer, epicor client installer, upgrade epicor 10 to kinetic, epicor upgrade cost --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json