Connect NetSuite to Snowflake

NetSuite is the source of truth for revenue, cost, and inventory. Snowflake is where finance and analytics model it against sales, product, and marketing. NetSuite has no change-data-capture stream, so the usual pipeline is a nightly export, a fragile ODBC job, or a managed connector that is a black box at month-end.

• Transactions and entities land in Snowflake every few minutes on a lastModified watermark, and the connector's Record Created or Changed trigger polls a SuiteQL table from every minute for the tables that need it
• SuiteQL joins pull a transaction with its customer, subsidiary, and line items in one query, so the warehouse tables are already shaped for reporting
• Every load is a run you can inspect with the query, the row count, and the merge, so a number that looks wrong in a board is traceable to a specific sync
• Loads stay within your concurrency limit: process large backfills in chunks, outside peak hours, with Retry on failure for concurrency rejections

The load flow most finance-analytics teams turn on first.

NetSuite transactions into RAW.NETSUITE.TRANSACTION, every five minutes

Watermark-driven through SuiteQL, with a nightly full reconcile.

1. 1
   Trigger: a schedule every 5 minutes.
2. 2
   Query: Run a SuiteQL query for transactions where lastmodifieddate > :watermark, joining the entity, subsidiary, and currency, up to 1,000 rows per page.
3. 3
   Lines: a second SuiteQL query pulls the transaction lines for the same set, into a TRANSACTION_LINE table.
4. 4
   Merge: Execute Snowflake SQL with MERGE INTO RAW.NETSUITE.TRANSACTION t USING (SELECT ...) s ON t.INTERNAL_ID = s.INTERNAL_ID, in chunks for large pages.
5. 5
   Watermark: write the max lastmodifieddate seen to a control table.
6. 6
   Deletes: a nightly SuiteQL query of NetSuite's deleted-record table marks IS_DELETED = TRUE in the warehouse.
7. 7
   Nightly reconcile: a SuiteQL query of the trailing 45 days is merged, catching any row a short-window watermark missed.

The starting map for the transaction to RAW.NETSUITE.TRANSACTION step.

• Transactions and lines. Sales orders, invoices, bills, journals, and their lines land as typed tables, joined to entity and subsidiary. (NetSuite to Snowflake)
• Entities and items. Customers, vendors, employees, and the item list sync as dimension tables for the fact tables to join. (NetSuite to Snowflake)
• Custom records. Any custom record type is queried with SuiteQL and loaded the same way as a standard record. (NetSuite to Snowflake)
• Dataset results. A SuiteAnalytics dataset runs on a schedule and its result set lands as a table, keeping the report logic in NetSuite. (NetSuite to Snowflake)

The same controls apply to this sync as to every other Neblex workload.

• Run history. Every load records the SuiteQL statement, the row count, and the merge. A failed run can be replayed from the step that failed.
• Kind to governance. Large loads run in chunks on a schedule you choose, so a backfill does not crowd out other integrations.
• Scoped access. NetSuite uses a role with read access to the record types being loaded. Snowflake uses a role with grants on the target schema only.
• Environments. Build against a NetSuite sandbox and a Snowflake scratch schema, then promote the same flow to production.