Skip to content

Entry 05 of 28· 4 min read

A support handover checklist for teams moving beyond ERP implementation

A practical checklist for the move from ERP implementation to support.

Explore NetSuite support
a bunch of keys sitting on top of a wooden table
Handover is a moment. Support is everything after it.Photograph: Filip Szalbot

¶01 Why the handover is where ERP projects quietly go wrong

An ERP support handover should preserve the decisions, workarounds and business context the implementation team holds. Otherwise the support desk inherits a system it did not design, and the client has to explain their business again.

Scheduled saved searches are a concrete handover check. Oracle documents a condition where a scheduled email stops after a change of owner if the new owner has never scheduled a saved search. Record the search, its owner and audience, then check the next scheduled delivery with the incoming team. See Oracle’s saved-search ownership guidance.

Before the project team moves on, agree the support owner, escalation route and written record of what remains unresolved.

¶02 The ERP go-live to support handover checklist

Walk this checklist through with the implementation team and incoming support owner. Confirm named-user access, credential ownership and secure recovery arrangements alongside the project context.

  1. Open issues and known limitations: a current list of unresolved bugs, deferred requirements and accepted workarounds, with who agreed each one and why. The support team should never discover a 'known issue' from an angry user.

  2. Customisations and configuration decisions: what was built beyond standard, what it does, and the reasoning behind it. For NetSuite, that means SuiteScript, workflows, saved searches, custom records and any scripted automations, plus the sandbox-to-production process used to deploy them.

  3. Integrations and data flows: every connected system, the direction data moves, the schedule, the credentials owner and what happens when a sync fails. Note the failure points the project team already worried about.

  4. User roles, permissions and access: who has what, why, and who signs off changes. Confirm the client's own admin access and that the implementation team's elevated access is reviewed or removed. This is not housekeeping: the NCSC's guidance is to review accounts for unnecessary privileges regularly and revoke privileged access when it is no longer required, and a go-live is exactly such a moment.

  5. Documentation and runbooks: configuration notes, key processes, month-end steps and a plain-language description of how the client actually uses the system day to day, not just how it was specced.

  6. Outstanding training and adoption gaps: which roles are confident, which are still shaky, and any sessions promised but not yet delivered.

  7. Named contacts on both sides: who the client calls, who owns escalation internally, and the route from routine ticket to senior consultant when something serious breaks.

  8. Support scope and SLAs in writing: what is covered, what is chargeable change work, response and resolution expectations, and how out-of-scope requests are quoted.

  9. Environment and licence housekeeping: production and sandbox details, refresh cadence, renewal dates, and who is responsible for upgrades and release testing.

¶03 Transfer context, not just credentials

Run a joint session with the lead consultant, incoming support owner and client. Walk the system live, including deferred requirements, fragile mappings and tolerated workarounds. Let the client ask questions while the people who built it are available.

Give the client a written outcome: what works, what remains fragile, who owns each outstanding action and who to call.

Use the session to explain decisions that a configuration list will miss. Why was a requirement deferred? What must happen before a workaround can be removed? Which integration mapping should be reviewed before a process changes? Assign an owner to each answer rather than leaving the incoming support team to infer it.

Check that the client can actually reach the runbooks and recovery arrangements. A document held only by the departing project team is not a usable handover.

¶04 The post-go-live silence is a commercial problem

After an intensive implementation, a move straight into a ticket queue can feel abrupt. A clear handover and escalation route help the client understand how the consultancy will support them after go-live.

If nothing fills that space, the client's experience of you becomes the support queue, and the support queue is rarely where relationships deepen.

That experience matters to later optimisation, renewal and referral conversations. It is worth planning alongside the technical transition.

¶05 Make the handover a standard step, not a scramble

Capture decisions during the project. Keep the checklist current, name the owners and schedule the joint session before the implementation team leaves. This avoids reconstructing the project in its final week.

Include report definitions and ownership and the integration decisions. For communicating this expertise between projects, see the NetSuite partner marketing guide.

Basis for this piece

Five years inside a NetSuite consultancy, watching implementations from the marketing side of the same business. It is experience rather than a survey, and the access-control recommendation is linked to NCSC guidance.

Asked and answered

Your questions.

What should an ERP support handover include?

Cover open issues, customisations, integrations, access, runbooks, training gaps, named contacts, written support scope and SLAs, and environment and licence details. Confirm named-user access, credential ownership and secure recovery arrangements alongside project context.

When should the handover from implementation to support happen?

Capture material throughout the project. Hold a joint session around go-live while the implementation team remains available, with the client and incoming support owner present.

Why do clients feel abandoned after ERP go-live?

The move from a named project team to a support queue can lose context. A written handover, named support owner and escalation route help the client understand who is responsible.

Next steps

Find more practical ERP guidance.