NetSuite Support Partner Onboarding Checklist

This checklist covers what you need to provide, what the support partner should do, and how to verify the onboarding is complete.

---

Part 1: Access setup (Week 1)

NetSuite account access

• Create an Administrator-level employee record for the support partner's primary contact
• Assign the Administrator role
• Confirm the partner has logged in and can access all areas of the account (scripts, workflows, saved searches, roles, integrations)
• Verify they can access the Sandbox environment if one is available

Note on Administrator access: Some teams are uncomfortable granting full Administrator access to external partners. If this applies to your situation, discuss the minimum access level needed. The support partner will need at minimum: access to Customization (scripts, workflows, saved searches, custom fields), Setup (roles, users, integrations), and Reports. Restricted access slows onboarding and limits the partner's ability to diagnose issues efficiently.

Integration platform access (if applicable)

• Provide read access to any middleware platforms (Celigo, Boomi, custom REST infrastructure) the partner will need to maintain
• Share integration documentation or API credentials stored internally
• Confirm the partner can view integration sync logs and error queues

Communication channel

• Agree on the primary communication channel for day-to-day requests (email, Slack, or project management tool)
• Establish how urgent issues are escalated (phone, direct message, emergency email)
• Add the support partner to any existing NetSuite-related Slack channels or project boards where relevant context lives

---

Part 2: Context handoff (Week 1-2)

The support partner needs context that is not visible in the account itself: the history of decisions, known issues, and active work in progress.

Document what you know

• Provide any existing account documentation: script inventories, integration specs, process guides
• Share the open issue list: known bugs, deferred items, intermittent problems
• Note any in-progress work: scripts in Sandbox that have not yet been deployed to Production, pending configuration changes
• List upcoming projects or requests already scoped but not started
• Identify the internal stakeholders the partner will interact with (who owns which process areas)

Transition handoff from the previous partner (if applicable)

If switching from an existing support engagement:

• Request the previous partner's account documentation and issue list before their access is removed
• Schedule an overlap period where both the previous partner and the new partner have account access (2-4 weeks is typical)
• Ask the previous partner to answer specific technical questions the new partner has after their initial account review
• Note any open Sandbox work in progress and decide whether to deploy or hand off

---

Part 3: What the support partner should deliver in Week 1-2

This is what a competent support partner does during initial onboarding. Use this list to verify the engagement is on track.

• Confirms their access is functional and they can read scripts, workflows, and integration records
• Reads existing script deployments and notes what each does and any concerns
• Reviews active workflows and notes entry conditions, states, and any findings
• Checks integration health: recent sync logs, error rates
• Reviews roles and confirms access structure makes sense
• Asks specific, informed questions about your account (not generic "how does your account work" questions)
• Provides an initial finding summary: here is what we noticed in the first week, here is what we think needs attention

If the partner does not produce this: Follow up. A partner who spends the first two weeks waiting for your documentation rather than reading the account is starting slowly.

---

Part 4: Establishing the working relationship (Week 2-3)

• Agree on the request process: how do you submit a new request? What information do you include? What response time should you expect?
• Agree on communication for active work: how will the partner communicate when work begins, when it is in Sandbox for review, and when it is ready for Production deployment?
• Clarify the Production deployment process: does the partner deploy directly, or do they stage in Sandbox and you or your administrator deploys?
• Agree on how urgent issues are handled outside of normal business hours if that matters for your account
• Confirm the invoicing and hours tracking process: how do you know how hours are being used?

---

Part 5: End-of-month-one review

At the end of the first 30 days, do a brief structured review:

• What high-priority issues were identified and addressed?
• What is the current open issue list?
• What is in Sandbox for testing or pending deployment?
• What upcoming items are on the radar (upcoming release, known projects)?
• How is the communication working? Is the request process efficient?
• Is the partner able to give informed estimates and pushback when a request will interact unexpectedly with existing customizations?

---

Signs onboarding is going well

• The partner asks specific questions about your account that show they have read it carefully
• They can describe what is running in your account without you having to explain it
• The first issues addressed are the right priorities, not just the easiest items
• Communication is direct and responsive
• You do not feel like you are re-explaining context on every interaction

Signs onboarding is not going well

• The partner is waiting for your documentation rather than reading the account
• Early recommendations are generic (not specific to your account configuration)
• Response times are slow without explanation
• You feel like you are managing the partner more than the partner is managing the work
• The partner cannot answer specific questions about your account after two weeks

---

Related resources

• NetSuite post-go-live support: what an ongoing support engagement covers
• How to evaluate a NetSuite post-go-live support partner: questions to ask before signing
• NetSuite partner replacement: the full transition process when switching from one support arrangement to another
• NetSuite post-go-live support: what to expect in year one: month-by-month expectations for the first year