Question 1

Which NetSuite connector should I use for Databricks?

Accepted Answer

SuiteAnalytics Connect, in almost every case where the goal is loading a warehouse. It exposes every SuiteAnalytics table and column your role can see, including custom tables, discovered from NetSuite's own metadata, which is far wider than the API surface. That also matches what runs in production: the NetSuite to Databricks syncs we see today go through the SuiteAnalytics connector rather than the standard one. Use SuiteTalk when you want API records or two way syncing with other applications.

Question 2

Can I write NetSuite tables to an external location?

Accepted Answer

Yes, with two conditions. Choosing a customer selected external destination location is a bulk sync feature, so it is not available to model syncs, and it requires Unity Catalog. You also need the grants that go with it, including CREATE EXTERNAL TABLE, READ FILES and access to the relevant storage credential. If you are on the default hive_metastore path, that option is not available and tables are managed in place instead.

Question 3

What has to be in place on the NetSuite side first?

Accepted Answer

The SuiteAnalytics Connect licence above all, since it is a paid add on and the most frequent reason a project stalls before it starts. Beyond that: OAuth 2.0 enabled, an Integration record using the machine to machine grant carrying the SuiteAnalytics Connect scope, a role with the SuiteAnalytics Connect and access token permissions, and an RSA key pair with the public certificate uploaded. You then supply account ID, role ID, client ID, certificate ID and private key. The connector also depends on NetSuite's native ODBC driver.

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 an incremental run will not flag the row as gone. The SOAP types do mention deleted records and SuiteAnalytics metadata does mark which tables allow hard deletes, but none of that is wired into the sync. A periodic full resync clears rows that no longer exist.

Question 5

Why load ERP data into a lakehouse?

Accepted Answer

Because an ERP is where finance operates rather than where the business gets understood, and reporting inside it is bounded by it. Connecting orders and invoices to CRM activity, product usage or support history means getting the data out first. ETL into a data warehouse does that, takes heavy reporting load off a system finance needs responsive at close, and puts the numbers where planning work already happens.

Sync NetSuite to Databricks

Sync NetSuite to Databricks with Polytomic

SuiteAnalytics for warehouses

Custom tables included

External locations supported

Or sync Databricks to NetSuite

Trusted by businesses worldwide

Step-by-step integration guide

Connect NetSuite in Polytomic

Connect Databricks in Polytomic

Create a sync between NetSuite and Databricks

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 Databricks?