File storage is one of the few NetSuite costs that grows without anyone deciding to grow it. Nobody approves it. It arrives one attachment at a time, and then one day procurement asks why the renewal went up.
The instinct is to delete things. That is the one response guaranteed to cause a problem later, because the documents taking up the space are exactly the ones an auditor will ask for.
In almost every account we have looked at, the same four things account for the overwhelming majority of the file cabinet, and only one of them is obvious.
The second row is the interesting one. Every time an invoice is printed or emailed, many configurations save the rendered PDF to the file cabinet. It is a perfect duplicate of something NetSuite can regenerate on demand from the transaction and the template. Organisations routinely carry years of these without knowing they exist.
Before any archival project, that is the first question worth asking: how much of this is regenerable output rather than source documents? It is often a surprising amount, and it is the one category where deletion is genuinely safe.
The reason storage grows unchecked is that no one owns the decision. Finance assumes IT has a retention policy. IT assumes finance has told them what the statutory period is. Neither conversation happens, so the default is to keep everything forever at the most expensive tier available.
You do not need a formal policy document to make progress. You need one number per document type: how long must this be retrievable, and how fast. A signed customer contract might be seven years and instantly. A shipping label from 2021 might be three years and slowly. Those two answers put the documents in different places and the cost difference is most of the bill.
The approach that works keeps every document and changes only where it physically sits. Three tiers is usually enough:
The part that makes this acceptable to users is the link-back. If archiving means "the document is somewhere else and you have to go find it", the project fails at the first month end, because someone senior cannot produce a document in a meeting. If the attachment still appears on the record and still opens on click, nobody notices the change happened at all, which is the goal.
Archival should be rules-based, not a one-off sweep, or you are back where you started in eighteen months. A workable starting rule set:
The exclusions matter more than the inclusions. A script file archived out of the file cabinet does not gracefully degrade, it breaks a deployment, usually at the least convenient moment. Any archival mechanism that cannot express exclusions is not ready for a production account.
Permissions. A document that was restricted in NetSuite must stay restricted after it moves. If the destination library is open to everyone in the organisation, you have not saved money, you have created a data exposure and attached a cost saving to it. Map the permission model before the first file moves, not after.
Where an account is carrying several years of attachments and generated PDFs, the archivable share is typically most of the volume, because the newest documents are a small fraction of what has accumulated. The saving is the difference between what you pay for that volume in NetSuite and what the same volume costs in SharePoint, which most organisations are already paying for through their Microsoft licensing.
That is the whole arithmetic, and it is worth doing with your own contract rate in front of you rather than a vendor estimate. We built a calculator for exactly that, because the answer is different for everyone and the inputs are all yours.
Put your own volume and contract rate in and see what archival tiering would return, monthly and over three years.
Years of building on NetSuite: SuiteScript, SuiteFlow, SuiteQL, SuiteTalk, Advanced PDF templates and Celigo integrations. We write these up when a problem comes round for the third time.
Tell us what you are running today and where it is breaking down. Most calls run 20 to 30 minutes and end with a clear next step. We reply within one business day.