Questions to Ask Before Switching NetSuite Partners
Need help applying this in your account?
Evaluating a NetSuite support partner is different from evaluating an implementation partner. An implementation partner needs to demonstrate project management capability, industry experience, and the ability to configure NetSuite from scratch. An ongoing support partner needs to demonstrate something different: the ability to inherit an existing account, retain context across requests over months and years, and handle small work without the overhead of a project-delivery model.
Quick answer
Evaluating a NetSuite ongoing support partner requires different questions than evaluating an implementation partner. An ongoing support partner needs to demonstrate the ability to inherit an existing account, retain context across requests over months and years, and handle small work efficiently without project-delivery overhead. The most important questions to ask: How do they document and retain account knowledge across the engagement? What happens to account context if the consultant who works on your account leaves their firm? How do they onboard a new account when the previous partner left no documentation? How do they handle requests that come in without a defined scope? How do they stay current on NetSuite releases and proactively notify clients of relevant changes? Ask for a reference from a client who switched to them from a previous partner, since that scenario reveals how well they handle account inheritance under real conditions.
Most evaluation processes ask the wrong questions. These are the right ones.
About their support model
How do you handle routine requests without a statement of work?
A partner built for ongoing support should have a clear answer: routine requests are handled within the active monthly engagement without a formal scoping process. A partner who responds that most requests require a proposal or SOW is operating a project model, not a support model. The overhead of per-request scoping is exactly what makes large consulting firms expensive for ongoing work.
What is included in your monthly retainer versus what triggers additional billing?
Understand the scope boundary explicitly. Some firms include development work in the retainer; others include only administration and bill development separately at a higher rate. Some bill for every communication; others treat short questions as included. The scope boundary should be clear before you sign, not discovered after the first invoice.
How do you prioritize work when multiple requests arrive at the same time?
The answer reveals whether the partner has a genuine triage process or handles work on a first-come-first-served basis. A partner doing ongoing support for multiple clients needs a clear way to distinguish urgent from standard requests. If the answer is vague, urgent issues will compete with routine work in a queue with no differentiation.
What happens when monthly hours run out mid-month?
Understand the overage process: is additional work billed at an agreed overage rate, does it roll to the next month's allocation, or does work stop until the next billing cycle? A support partner without a clear overage policy creates uncertainty at the worst possible moment, which is when the account has a higher-than-usual volume of work.
About account knowledge and continuity
How do you document and retain account knowledge across the engagement?
This is the most important question on the list. The value of an ongoing support partner increases over time as they accumulate context on the account. A partner who does not document that context is effectively starting from scratch on each request, which drives up time and cost for every engagement.
The answer should describe a specific practice: account documentation maintained across all active scripts and workflows, notes on why specific customizations were built a certain way, records of known issues and how they were resolved. A vague answer ("we maintain good notes") is not sufficient.
What happens to account context if the person working on my account leaves your firm?
Staff turnover is a reality at every consulting firm. The question is whether institutional knowledge survives turnover. If the answer is that account documentation would allow a new team member to pick up where the previous one left off, that is a genuine answer. If the answer depends entirely on the continuity of a specific individual, the risk of a personnel change is higher than it appears.
How do you onboard a new account when the previous partner has not left thorough documentation?
A strong ongoing-support partner does not rely on the previous partner's documentation. They read the account directly: reviewing script source code, workflow configurations, saved searches, and integration records independently. The answer to this question reveals whether the firm can function when handed an undocumented account, which is the common case.
About technical credentials and capability
What NetSuite certifications does the developer who will work on my account hold?
Oracle NetSuite's SuiteCloud Developer II certification covers advanced SuiteScript development including Map/Reduce, RESTlet, Suitelet, and SuiteScript 2.x APIs. The Administrator Professional certification covers configuration, administration, and account management. Both are verifiable through Oracle and represent a meaningful capability floor. Ask specifically about the developer who will handle the account, not the firm's certifications in general.
Have you worked with SuiteScript 1.0 accounts, or only SuiteScript 2.x?
Many live accounts still run some SuiteScript 1.0 scripts built during earlier implementations. The APIs are different, governance behavior differs from 2.x, and migration decisions require understanding both. A partner who only works with 2.x will either refuse to touch 1.0 scripts or touch them without sufficient understanding of how they behave.
How do you handle NetSuite's twice-yearly release cycle?
The answer should include reviewing release notes for compatibility with existing customizations, testing in a Sandbox environment before the release reaches Production, and proactively flagging anything that requires attention. A partner who answers reactively (addressing release-related issues after they surface in Production) is not providing release management; they are providing break-fix for release-caused breaks.
About the working relationship
Who will be my primary contact and how do I reach them directly?
In larger firms, the primary contact is often an account manager who relays requests to a development team. In boutique firms, the primary contact is typically the developer doing the work. Both models can function, but the relay model adds a communication lag that affects every interaction. Understand the model before committing.
What is your typical response time for standard requests versus urgent issues?
Get a specific answer, not a general commitment to responsiveness. A partner who distinguishes between response time for an urgent production issue (same day) and a standard development request (within the week) has a defined service level. A partner who says "we respond quickly" has not defined anything.
Do you require a minimum contract commitment?
Month-to-month is the standard model for boutique NetSuite support partners. A requirement for a 12-month or multi-year commitment before the relationship has been established is a retention mechanism, not a service requirement. A three-month initial engagement to allow both parties to assess the fit is reasonable; anything longer warrants scrutiny.
What the answers reveal
A partner built for ongoing support will have precise answers to the questions about their model, clear documentation practices, and a working relationship structure that gives you direct access to the developer. They will describe a proactive approach to release management and a triage process for urgent versus standard requests.
A project-delivery firm will have vaguer answers about ongoing support processes, will likely describe a scoping process for most requests, and will frame the relationship around deliverables rather than a continuous engagement.
The distinction matters because the wrong model does not just produce a worse experience; it produces the same structural mismatch that likely caused the previous partner relationship to break down.
Related resources
- NetSuite partner replacement: full overview of what the transition looks like
- NetSuite partner transition checklist: structured checklist for the handoff process
- How to switch NetSuite partners without losing momentum: the right sequence for a low-disruption transition
- NetSuite Care pricing: monthly support plans from a boutique partner built for ongoing work
Related Resources
NetSuite Support Partner Evaluation Checklist
A structured checklist for evaluating NetSuite post-go-live support partners. Covers who does the work, certifications, billing model, response time, release handling, and red flags to walk away from.
NetSuite Account Access Handoff Guide
What access and credentials need to transfer when switching NetSuite partners: administrator roles, integration credentials, third-party tools, and what to verify before removing the previous partner's access.
Need help applying this in your account?
We work with post-go-live NetSuite accounts every day. Tell us what you're working on.