Source connector

NetSuite connector

NetSuite integration for databases, warehouses and BI tools

Cloud ERP for finance, inventory, and operations. Datrise captures NetSuite entities such as transactions, customers, items, subsidiaries, and GL activity, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The NetSuite SuiteTalk REST Web Services (record/v1) + SuiteQL, with SuiteAnalytics Connect for bulk SQL access authenticates with OAuth 2.0, API key, incremental runs key on lastModifiedDate (queryable via SuiteQL).

Of the 5 objects, 3 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `netsuite_transactions`) with a schema derived from the NetSuite API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the NetSuite pipeline page, and join the waitlist to get the NetSuite connector (ERP) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What NetSuite data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
transactions	netsuite_transactions	Append-only, incremental by timestamp
customers	netsuite_customers	Upsert by primary key, incremental on updated-at
items	netsuite_items	Upsert by primary key, incremental on updated-at
subsidiaries	netsuite_subsidiaries	Upsert by primary key, incremental on updated-at
GL activity	netsuite_gl_activity	Append-only, incremental by timestamp

NetSuite API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	NetSuite SuiteTalk REST Web Services (record/v1) + SuiteQL, with SuiteAnalytics Connect for bulk SQL access
Authentication	OAuth 2.0, API key — OAuth 2.0 (Authorization Code or Client Credentials/machine-to-machine) is Oracle's recommended method; Token-Based Authentication (a non-expiring consumer/token key-secret pair) still works but new TBA integrations are blocked starting with the 2027.1 release.
Pagination	offset — Collection endpoints use limit (default 1000, range 1-1000) and offset, where offset must be evenly divisible by limit; the response includes count, totalResults, and hasMore.
Rate limit	Not published
Incremental cursor	lastModifiedDate (queryable via SuiteQL) — lastModifiedDate reflects any field-level change including system-triggered ones, so it can over-fire relative to pure business edits, and SuiteQL result sets cap at 100,000 rows per query.
Webhooks	Not published
Bulk export	Yes — SuiteAnalytics Connect (read-only SQL over ODBC/JDBC/ADO.NET)
Deletes detectable	Yes — The SOAP getDeleted operation returns deleted records by type/date, but is scheduled for removal alongside SOAP by the 2028.2 release, so REST/SuiteQL-only connectors often must diff ID sets instead

Official API reference

What bites when replicating NetSuite

REST collection endpoints require offset to be exactly divisible by limit (offset=20&limit=10 is valid, offset=3&limit=2 errors), so an off-by-one cursor hard-fails rather than truncating silently.
SuiteQL caps result sets at 100,000 rows per query (up to 1,000,000 only via the separately licensed SuiteAnalytics Connect), so large full-refresh pulls must be chunked by date or ID range.
Token-Based Authentication is being sunset: Oracle has stated new TBA integrations cannot be created starting with the 2027.1 release, with full SOAP/TBA removal targeted for the 2028.2 release.
REST/SuiteQL result sets are not cached server-side, so concurrent writes during an offset-paginated scan can skip or duplicate rows; use ID-keyset pagination (WHERE id > lastId ORDER BY id) instead of offset for actively-changing tables.

Compare this against every other documented API

Popular destinations for NetSuite

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

NetSuite connector FAQ

What NetSuite data does the connector extract?: 5 objects: transactions, customers, items, subsidiaries and GL activity. Each lands in its own table with types preserved; history-style objects (2: transactions and GL activity) load as append-only streams.
Is the NetSuite integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load NetSuite data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each NetSuite → destination pair has its own page with the object-to-table mapping.

Related ERP sources

Other sources in the same category, each with its own connector page.

Early access

Launch your NetSuite pipeline with guided onboarding

Join the waitlist to get priority access for NetSuite integrations with guided setup, schema-aware mapping, and production-grade incremental sync.