Epicor Kinetic Go-Live Readiness Checklist (Free)

0%

0 of 28 items complete

11 critical items still open - these are the highest-risk gaps.

Download checklist:

Data readiness

Part master, BOM and routing data loaded and reconciled to legacy countsCRITICALOpen sales orders, POs and jobs loaded with quantities reconciledCRITICALOn-hand inventory counted and loaded by warehouse and binCRITICALCustomer and supplier masters de-duplicated and approvedOpening balances for GL, AR and AP agreed with financeCRITICALMock conversions run at least twice with timings recorded

Configuration and security

Company, plant, warehouse and calendar setup signed offSecurity groups tested with real user roles, not only adminCRITICALMenu, dashboard and report access reviewed per roleNumbering sequences and defaults confirmedCustomizations and BPMs reviewed, tested and documentedCRITICALPrinting, labels and document formats tested on real printers

Integrations

All interfaces listed with owner, frequency and test evidenceCRITICALEDI partners tested for orders, advance ship notices and invoicesBanking and payment file formats testedShop floor data collection devices tested on the production networkFallback process agreed if an interface fails on day one

People and training

Every role trained and signed off using real transactionsCRITICALSuper users named for each department and each shiftQuick reference guides available at workstationsDress rehearsal of the order to cash and procure to pay flows completedCRITICALMonth-end close rehearsed in the test environment

Cutover and support

Cutover plan with hour by hour tasks, owners and dependenciesCRITICALBackup and rollback plan agreed, with a decision deadlineCRITICALLegacy system set to read-only after final extractHypercare roster, issue log and escalation path publishedGo/no-go criteria agreed in writing before cutover weekendFirst week and first month-end support plans scheduled

Do not go live with open critical items. Anything critical that is not ticked is a go/no-go discussion for the steering group.

Go-live readiness review

Optional: share your completed checklist and we will comment on the gaps we see.

Optional. The tool and every export work without this. No spam.

How to use the checklist

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

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.

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

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.

Frequently Asked Questions

How long before go-live should we start this checklist?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

Epicor

More Epicor tools

See all

Epicor Kinetic Go-Live Readiness Checklist for Manufacturers