NetSuite Post-Go-Live Support

NetSuite's support handles platform bugs and questions about standard functionality. We handle the customization layer: scripts, workflows, saved searches, templates, and configuration specific to your account. Most day-to-day questions in a live account sit in the customization layer, not the platform itself.

SuitePacific offers three engagement models: dedicated monthly support (a fixed block of hours applied to whatever comes up each month), on-demand access for occasional requests without a monthly commitment, and project-based engagements for defined builds with an agreed scope. Accounts with a steady stream of development and configuration needs typically choose dedicated monthly support; it provides consistent access without the overhead of scoping each individual request.

We typically start with a three-month engagement, which gives enough time to understand the account and address the highest-priority items. Most clients continue month-to-month after that.

Yes. We handle transitions regularly. The process involves a documented handoff of active customizations, known issues, and in-progress work. We also review the account independently rather than relying solely on the previous provider's documentation.

Yes. Most live accounts need both. Administration covers configuration changes inside NetSuite's built-in tools. Development covers SuiteScript, integrations, and automation that requires custom code. Both are handled within the same engagement.

A monthly engagement provides a dedicated block of hours applied to whatever comes up during the month: new development requests, bug fixes, configuration changes, saved search updates, administration tasks, and integration maintenance. Work is brought as it arises; we handle it within the allocated hours. Most accounts find a consistent level of work month to month, with occasional spikes during NetSuite release cycles or business process changes.

Urgent issues get prioritized ahead of queued development work. Because we maintain context on your account, there is no ramp-up time diagnosing the problem. We have access to your existing scripts, workflows, and configuration history, which is typically where urgent issues originate.

Yes. We work with both SuiteScript 1.0 and SuiteScript 2.x accounts. Legacy 1.0 scripts have different APIs and governance behavior than 2.x. We document which scripts are on 1.0 and assess whether migration to 2.x is warranted as part of ongoing maintenance, rather than recommending a wholesale migration that creates unnecessary disruption.

Yes. Custom records, custom fields, custom forms, and saved searches built on custom records are a standard part of post-go-live administration and development. We create, modify, and maintain these as part of the ongoing engagement.

Before each release, we review the release preview in your Sandbox environment and check for compatibility issues with your existing customizations. Most customizations survive releases without changes, but SuiteFlow and advanced PDF templates occasionally require adjustments. We flag issues proactively so they are addressed before the release reaches your Production account.

Yes. We work alongside internal IT and administrators regularly. The typical arrangement has internal IT managing infrastructure and general IT policy while we handle NetSuite-specific development, customization, and configuration. We adapt the scope of our engagement to avoid overlap with existing internal capabilities.

All customizations built during the engagement belong to your NetSuite account. We do not use proprietary tooling, platform wrappers, or external services that would make the work inaccessible after the engagement ends. We maintain documentation of active scripts and workflows, which we provide during offboarding.

Hypercare is the period immediately after go-live, typically the first 30-90 days, when issues surface at the highest rate. Data entry errors, integration failures, and configuration gaps that testing did not catch all appear under real transaction volumes. A post-go-live support partner stabilizes this period by diagnosing and resolving issues as they arise rather than letting them accumulate into a backlog while the internal team tries to keep up with day-to-day operations.

Break-fix support is on-demand: you engage a consultant when something breaks, pay per incident or per hour, and the relationship ends when the issue is resolved. Managed support is a retainer covering whatever comes up each month, including proactive work and new development. Break-fix accumulates context overhead on every call because the consultant starts from scratch each time. Managed support builds institutional knowledge, so each request takes less time than the last. For accounts with a steady stream of ongoing needs, managed support is typically more cost-effective once re-onboarding time is factored into each break-fix engagement.

Most accounts maintain an ongoing support engagement indefinitely. NetSuite accounts continue to evolve: business processes change, integrations require maintenance, new capabilities need development, and twice-yearly NetSuite releases require regression testing in Sandbox. Accounts that end a support engagement typically restart within 6-12 months when accumulated needs become urgent. The relevant question for most accounts is not how long support lasts but how many hours per month the account actually generates.

A full-time NetSuite administrator covers configuration, administration, and basic saved searches but typically does not cover SuiteScript development, integration work, or complex automation. Accounts needing both development and administration would require a developer-level hire, which carries the full overhead of a full-time employee: salary, benefits, paid time off, and ramp-up time. A retainer covering both development and administration provides access to a broader skill set without fixed headcount cost, which is generally more cost-effective for mid-market accounts that need both capabilities but not at full-time volume for either.

We perform an independent account review during onboarding, reading existing scripts, workflows, and configuration ourselves rather than relying on documentation from the previous provider. Overlapping the transition by starting an engagement with us while the existing contract winds down is the cleanest approach: it avoids a coverage gap and gives us time to learn the account before the handoff is complete. All customizations built by a previous provider remain in your NetSuite account. We do not use proprietary tooling or wrappers that would make prior work inaccessible.

SuitePacific post-go-live support is priced as a fixed monthly retainer with three tiers: Care at $799 per month covering 10 hours, Care Plus at $1,499 per month covering 20 hours, and Care Pro at $2,499 per month covering 35 hours. All plans require a 3-month minimum, then continue month-to-month. Hours cover SuiteScript development, workflow automation, saved searches and dashboards, Advanced PDF templates, troubleshooting, and technical guidance. There is no Statement of Work required per request within the retainer scope. The effective hourly rate at Care Plus and Care Pro is $75 to $80 per hour, which compares favorably to large partner firms that bill $150 to $300 per hour and add re-onboarding overhead on each engagement.

NetSuite Advanced Customer Support (ACS) is Oracle's own premium support offering, priced as a percentage of your annual license fee. ACS covers configuration guidance, standard feature questions, and bug escalation to Oracle Engineering. It does not cover SuiteScript customization, third-party integrations, custom workflow logic, or account-specific design decisions. A third-party support partner covers exactly the areas ACS does not: the customization layer that is specific to your account. Most live accounts that need both platform guidance and ongoing customization work use Oracle support or ACS alongside a third-party partner, not one or the other.

Most new engagements are active within one to two weeks of the initial conversation. The first step is an intake call to understand the account scope and priority issues. We then request Administrator access and spend the first week reading existing scripts, workflows, and integrations before making any changes. The first development work typically begins in week two. If there are urgent production issues, those are triaged immediately during onboarding and do not wait for a full account review to complete.

Oracle offers several NetSuite certifications. The most relevant for a post-go-live support engagement are SuiteCloud Developer II (covers SuiteScript 2.x, advanced scripting, and API integration) and Administrator Professional (covers account configuration, roles, workflows, and ongoing administration). SuiteCloud Developer II is the most technically demanding NetSuite certification and is not widely held. SuitePacific holds both. When evaluating a support partner, ask specifically whether the individual assigned to your account holds these certifications, not just the firm. Certifications at the firm level without the assigned developer holding them provide no practical assurance.

Yes. SuitePacific Care at $799 per month is structured for SMBs that need a responsive technical resource without the cost of a full-time hire or an enterprise consulting retainer. The comparison point is not a full-time NetSuite developer (which would cost $80,000 to $130,000 per year plus benefits) but an on-demand break-fix consultant billing $150 to $300 per hour with re-onboarding overhead on every engagement. For accounts that generate four or more hours of ongoing work per month, a fixed retainer at $799 is typically more cost-effective than break-fix at any comparable rate once per-request overhead is factored in.