Question 1

Which NetSuite connector should I use for Redshift?

Accepted Answer

SuiteAnalytics Connect, in almost every case where the goal is loading a data 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 customers actually run: the NetSuite to Redshift syncs in production 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 instead.

Question 2

What do I need before connecting NetSuite SuiteAnalytics?

Accepted Answer

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

Question 3

What NetSuite data can I load into Redshift?

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 the custom records they have built. Two tables get special handling on incremental reads, transactionLine and inventoryAssignment, which use parent driven logic rather than their own timestamps. Through SuiteTalk instead you get the record types your role can see plus a combined Transactions object.

Question 4

What happens in Redshift when a NetSuite record is deleted?

Accepted Answer

It stays until something reconciles it, which is worth planning for rather than finding out 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 is how you clear rows that no longer exist.

Question 5

Why load NetSuite into a data warehouse?

Accepted Answer

Because an ERP is where finance operates, not where the business gets understood. Reporting inside NetSuite is bounded by NetSuite, so linking orders and invoices to CRM activity, product usage or support history means getting the data out first. Scheduled ETL does that and takes heavy reporting load off a system your finance team needs to stay responsive when the month closes.

Sync NetSuite to Redshift

Sync NetSuite to Redshift with Polytomic

SuiteAnalytics for warehouses

Custom tables included

Incremental where offered

Or sync Redshift to NetSuite

Trusted by businesses worldwide

Step-by-step integration guide

Connect NetSuite in Polytomic

Connect Redshift in Polytomic

Create a sync between NetSuite and Redshift

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