NetSuite to Databricks: How to Move Your Data

Moving NetSuite into Databricks takes the system that knows what your business actually earned and puts it where the rest of your data already lives. The usual alternative is a saved search exported on a schedule, which works until someone edits the search, and gives you a report rather than a dataset.

This guide covers the managed path with Airbyte. One thing about this connector is unlike almost every other source in the catalogue and shapes the entire project: the NetSuite role you connect with determines which streams exist. Your schema is a permissions decision made by a NetSuite administrator, not a property of NetSuite itself.

NetSuite to Databricks at a glance:

Why move data from NetSuite to Databricks?

Two situations account for most of these pipelines.

The first is joining finance to everything else. NetSuite holds invoices, revenue and the general ledger. Your product database knows what customers use, your CRM knows who sold to them, and questions about margin per customer or revenue per feature need all three in one place. That place is not NetSuite.

The second is analytical work NetSuite is not built for. Cohort analysis, forecasting, anything involving Python or a notebook. Databricks gives you that plus Unity Catalog governance over data that is, by definition, sensitive. If all you need is a monthly report NetSuite can already produce, this pipeline is more machinery than the question deserves.

What do you need before you start?

Two of these are NetSuite configuration that may not be in place, so confirm them before scoping anything:

SuiteAnalytics Connect, enabled and licensed. The connector needs a NetSuite environment using SuiteAnalytics Connect and the NetSuite2.com data source for integrations. This is a NetSuite feature question rather than an Airbyte one, and the answer is occasionally no.

A dedicated read-only user with the right role. The role needs read access to every table you intend to replicate, and at minimum the SuiteAnalytics Connect permission to connect over JDBC at all. Both the user and the role matter here, for reasons covered below.

Connection details from the NetSuite UI. Host, port (typically 1708), account ID and role are all found on the NetSuite home page under Settings, then Set Up SuiteAnalytics Connect. The account ID identifies the NetSuite account rather than the individual user. The NetSuite source documentation covers each field.

A security review of the SSL constraint. Airbyte does not support connecting over SSL using a custom Certificate Authority. If your organisation mandates a private CA for all outbound connections, raise this before you build rather than during a review.

On the Databricks side, each stream becomes a table in Unity Catalog and the connector needs permission to create Volumes for Avro staging. Given this is financial data, agree the catalog and schema with whoever owns governance before the first sync rather than after.

How do you build a NetSuite to Databricks pipeline in Airbyte?

Step 1: Design the NetSuite role deliberately

Work with your NetSuite administrator to create a role granting read access to exactly the tables you want replicated, and no more. This is the most consequential step in the build, because that role becomes your data model. Write down what it can see, and treat future changes to it as schema changes rather than routine permission edits.

Step 2: Configure the NetSuite source

Click Sources in the left navigation, then New Source, and select NetSuite, following adding a source. Supply the host, port, account ID and role, then choose an authentication method. The connector supports every method SuiteAnalytics Connect offers: username and password, token based authentication, and OAuth 2.0. Token based authentication is the usual choice for an integration, since it does not tie the pipeline to a person's password.

Step 3: Configure the Databricks destination

Click Destinations, then New Destination, and select Databricks, following adding a destination. Supply your workspace details, the catalog and schema, and authentication. Airbyte creates one table per stream with its own metadata columns alongside your data.

Step 4: Pick cursors and sync modes per stream

Click Connections, then New connection, and select tables and a sync mode. Incremental here is cursor-based rather than log-based, so each stream needs a column that only increases and is set on every write. NetSuite's modification timestamps usually serve, but verify per table rather than assuming, because a table where the cursor does not move on update will silently stop reflecting changes.

Start with a small set of tables and confirm the row counts against NetSuite before extending. On a system where the numbers are the point, validating early is cheaper than explaining a discrepancy to finance later.

Why does your NetSuite role define your schema?

Streams are generated based on the role and user access, together with account settings. The connector does not enumerate everything NetSuite contains and then filter. It sees only what the connecting role can see, and builds the catalogue from that.

The practical consequences are worth spelling out. A table missing from your catalogue is usually a permissions gap rather than an unsupported stream, so the fix is in NetSuite rather than in Airbyte. And an administrator adjusting that role months later, for entirely unrelated reasons, changes what your pipeline can read. Nothing warns you: the stream simply stops appearing.

So use a role dedicated to this integration rather than an existing finance or administrator role, and name it so its purpose is obvious to whoever inherits NetSuite administration. It costs nothing at setup and prevents the class of failure where a well-meant permissions tidy-up breaks a downstream model nobody connected to it.

What does an incubating connector mean in practice?

Airbyte describes this as an incubating enterprise source, and that is worth taking at face value rather than glossing over. It means the connector is actively developing, and its behaviour and configuration may change more than a long-established connector's would.

That is not a reason to avoid it. It is a reason to validate rather than assume. Reconcile a few tables against NetSuite's own reporting during the first weeks, keep an eye on connector release notes, and avoid making this pipeline the sole source for anything a regulator or auditor will look at until you have watched it behave for a while.

Note also that a separate community NetSuite connector exists which reads the REST interface rather than SuiteAnalytics Connect, with a quite different permissions setup involving manually adding access to Transactions, Reports, Lists and Setup entities. If someone in your organisation has previously built a NetSuite pipeline, check which of the two they used before assuming the setup carries over.

Frequently asked questions

Why is a NetSuite table missing from my catalogue?

Almost always a role permissions gap. Streams are generated from what the connecting role and user can access, so grant the role read access to that table in NetSuite and refresh the source schema.

Does the NetSuite connector support change data capture?

No. It offers full refresh and cursor-based incremental syncs, so deletions are not captured and updates are only seen when they advance the cursor column.

Do I need SuiteAnalytics Connect?

Yes, along with the NetSuite2.com data source for integrations. The role also needs the SuiteAnalytics Connect permission at minimum to connect over JDBC.

Can I connect using a custom Certificate Authority?

No. Connecting over SSL with a custom CA is not supported, so check that against your organisation's requirements before designing around this connector.

Can I do this without writing code?

The Airbyte setup is entirely UI-driven. The NetSuite side needs an administrator to enable SuiteAnalytics Connect and create the role, which is configuration rather than code.

Get your NetSuite data into Databricks

Confirm SuiteAnalytics Connect and the SSL constraint before scoping the project, then design a dedicated role and treat it as your schema definition. Verify cursors per table, start with a small set, and reconcile against NetSuite before anyone builds a model on top.

Airbyte's connector catalog includes 600+ pre-built connectors, so finance data can sit alongside product and CRM sources in the same lakehouse. For NetSuite into a warehouse instead, see NetSuite to Snowflake, and for another enterprise source with heavy prerequisites, IBM Db2 to Databricks.

Start syncing now →