Question 1

Which NetSuite connector should I use here?

Accepted Answer

SuiteAnalytics Connect, in almost any case where the goal is loading a warehouse. It exposes every SuiteAnalytics table and column your role can see, custom tables included, discovered from NetSuite's own metadata, which is a far wider surface than the API offers. The standard NetSuite connector runs on SuiteTalk REST and SOAP and is the right choice when you want API records or two way syncing with other applications instead.

Question 2

What has to exist before the first sync?

Accepted Answer

On the NetSuite side, a SuiteAnalytics Connect licence, OAuth 2.0 enabled, an Integration record using the machine to machine grant with the SuiteAnalytics Connect scope, a role carrying the right permissions, and an RSA key pair with the public certificate uploaded. On the ClickHouse side, an account with SELECT, INSERT, CREATE TABLE, DROP TABLE, TRUNCATE and ALTER, plus CREATE DATABASE if you want Polytomic to create the target database rather than creating it yourself first.

Question 3

What NetSuite data can I load?

Accepted Answer

Through SuiteAnalytics Connect, the full set of tables and columns available to your role, which for most finance teams covers transactions, transaction lines, entities, items, accounts and any custom records. Two tables get special handling on incremental reads, transactionLine and inventoryAssignment, which use parent driven logic rather than their own timestamps. Through SuiteTalk you instead get the record types your role can see plus a combined Transactions object.

Question 4

What happens when a NetSuite record is deleted?

Accepted Answer

It stays until something reconciles it, which is worth planning for rather than discovering during a close. Neither NetSuite path turns deletions into delete events today, so no incremental run will flag the row as gone regardless of what the destination supports. The SOAP types do mention deleted records and SuiteAnalytics metadata does mark hard deletable tables, but none of that is wired into the sync. A periodic full resync is the answer.

Question 5

Why load ERP data into ClickHouse?

Accepted Answer

Because reporting inside an ERP is bounded by the ERP, and the joins people want reach outside it. Connecting orders and invoices to product usage or support history means getting the data out first. Where ClickHouse specifically earns its place is when that operational data is high volume, since a ledger joined to millions of events is a scan heavy query and that is what this engine is designed to make fast.

Sync NetSuite to ClickHouse

Sync NetSuite to ClickHouse with Polytomic

SuiteAnalytics for warehouses

Custom tables included

Database created for you

Or sync ClickHouse to NetSuite

Trusted by businesses worldwide

Step-by-step integration guide

Connect NetSuite in Polytomic

Connect ClickHouse in Polytomic

Create a sync between NetSuite and ClickHouse

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect NetSuite with ClickHouse?