Skip to content

ERP and finance

How to find and size your NetSuite data.

Count the transactions NetSuite holds with a saved search, and see how Full CSV Export, search exports, Persist (CSV) and SuiteQL work if a buyer licenses it.

Find how much you have

  1. Sign in with a role that can build saved searches and export them. Go to Reports, then Saved Searches, then All Saved Searches, then New, and select Transaction. Oracle says exporting results needs the Export Lists and Perform Search permissions, so ask an administrator if you do not see an Export button.

  2. On the Criteria subtab, add Main Line set to Yes. Oracle says this returns one row per transaction and skips line details, and that without it header and line data come back as separate rows, which pushes the count up. The filter does not work for Journal Entry searches, so count journal entries separately and say whether you counted entries or lines.

  3. Add a Date filter that covers your whole history. Oracle describes named periods, custom ranges with a start and end date, and relative ranges. If the search later times out, run it one year at a time.

  4. On the Results subtab, set the transaction type field to the Group summary type and Internal ID to Count. Oracle describes Count as counting the results found for that column and Group as rolling results up by the field. Run it and add up the rows. The total is the number to report, and the per-type breakdown goes in your description.

  5. Add the Date field with the Minimum summary type, which Oracle describes as showing the earliest date value, to find where your records start. Check it against the date you went live, since data migrated in from an older system may start earlier.

  6. If the search times out or will not export, use Persist (CSV) from the All Saved Searches list. Oracle says it runs the search in the background for up to 3 hours and saves a CSV that stays available for 7 days.

  7. Customers, vendors, items and employees are lists, not transactions. Count them from their own record searches or from the Full CSV Export files, and put them in the description rather than in the transactions total.

What to put on your intake

Your intake has five boxes for each system. Here is what goes in each one for NetSuite.

What does it hold?
Your company's financial record: transactions such as invoices, bills, payments, purchase orders and journal entries, the chart of accounts, customers, vendors, items, and the notes and memos on records. Say which subsidiaries and modules are in use. Something like: AP and AR transactions, purchase orders and month-end journals across three entities.
Data types
Structured records. Add Text if memo fields and record notes are in scope and you are willing to license them, since they often name customers and vendors.
How big is it?
Choose Transactions and enter the total from the grouped saved search with Main Line set to Yes. Put the per-type counts and the number of customers, vendors and items in the description.
Verified or estimated
Verified when the figure is the saved search total over your full date range. Estimated when you scaled up from one period or could not apply Main Line, for example for journal entries.
Records start
The earliest transaction date from the Minimum summary on Date. If you migrated from another system, say whether the earlier years came in as individual transactions or as opening balances.

Exporting the full history

If a buyer licenses your records, this is how the full history comes out of NetSuite.

  1. A buyer export happens only after a license is signed and the scope is agreed: which subsidiaries, which years, which transaction types, and whether memos and notes are in. Oracle's help pages we reviewed do not describe what happens to your data when a subscription ends, so confirm that with Oracle or in your contract before you end it, and take your own copy first.

  2. Full CSV Export is the built-in route. An administrator goes to Setup, then Import/Export, then Export Tasks, then Full CSV Export, and clicks Submit. The result is a ZIP of CSV files for the lists Oracle names, including customers, vendors, items, employees, contacts, notes and a Transaction Detail Report. Oracle says it does not export all data, and that it runs your saved searches, so a saved search that fails can make the export fail.

  3. For targeted exports, open a saved search and click Export - CSV on the results page, or open a report and click its export icon in the footer. Add Internal ID as a results column so relationships between records survive, which Oracle recommends. For a transaction history, Oracle says a customized Transaction Detail report can filter by transaction type and add columns such as transaction number and memo.

  4. For large searches, use Persist (CSV). In All Saved Searches, click Persist (CSV) for the search. When it completes, a download link appears on the Search Results page. Oracle says the CSV is deleted after 7 days, and that a search still pending after 24 hours is marked failed, in which case you can run it again.

  5. Developers can run SuiteQL over REST: send a POST to the suiteql resource with the required Prefer: transient header and page with limit and offset. Oracle says this returns at most 100,000 results, and that for more you can use SuiteAnalytics Connect with the NetSuite2.com data source. Oracle also lists a SOAP web services program, and says ODBC access through SuiteAnalytics Connect is an additional service with a fee.

  6. Notes on records can be pulled with a System Note or User Note search, or in some cases through a search on contacts, customers or vendors. Under the license, customer, vendor and employee identifiers, bank and card details, and payroll data are removed before anything reaches a buyer.

We only ask for an export after you sign a license and agree the scope. Sizing your data for the intake never needs one.

Limits to know

  • Full CSV Export is not a full export. Oracle says it does not currently export all data. Oracle says list exports follow the view you have selected for each list, so check each list's view first, and if the export times out you can export smaller sets from the pages for the lists or reports it names.
  • Oracle's pages give different row limits. One article says search results are limited to 10 MB, roughly 20,000 rows and 50 columns when exported to CSV, and that most reports stop at 25,000 rows or 75,000 for a listed group. Another topic says reports stop at 100,000 rows on demand and 1,000,000 when run in the background, and that saved searches do not have row limits like reports, although very large exports may fail. Split by date range and use Persist (CSV) rather than trusting any one figure.
  • CSV loses precision. Oracle says CSV exports limit decimals to 2 places, do not support Unicode, and expand collapsed rows. For more precision, export to Excel first and then save as CSV. Excel also shows numbers of more than 16 digits in scientific notation, which loses digits, so open CSVs with Excel's Text Import Wizard and set the column to Text.
  • Text columns in search results are limited to 4,000 bytes, so long memos can come out cut short. Check any field a buyer will rely on.
  • Counting transactions is easy to get wrong. Without the Main Line filter a transaction search returns separate header and line rows, and the filter does not work for journal entries. Say in your description how you counted.
  • Address and contact fields travel with exports. Oracle warns that users can export all address result fields on the customer record to Excel or CSV, including addressee, the address lines, city, state, zip code and country. Those are among the fields removed before delivery.
  • Developer routes have caps. Oracle says SuiteScript searches through the N/search module are limited to 1,000 records, REST SuiteQL returns at most 100,000, and custom transaction body fields queried with SuiteQL may not return data from their corresponding subtabs. Check custom records against a saved search.
  • If you are an accounting or bookkeeping firm that keeps clients' books in NetSuite, those records belong to the clients, and a firm can license them only with each client's specific consent under the AICPA Code (1.700.001). Income tax return information is never licensed (IRC §7216, 26 U.S.C. 7216). This is general information, not legal advice.

This guide isn't legal advice. Check your contracts, and any recording-consent rules that apply, with your own lawyer.

Why buyers value it

NetSuite is where a company's money moves through recorded steps: orders, bills, payments, adjustments and the month-end close. For software, distribution, manufacturing, retail and services companies it is the system of record for finance operations, and years of transactions, with the memos and notes around them, show how invoices get coded, how exceptions are handled and how the books get closed.

Buyers building finance and accounting automation, and evaluation sets for it, want real ledger activity with the reasoning attached, across more than one entity and several years. It is strongest alongside your payables and approval tools, because then each ledger entry has the document trail that produced it.

What stays private

Customer, vendor, employee and partner names, street addresses, phone numbers, email addresses, tax IDs and bank or card details are removed from transactions, lists, memo fields and notes before delivery under the license. Payroll, compensation and HR records are excluded. Attachments are excluded by default, since they often belong to someone else.

Your logins, roles and permissions, saved searches, scripts and integration credentials are not part of the license. If NetSuite holds clients' books because you are an accounting firm, those are client records and need each client's specific consent under the AICPA Code of Professional Conduct (opens in a new tab). Income tax return information is never licensed under IRC §7216 (opens in a new tab), and 26 CFR 301.7216-2 (opens in a new tab) bars selling even anonymous statistics built from it. This is general information, not legal advice.

Common questions

No. Oracle says it does not currently export all data. It covers the lists Oracle names, such as customers, vendors, items, employees, notes and a Transaction Detail Report, and only administrators can run it. Transactions usually come from saved search or report exports, or from SuiteQL.

Probably because header and line data come back as separate rows. Oracle says adding the Main Line filter set to Yes returns one row per transaction. The filter does not work for journal entry searches, so those need their own count.

Only for very large pulls. Oracle says REST SuiteQL returns at most 100,000 results and suggests SuiteAnalytics Connect with the NetSuite2.com data source beyond that. Oracle says ODBC access is an additional service with a fee. Most owners can size and export with saved searches and Persist (CSV).

Not on your own authority. Client records belong to the client, and the AICPA Code (1.700.001) requires the client's specific consent before a member in public practice discloses confidential client information. Income tax return information is never licensed (26 U.S.C. 7216; 26 CFR 301.7216-2(o)). This is general information, not legal advice.

Sources

Vendor documentation, checked . Screens and plans change, so if a step looks different in your account, check with NetSuite.