Leaving NetSuite? Get your data out before the contract ends

What to export before your NetSuite contract ends, and how to check you got it all.

If you’re moving off NetSuite, the new system gets all the attention. The part that gets missed is what you take with you. Once your subscription ends, Oracle’s subscription agreement lets them deactivate the account and delete the data in it. There’s no grace period you should count on. Whatever you didn’t export before that date is gone.

Getting your data out is its own project. It takes longer than people expect, and it goes a lot better if it starts months before the renewal date instead of the last week.

Start with the contract

Pull your NetSuite agreement and find two dates, the end of your current term and the deadline for giving notice. Your export plan works backward from those.

While you have your account rep’s attention, ask about read-only access after you leave. NetSuite has offered data retention arrangements where a user or two keeps read-only access for a set number of years. It’s worth asking what that costs before you decide you don’t need it. If you get an offer, get it in writing, including how many users, how many years and what happens at the end.

Even with read-only access, I’d still do the export. It’s your safety net if the arrangement changes or the account gets shut off anyway.

Full CSV Export isn’t a full export

There’s a menu option at Setup > Import/Export > Export Tasks > Full CSV Export, and the name makes it sound like the answer. It isn’t. It pulls a set list of things: customers, vendors, items, employees, contacts, accounting lists, the Transaction Detail report, notes, tasks and a few others. It doesn’t get your custom records, your File Cabinet, your system notes, or the line detail on most transactions.

On an account with a few years of history, it probably won’t finish anyway. It tries to run everything in one pass and usually times out, especially on the Transaction Detail report. Oracle’s own fix is to export each list separately. It also runs off your saved searches and the list views you have selected, so if one of those searches errors, the whole export fails. I’d skip it and go straight to saved searches split by date range.

Who should run the exports

NetSuite filters every list, search and report by role. If somebody without full access runs the exports, records get left out and nobody notices because there’s no error. Have the exports run under the Administrator role, by somebody you trust, with the person who knows the data telling them what to pull.

What to get

Financials

• Chart of accounts, including inactive accounts
• Balance sheet, income statement, cash flow and trial balance by month for every year you need to keep
• Trial balance by month for the current year, by account and subsidiary. That’s usually what gets loaded into the new system as monthly JEs so you have year-to-date numbers and comparisons
• General ledger detail by period (the Transaction Detail report works well here, with transaction number and memo added)
• AR and AP aging as of your cutover date, plus the open invoices and bills themselves with number, date, due date and open balance, so they can load as open items in the new system
• Customer credits, unapplied payments and customer deposits. These don’t show up on an invoice aging, and they’re easy to lose
• Sales tax reports and filings
• Fixed asset register and depreciation schedules, if you use the Fixed Assets module
• Bank and credit card recs

Reports are easier than saved searches for financials because the totals already match what you’ve been reporting. Talk to your CPA about what else they want kept and for how long.

Master data

Customers, vendors, items, employees, contacts, partners, price levels and terms. Include inactive records. You may not load them into the new system, but you’ll want to be able to look them up. On vendors, get the tax ID and 1099 flag. On items, get UPCs, vendor part numbers and the web descriptions and images if NetSuite feeds your website.

Transactions with line detail

SOs, invoices, credit memos, customer payments, POs, item receipts, vendor bills, bill payments, JEs, IFs, inventory adjustments and transfers, work orders and assembly builds. Whatever you use. Build a saved search for each type with the line detail you need.

Export the internal ID on every row, and the created from and applied to links on transactions. That’s what lets you tie an invoice back to its SO or a payment to the bills it paid.

Watch for duplicates though. A transaction search returns a row for every line, including tax, shipping and COGS lines, so one invoice can show up a dozen times. Adding applied to fields multiplies that again when one payment covers several bills. Set Main Line on purpose, true for one row per transaction or false for line detail, and dedupe on internal ID before you total anything. Otherwise your totals will come out higher than NetSuite’s.

Inventory

On hand by location with cost, plus bin, lot and serial detail if you use them. That’s what your opening inventory in the new system gets built from, so it has to tie to the inventory balance on your trial balance. Check for inactive items that still have quantity on hand. They drop out of most searches and they’re the first thing that makes the count not tie. If you track serial numbers, export the serial history too. Once NetSuite is gone, that’s usually the first question somebody can’t answer.

Documents and attachments

Files attached to records live in the File Cabinet. You can download a folder from the Documents tab and it comes down as a ZIP with the folder structure kept. For a lot of folders, that’s slow, and bulk downloads for large volumes usually take a script.

The file itself doesn’t tell you which record it belonged to. Run a saved search of files joined to the records they’re attached to, so you know which PDF goes with which vendor bill.

The invoice and PO forms you print from NetSuite are generated when you print them. They aren’t saved anywhere unless they were emailed or attached. If you need PDF copies of transactions, you have to print them before you go.

You can do that in bulk. First make sure Print Using HTML is unchecked under Home > Set Preferences > Transactions so it prints to PDF. Then go to Transactions > Management > Print Checks and Forms and pick the transaction type. Check Allow Reprinting so everything shows up, not just what’s waiting to print, filter by date, Mark All and Print. You get one combined PDF per batch, so run it a month or a year at a time or it’ll time out. It covers the types on that page, like invoices, bills, POs and credit memos.

If you want one PDF per transaction, named by transaction number, that takes a script that saves each one to a File Cabinet folder. Then you download the folder as a ZIP.

Audit trail

System notes show who changed what and when. They don’t come out in any standard export, so build a system notes saved search for the records and date ranges your auditors care about. Grab the login audit trail while you’re there.

Your customizations

This one is easy to skip because it isn’t data, but it’s the record of how your business actually ran. Custom fields, custom records, saved searches, workflows, scripts, advanced PDF templates and email templates. When somebody asks why the new system doesn’t auto-approve POs under a certain amount, the answer is sitting in a workflow you’re about to lose.

The easiest way to document it is to have Claude do it. With the NetSuite AI connector set up, Claude can pull your scripts, custom records, saved searches and the custom fields on each record type. It can sort out what came from SuiteApps and what was built for your company, then write up the custom pieces in plain English. Your admin has to set up the connector and a role for it first.

The connector can’t see workflows. For those, use the Claude browser extension. Open a workflow in NetSuite and it can read the states, conditions and actions and write up what the workflow does.

Claude is reading names, settings and screens, not the script code itself. Have whoever built or uses each piece check the write-up. A plain line like “POs over $5,000 go to the controller for approval” is what your new system’s implementer actually needs.

If you’d rather do it by hand, most of it can be exported as lists from Customization > Lists, Records & Fields, Customization > Scripting and Customization > Workflow. Download the SuiteScripts folder from the File Cabinet to keep the script files, and copy the source of your advanced PDF templates into text files.

If you have a developer or an advanced admin, SDF can import your customizations from the account into a project. That gets you the actual definitions and script files in one place, which is the most complete copy you can keep.

Make a list of your integrations too, what connects to NetSuite, what it sends and what it receives. Each one needs to be shut off or repointed at cutover.

Map these before anything moves

Your exports are full of references. A customer points to a sales rep, a subsidiary and terms. An item points to a vendor, units and accounts. The new system needs its own version of each of those set up before the records that use them can load.

• Chart of accounts. Every NetSuite account has to map to an account in the new system, including inactive ones that show up in history. Keep it in a spreadsheet with the old number, old name and new number. Items, transactions and GL history all point at accounts, so nothing else loads right without it.
• Subsidiaries. If you have more than one, every customer, vendor, item and transaction belongs to one. Decide how those map before anything loads. Export your intercompany balances too, and make sure both sides agree at cutover.
• Locations, departments and classes. Transactions and GL detail carry these, and your financials are probably reported by them. Map each one to its match in the new system, including inactive ones, or your history won’t roll up the same way.
• Sales reps. The sales rep on customers and transactions is an employee record in NetSuite. Export employees, including inactive ones, so old orders still show who sold them.
• Units of measure. Export your unit types and conversion rates. If you buy by the case and sell by the each, quantities will be off until the units line up.
• Vendors before items. Items carry the preferred vendor and vendor pricing, so vendors have to be in the new system before items load. Same idea for customers before open orders.

Keep the NetSuite internal ID in every mapping sheet. That’s what you match on.

A few things that trip people up

Large exports time out. Split them by date range, or by year, and check the row counts. For big accounts, SuiteAnalytics Connect or SuiteQL is faster, though Connect is an extra fee.

Excel turns long numbers into scientific notation when you open a CSV. UPCs, serial numbers and account numbers get mangled, and anything past 16 digits gets lost. Export to Excel instead of CSV, or open the CSV through the Text Import Wizard and set those columns to text.

Don’t plan the final export during month-end or year-end close. Your accounting team is too busy to check it.

Check it before you cancel

A backup nobody checked is a guess. Tie the trial balance from your exports to NetSuite. Compare record counts for each export. Make sure open AR and AP match. Open a few files to make sure they aren’t corrupt. Write down what you exported, when and who ran it.

Store it in two places, and make sure it’s somewhere with access controls. It’s your whole customer list and financial history.

If you can swing it, turn off everybody’s login but keep the account for a few weeks after you’re working in the new system. See what people come asking for. That tells you what you missed while you can still go get it. Keeping it through your first close in the new system is even better.

Need help getting it out?

We do this work for companies coming onto NetSuite and companies leaving it. If you’re facing a renewal date and aren’t sure what all you need, we’ll go through your account with you. Book a free hour.

Author: Renee Chandler, Fourth Wave Consulting. NetSuite accounting and finance.