Independent NetSuite consultancy · London, UK
NetSuite integration services: NetSuite at the centre of your stack.
Native SuiteScript, Celigo or Dell Boomi: I pick the right approach for each integration and build it to handle failure in ways finance can trust.
When you need this
You're adding e-commerce, CRM, procurement, payments, payroll or any system NetSuite needs to talk to, or an existing integration keeps failing.
What's included
- Native REST/SOAP integration in SuiteScript
- Celigo and Dell Boomi iPaaS implementations
- CRM: Salesforce, HubSpot, Lime, ServiceNow
- Ecommerce: Shopify+, Amazon, bespoke platforms
- Payments: Stripe, SEPA, EFT (HSBC, SVB, BoA)
- HR / expense: ADP, Concur, Expensify, WorkDay
- 3PL, EDI, WMS, OCR (Docupeak, Adobe)
- Tax & e-invoicing: SuiteTax, Avalara, regulatory portals
How I work
How a NetSuite integration project runs.
Step 1
Scope
Which records move, in which direction, how often, and which system is the master for each field.
Step 2
Design
Field mappings, error handling, retries and alerts designed up front, not bolted on after the first failure.
Step 3
Build
Native SuiteScript 2.1 (REST, RESTlets, Map/Reduce) or Celigo and Boomi, chosen integration by integration.
Step 4
Test and monitor
End-to-end testing with realistic volumes, plus monitoring so failures are seen and fixed the same day, not found at month-end.
Native SuiteScript or an iPaaS like Celigo?
My default for finance-critical integrations is native SuiteScript 2.1. It keeps everything inside NetSuite's own audit trail, avoids ongoing iPaaS licence costs, and gives full control over mapping and error handling.
An iPaaS earns its place when you have many systems to connect, pre-built connectors that genuinely fit, or a team that will maintain flows without a developer. I've built both: The Jockey Club's Coupa integration runs on Celigo, while Cape.io's Fortnox integration is native SuiteScript.
The trade-offs are covered in more depth in native SuiteScript vs iPaaS for NetSuite integrations.
Integration Rescue Sprint
One to two weeks, fixed price. Stabilise failing Celigo, Boomi or SuiteScript integrations, clear the backlog and add monitoring.
See what's included →Relevant experience
Related case studies.
The Jockey Club
Coupa to NetSuite source-to-pay on Celigo: 24 flows across nine group entities.
Read more →Cape.io
A native SuiteScript integration between NetSuite and Fortnox across eight OneWorld subsidiaries.
Read more →Pink Group: Salesforce
Salesforce and NetSuite kept in step, from opportunity to invoice.
Read more →iSAMS & Famly
Schools and nurseries connected to NetSuite OneWorld across 40 subsidiaries.
Read more →NetSuite × Agentic AI
A working pattern for connecting NetSuite to Claude through MCP.
Read more →Live demo: Integration Control Tower
See how integration failures can be monitored and retried from one screen.
Read more →FAQ
NetSuite Integration: common questions.
Which systems have you integrated with NetSuite?
Salesforce, HubSpot, Shopify Plus, Coupa, Stripe, Fortnox, Lime CRM, Concur, ADP, Avalara, Kyriba, BlackLine, EazyStock, iSAMS, Famly, hotel PMS systems such as Opera, and banks for payments and reconciliation, among others.
Can you fix an integration that keeps failing?
Yes. The Integration Rescue Sprint is designed for that: find the root causes, clear the backlog and add monitoring so it stays fixed.
Real-time or scheduled?
Whichever the process needs. Orders and payments often need near real-time updates; many finance flows are better as scheduled batches with clear reconciliation.
Do Oracle's authentication changes affect our integrations?
Possibly. Integrations using token-based authentication or SOAP web services are affected by changes Oracle has announced for 2027.1 and 2028.2. See what's changing and when.
Related reading
Ready to find your NetSuite hero?
Book a free 30-minute call. I'll listen to what you're trying to do and tell you honestly what the right path is, even if it's not with me.