From NetSuite to Actionable Insights in Minutes
No ODBC licenses. No complex ETL. Connect your NetSuite account, pick your tables, choose a destination - and Acterys handles everything else.
The connection takes minutes. What keeps it working for years is everything you cannot see.
A read, a copy, and a database you own
Four stages, and nothing between them that you have to license, install or keep running. The transport at each hop is named below it.
Your source of truth. Read-only, under your own integration record and its role.
SuiteQL over REST
Schema detection, incremental extraction, typing, scheduling and the run log.
Changed rows only
SQL Server, Azure SQL, Snowflake, Fabric or BigQuery, in your own tenancy.
Typed tables, star schema
Six report templates on the synced model, and anything else that speaks SQL.
Refreshed on your schedule
Three steps, in order
Each one is a screen in the product. Nothing here needs a developer, and nothing here is installed on a server.
Connect your NetSuite account
Create an Integration record, issue a token-based auth pair, paste it in. The connection is verified against your account before anything is scheduled.
- Token-based authentication, no password stored anywhere
- OneWorld multi-subsidiary accounts supported
- Role-based access in NetSuite is respected end to end
Select tables and set the mode
Schemas are read from your own account, so the list already carries your custom records and fields. Large tables run incremental; small dimensions refresh in full.
- Schema detection across 340+ readable tables
- Incremental mode tracks changes by last-modified date
- Custom SuiteQL where a saved search cannot express the join
Choose the destination and schedule it
The schema is provisioned in your target, the first load runs, and the schedule takes over. Every run afterwards is a line in the log with its row counts.
- Power BI direct and push datasets
- SQL Server, Azure SQL, Snowflake, Fabric, BigQuery, Databricks
- Hourly, nightly or a custom interval, per table group
What happens under the hood
The connector composes SuiteQL against NetSuite's analytical store, then types the result and loads it into your destination in a shape Power BI can model directly.
Joins, GROUP BY and subqueries are available, which is the practical difference between SuiteQL and a saved search.
JSON off the REST endpoint
A typed table
| tranid | trandate | netamount |
|---|---|---|
| INV-1042 | 2026-08-27 | 15,420.00 |
| INV-1043 | 2026-08-27 | 8,750.00 |
A star schema in the destination
One fact table for transaction lines, dimensions for account, customer, item, subsidiary and date, with the relationships already declared. The Power BI templates load against exactly this shape.
Six things that follow from not using ODBC
Most of what is below is not a feature we added. It is what you get once the driver, the gateway and the per-row meter are out of the path.
The REST web services your NetSuite licence already includes. No ODBC driver on a machine somewhere, no gateway service, no SuiteAnalytics Connect seat.
Changed rows only, tracked by last-modified date. A nightly run over tens of millions of transaction lines finishes in minutes rather than reloading them.
Every run records its tables, row counts, duration and any error. A broken sync announces itself instead of showing up as a dashboard nobody trusts.
Hourly, nightly, or a custom interval per table group, so the tables month-end depends on can move on a different cadence from the rest.
Power BI, SQL Server, Azure SQL, Snowflake, Fabric, BigQuery and Databricks from the same configured sync, into databases you own.
Data moves from NetSuite to your destination. There is no vendor-side copy of your general ledger to reason about in a security review. How we handle it.