When You Leave NetSuite, Don't Leave Your Audit Trail Behind
When a company moves off NetSuite, transaction data gets migrated — but what about the attachments auditors actually ask for? A real-world case on structured document archival during ERP migration.
"Most ERP migrations move the numbers. Very few preserve the evidence behind them."
A gap no one planned for
The client had made the decision: NetSuite was out, a new ERP was in. The migration team mapped every transaction, every customer record, every open balance. The go-live looked clean.
But no one had asked what would happen to the File Cabinet — the thousands of attachments accumulated over years of operations. Vendor invoices. Purchase order scans. Customer agreements. Payment confirmations. All sitting inside NetSuite, completely outside the migration scope.
Once NetSuite was decommissioned, access to those files would be gone. And in the event of a tax audit or regulatory review, those files are exactly what gets requested first.
An unstructured export helps no one
A bulk export without organisation would produce thousands of files with no context, no traceability, and no way to find anything under audit pressure.
Why auditors ask for attachments, not just data
Numbers in an ERP are a record of what happened. Attachments are the proof. When a tax authority reviews a purchase transaction, they ask for the vendor invoice, the purchase order, the delivery note — the exact files stored as attachments in NetSuite.
| Region | Framework | Retention Period |
|---|---|---|
| India | Companies Act | 8 years |
| United States | IRS Guidance | 7 years |
| European Union | Varies by country | 6–10 years |
An ERP migration does not pause these obligations. The company is still legally responsible for producing historical documents years after the system change — regardless of which ERP they are now running.
Structure that makes retrieval obvious
Instead of exporting files and hoping for the best, we designed a hierarchical folder structure that mirrors how the business actually thinks about its records — by entity, year, month, and transaction.
A flat pile of files. No vendor, no date, no transaction reference. Finding anything requires manual search.
📁 Export/
file_001.pdf
scan_002.pdf
invoice_copy.pdf
doc_final_v2.pdf
attachment_778.pdf
... 4,000+ filesEvery file traceable by entity, date, record type, and transaction ID. Navigation is direct and obvious.
📁 Customer_ABC/
└── 2026/
└── March/
└── PO_12345/
├── invoice.pdf
├── receipt.jpg
└── agreement.pdfBuilt on SuiteScript, designed for scale
The solution was built entirely within NetSuite using SuiteScript to automate folder creation, file extraction, and archive organisation — before the decommissioning window closed.
| Script Type | Purpose |
|---|---|
| Map/Reduce Script | Batch processing of large record volumes across all transaction types |
| Scheduled Script | Chunked, governance-safe export runs within NetSuite limits |
| RESTlet / Suitelet | Triggering export runs and monitoring progress in real time |
Two categories, fully covered
| Category | What It Covers | Status |
|---|---|---|
| Transaction Attachments | Purchase Orders, Invoices, Bills, Journals, and all related transaction records | ✓ Delivered |
| Entity Attachments | Files stored directly on Customer and Vendor master records | ✓ Delivered |
What the client gained
Storage options
The same folder structure works across different storage targets depending on the client's infrastructure:
The lesson for every ERP exit
Transactional data gets all the attention in an ERP migration — and rightly so. But the attachments behind those transactions are the ones regulators and auditors actually care about.
A structured archival strategy adds limited effort to a migration project. The cost of not having one — when an auditor comes looking for a 2022 vendor invoice three years after you've left NetSuite — is significantly higher.