# Epicor Kinetic Go-Live Readiness Checklist for Manufacturers > Source: https://netray.co/tools/epicor-kinetic-go-live-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A cutover checklist for a new Epicor Kinetic implementation or major re-implementation, grouped by data, security, integrations, people and support. ## Category epicor ## Erp Epicor Kinetic ## Industry Discrete Manufacturing ## Audience - Project manager - Epicor admin - Operations manager ## Tool **Kind:** checklist **Scoring Note:** Do not go live with open critical items. Anything critical that is not ticked is a go/no-go discussion for the steering group. **Groups:** #### Data readiness **Items:** **Text:** Part master, BOM and routing data loaded and reconciled to legacy counts **Critical:** true **Text:** Open sales orders, POs and jobs loaded with quantities reconciled **Critical:** true **Text:** On-hand inventory counted and loaded by warehouse and bin **Critical:** true Customer and supplier masters de-duplicated and approved **Text:** Opening balances for GL, AR and AP agreed with finance **Critical:** true Mock conversions run at least twice with timings recorded #### Configuration and security **Items:** Company, plant, warehouse and calendar setup signed off **Text:** Security groups tested with real user roles, not only admin **Critical:** true Menu, dashboard and report access reviewed per role Numbering sequences and defaults confirmed **Text:** Customizations and BPMs reviewed, tested and documented **Critical:** true Printing, labels and document formats tested on real printers #### Integrations **Items:** **Text:** All interfaces listed with owner, frequency and test evidence **Critical:** true EDI partners tested for orders, advance ship notices and invoices Banking and payment file formats tested Shop floor data collection devices tested on the production network Fallback process agreed if an interface fails on day one #### People and training **Items:** **Text:** Every role trained and signed off using real transactions **Critical:** true Super users named for each department and each shift Quick reference guides available at workstations **Text:** Dress rehearsal of the order to cash and procure to pay flows completed **Critical:** true Month-end close rehearsed in the test environment #### Cutover and support **Items:** **Text:** Cutover plan with hour by hour tasks, owners and dependencies **Critical:** true **Text:** Backup and rollback plan agreed, with a decision deadline **Critical:** true Legacy system set to read-only after final extract Hypercare roster, issue log and escalation path published Go/no-go criteria agreed in writing before cutover weekend First week and first month-end support plans scheduled ## Content **Intro:** Most failed go-lives are not caused by software but by gaps in data, security, interfaces or training that were visible weeks earlier. This checklist captures the points that matter for an Epicor Kinetic cutover in a discrete manufacturer. **Sections:** #### How to use the checklist **Body:** Assign each group to an owner and review the list weekly in the final eight weeks. Critical items are the ones where an open gap will stop shipping, invoicing or payroll feeds. Hold a formal go/no-go meeting with the checklist as the agenda. If a critical item is open, either fix it or document the workaround and the person who accepted the risk. Export the checklist to keep a record of what was decided. #### Data and rehearsal come first **Body:** Data issues cause the majority of day-one problems: wrong on-hand quantities, BOMs that do not match routings, and open orders with wrong dates. At least two mock conversions with reconciliations make the third, real one routine. Rehearse complete flows, from sales order through job, receipt, shipment and invoice, with the people who will perform them, not just consultants. **Bullets:** - Reconcile counts and values, not only record counts - Time every conversion step to plan the cutover window - Rehearse month-end before it happens live #### Common mistakes **Body:** Teams underestimate interface testing on the real network, skip role-based security testing, and leave printing and labels until the last week. Another common mistake is no clear decision owner for rollback. Agree beforehand who can call a no-go, and by what hour, because the options shrink quickly once the legacy system is switched off. **Cta:** Netray can help with a read-only reconciliation layer between legacy and Epicor during cutover, so teams can ask for counts and values from both systems without writing queries. **Faq:** #### How long before go-live should we start this checklist? **Answer:** Start about three months before the planned date and review weekly in the last eight weeks. Data conversion and training usually take the longest, so they need the earliest start. #### How many mock conversions are enough? **Answer:** Two full mock conversions are a practical minimum, with reconciliation each time. A third is wise if the second showed large differences. Each should be timed so the real cutover window is realistic. #### Who owns the go/no-go decision? **Answer:** A steering group with a named executive sponsor, usually operations or finance leadership, owns it. The project manager presents the checklist, but the sponsor decides and records the reasoning. #### Does this apply to an upgrade, not a new implementation? **Answer:** Many items apply, especially customizations, security, interfaces and training. Data conversion items matter less. Use the group structure and drop the items that do not apply to your upgrade scope. ## Search terms epicor go live checklist, epicor implementation checklist, epicor cutover plan, epicor kinetic go-live, erp go live readiness, epicor project checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json