Skip to main content

ERP adoption · Field guide

ERP go-live readiness checklist

A green systems test does not tell you whether people can run the business on day one. Use these checks to test the work, make gaps visible, and turn an SAP or Oracle go-live decision into a conversation about evidence.

The question that matters

Can each site or region do the critical work and recover when something goes wrong?

Six checks before you say go

Use this with an ERP sponsor, a process owner, and someone who supervises the work. Run it separately for each site or rollout wave. Check a box only when you can name the owner and show current evidence. No information is sent or stored by this checklist. You can print the page for your working session.

ERP go-live checks with current evidence
  1. Can each site complete its critical transactions and recover from a common exception?

    Evidence to ask for: A dated walkthrough from trigger to reconciliation. Include a real exception, its recovery path, and who owns the next step.

  2. Do frontline staff, supervisors, process owners, and support teams know who acts or approves when work stalls?

    Evidence to ask for: A role and access matrix tested with representative users, plus a named decision owner and backup for each critical exception.

  3. Can representative users do the work without a trainer leading them through it?

    Evidence to ask for: A role-based practice scenario in a safe environment, a recorded result, and a plan for anyone who still needs support.

  4. Which steps are standard everywhere, and where do local practices, languages, or constraints change the job?

    Evidence to ask for: A reviewed list of local variants, with a local owner, usable guidance, and an approved exception where the standard process does not fit.

  5. Does each team know what pauses, what continues, and who can stop the cutover if a critical operation cannot run?

    Evidence to ask for: A business cutover rehearsal, a documented fallback, and named authority for the go, hold, or stop decision.

  6. Can every shift report a problem, find a decision-maker, and tell when it is safe to return to normal support?

    Evidence to ask for: A staffed support roster, escalation and triage rules, daily issue reviews, and criteria for handing support back to operations.

Decide what happens to every open item

If a check is open, write down the site or wave, the business risk, the owner, and the next rehearsal date. If the team cannot complete or recover a critical workflow, bring that gap to the named go/no-go owner. Record any agreed workaround and who will monitor it. This worksheet informs the decision; it does not replace technical cutover criteria or authorize a go-live.

Released client evidence

Two ERP programs, two kinds of readiness

SAP · Plant readiness

Haworth

SDI helped Haworth connect an enterprise SAP program to how plants worked. The released case documents process and gap analysis, change tools for plant teams, implementation support, and hypercare.

Prove the future process on the floor, not just in a program plan.

Read the Haworth case study

Oracle · Global learning rollout

Amway

SDI established one accountable training team for Amway’s global Oracle learning rollout. The released case documents localized learning, regional delivery and trainer coaching, and a sandbox for practice before production.

Keep one owner for learning while making it usable in each region.

Read the Amway case study

These cases illustrate the documented readiness and learning work. They do not imply SDI owned technical configuration or migration, or promise the same result for another rollout.

Bring one go-live risk to the conversation.

Tell us which site or wave is next, what people must be able to do, and where you still need evidence. We will start with the work that is hardest to get right on day one.

Talk with SDI about ERP readiness