Can you change your NetSuite partner?
Yes, you can change your NetSuite partner at any time, subject to the notice period in your services contract: your account, data, configuration and custom developments stay where they are. Only the support team changes and, if requested, the Partner of Record registered with Oracle.
What changes and what stays the same
| Stays in your account | Changes |
|---|---|
| Data, history and documents | The team managing the account |
| Configuration, roles and workflows | The services contract |
| SuiteScript scripts and custom developments | The partner's users and access |
| Integrations and installed SuiteApps | The Partner of Record, if applicable |
| Licences and Oracle subscription | Support channels and agreements |
There are two qualifications: SuiteApps owned by the outgoing partner and integration credentials managed by that partner. Both are covered in the handover checklist.
What is the difference between the Partner of Record and the support partner?
The Partner of Record is the partner Oracle associates with your account; the support partner resolves issues and develops customisations. They can be the same organisation or different ones, and you can change them together or separately.
Your NetSuite subscription and your services agreement are separate contracts
The subscription, covering licences, modules and basic support, is contracted with Oracle NetSuite or through a reseller partner. Implementation, support and development services are contracted with the partner. You can therefore end the services agreement under its terms without changing the subscription, even midway through its term.
What the Partner of Record is and how to change it with your Oracle NetSuite Account Manager
Oracle's records identify the Partner of Record as the partner responsible for your account, typically because it sold or implemented NetSuite. Oracle assigns it; you cannot change it from within your account. Contact your Oracle NetSuite Account Manager for the procedure. The change does not alter your account, data or installed SuiteApps.
What the support or consulting partner does and why you can change it immediately
The support partner maintains the account day to day. This is a contractual relationship between your company and that partner, independent of Oracle. Once the agreement ends, you can give another team access through NetSuite outsourcing or managed services.
When to change both and when to change only one
| Situation | What to change |
|---|---|
| Support is the issue; the Oracle relationship works well | Only the support partner |
| You want one contact for licences, renewals and support | Both |
| The Partner of Record is no longer active | Both |
| You are in the middle of a licence renewal | Support first; discuss the Partner of Record with Oracle |
What signs suggest you need to change your NetSuite partner?
The main sign is that NetSuite stops evolving with your business and incidents take longer to resolve than operations can tolerate. Common situations include:
- Response times falling short of agreed commitments, especially for issues blocking invoicing or closing.
- A lack of proactive release updates or improvement proposals.
- Team turnover: each new consultant asks again how your account works.
- Limited knowledge of your industry or Spanish requirements such as SII, AEAT returns or Verifactu.
- Unpredictable billing: hours that cannot be linked to deliverables.
- Undocumented developments: scripts and workflows understood only by their original author.
How to change your NetSuite partner step by step
To change your NetSuite partner without interrupting operations, review the contract, inventory the account, select the new partner, arrange an overlap and close the outgoing partner's access.
- Review the current contract. Check notice periods, ownership of developments and source code, and the services included until the exit date.
- Inventory your account. List scripts, workflows, integrations, SuiteApps, partner users and AI connections through the NetSuite AI Connector Service.
- Choose the new partner. It should be able to take over a live account like yours; see how to choose a NetSuite partner for the selection criteria.
- Notify Oracle through your Account Manager if the Partner of Record will also change.
- Plan an overlap and knowledge transfer. A few weeks with both partners active allow joint reviews of open tickets, developments and critical integrations. The duration depends on the account's size and how well it is documented.
- Carry out an incoming account audit with the new partner to confirm the inventory and identify risks before it takes over support.
- Close the outgoing partner's access by following the handover security steps.
Handover checklist: data, integrations, SuiteApps and access
The data does not move during the handover. What you must secure is the knowledge, credentials and components that depend on the outgoing partner.
| Item | What happens when you change | What to secure |
|---|---|---|
| Developments and scripts | Stay in the account and keep running | Code ownership, repository access and documentation |
| Integrations and API credentials | Keep working unless changed | The user and token used by each integration |
| Third-party SuiteApps | Remain installed | Who pays the licence and holds the supplier relationship |
| Partner-owned SuiteApps | May depend on its licence or maintenance | Continued-use terms or a replacement plan |
| Documentation | Often lives outside NetSuite | Formal delivery before the contract ends |
| Sandbox | Remains available | Work in progress and items not yet deployed to production |
| Open tickets | Need a new owner | A list with status and ownership during the overlap |
If the integration landscape is complex, review it with a NetSuite integrations team before rotating credentials.
Security: how to remove the outgoing partner's access
Removing the outgoing partner means closing every access path, not just its user account. Removing a role is not enough: integrations may still connect using their own tokens.
- Disable its users when the overlap ends.
- Revoke TBA tokens under Setup > Users/Roles > Access Tokens.
- Revoke authorised OAuth 2.0 applications under Setup > Users/Roles > OAuth 2.0 Authorized Applications.
- Rotate the integration credentials known to the partner: client keys, certificates and technical-user passwords.
- Review AI Connector Service connections. If the partner connected an assistant such as ChatGPT or Claude, that connection is another OAuth 2.0 application and must be revoked or reassigned.
- Review system notes since notice was given. A system notes search filtered by partner users shows their subsequent changes; the Login Audit Trail shows their access.
Minimum documentation to request from the outgoing partner
- An inventory of scripts, workflows and custom fields, with their purpose.
- An integration map: systems, direction, frequency, user and authentication method.
- Source code and repository access where you own the developments.
- A SuiteApp list with versions and licence holders.
- Tax configuration and Spanish localisation settings.
- Open tickets and known issues.
Changing partner in Spain: tax localisation, SII and Verifactu
In Spain, the largest handover risk is tax compliance: if localisation, digital certificates or SII submissions depend on the outgoing partner, a poorly managed transition can delay filings with the AEAT.
If Spanish localisation is a SuiteApp owned by the outgoing partner
Some accounts use a partner-developed localisation rather than Oracle's. Check whether its use depends on a licence or maintenance agreement ending with the relationship. The alternative is the official Spain Localization SuiteApp, which generates VAT and SII reports and submits them to the AEAT. It requires NetSuite OneWorld with SuiteTax, so moving to it is a project in its own right; see our Spanish tax localisation in NetSuite guide.
AEAT digital certificates and SII submissions: ownership and continuity
SII requires invoice records to be submitted within four working days, so submissions cannot simply pause. Before switching, confirm:
- Which digital certificate NetSuite uses, whose name it is in and when it expires.
- Whether submissions are automatic or manual, and who reviews AEAT responses and rejections.
- That the new partner has observed at least one complete submission and correction cycle during the overlap.
Verifactu and e-invoicing: what to review during an adaptation project
Businesses in SII are outside Verifactu's scope, but other businesses must adapt their billing systems. The enacted rule, Royal Decree-Law 15/2025, sets 1 January 2027 for corporate income taxpayers and 1 July 2027 for other taxpayers. On 5 October 2026, Spain's Finance Ministry announced a postponement to October 2028 to align the obligations with e-invoicing; as of this article, that change has not been published in the BOE.
If your Verifactu adaptation is underway, hand over what has been configured, what has been tested and who will complete it.
When is the best time to change your NetSuite partner?
The best time is midway through a quiet month, away from year-end closing, AEAT filings and NetSuite upgrades; December and January are the least suitable periods.
| Risk window | When | Why to avoid it |
|---|---|---|
| Month-end closing | First days of each month | Reconciliations, accruals and management reporting |
| Year-end closing | December and January | Adjustments, audit and annual returns |
| Monthly VAT, for SII businesses | Until the 30th of the following month | Reconciling Modelo 303 with SII submissions |
| Quarterly VAT, for other businesses | 1–20 April, July and October; 1–30 January | Modelo 303 and other quarterly returns |
| Corporate income tax | July, for calendar-year companies | Finalised and reviewed accounts |
| NetSuite upgrades | Twice yearly, phased over several months | Release Preview testing and script reviews |
NetSuite publishes two major releases per year and upgrades accounts in phases; your date appears in the dashboard's New Release portlet. AEAT dates above are general deadlines: check the taxpayer calendar for the applicable dates.
What should the new partner do in the first 90 days?
In the first 90 days, the new partner should understand the account, resolve inherited issues and propose improvements, in that order.
- Days 1–30: account audit. Review configuration, roles, scripts, integrations, SuiteApps and tax localisation, using a NetSuite implementation checklist to cover every area.
- Days 1–60: inherited tickets. Prioritise by impact and resolve issues affecting invoicing, SII and closing first.
- Days 30–90: documentation. Complete missing material and maintain an up-to-date account map.
- Day 90: a NetSuite optimisation plan. A prioritised improvement list with effort and impact.
A useful handover indicator is that, by day 90, your team knows who resolves each type of issue and within what timeframe.
Frequently asked questions
Can I change partner during implementation?
Yes, but the risk is greater than for a live account. Agree on the exact project status, which deliverables are complete and accepted, what remains outstanding and what has been paid. The new partner will review the design before continuing the NetSuite implementation, which often affects the go-live date.
Can I move to a partner if Oracle implemented NetSuite directly?
Yes. If Oracle Professional Services handled implementation, you can engage a partner for support without changing the subscription. It needs account access and implementation documentation. If you also want it to become Partner of Record, discuss that with your Account Manager.
What if my current partner has closed or does not respond?
First check that someone in your company has the Administrator role. If nobody does, contact NetSuite support or your Account Manager to recover access as the account holder. Then remove the outgoing partner's access and arrange an incoming audit, because there will be no knowledge transfer.
Does changing the Partner of Record change my licence price?
NetSuite pricing depends on your subscription agreement and renewal, not your support partner. Before signing a Partner of Record change, ask your Account Manager whether it affects renewal terms.
Can I operate without a partner and use Oracle support, such as ACS?
Yes. Advanced Customer Support is Oracle's advanced support offering, with four levels: Advise, Monitor, Optimize and Architect. See NetSuite ACS versus partner managed services for the differences.
How much does changing NetSuite partner cost?
It depends on the account's size and documentation. Typical items are the incoming account audit, overlapping services from both partners, missing documentation and, where necessary, replacement of the outgoing partner's own SuiteApps.
