you could use NSAW for that OR CSV.
Benefits; TIME…. to bring historical transactional data into NetSuite as transactions into NetSuite you must do all of the following
1. ensure all Item/product data matches a NetSuite item…. this is usually a lot of work as it is typical during conversion legacy items are left behind and items tend to get renamed.
2. ensure all customer related data on the transaction data matches a NetSuite customer. again this is usually a process to get it to match
3. ensure all vendor related data on the transaction data matches a NetSuite vendor record. again this is usually a process to get it to match
4. create accounting periods for all historical transactions to land in…. THEN those periods should be reconciled and closed.
5. transactions created in this way either need to be taken all the way through the process….. Order,Bill,Fulfill,Pay…. Or Order, receive, bill, pay OR they need to closed.
a. as a side note to this one I am sure there are a 1000000 opinions on this or ways to. handle it but that only accentuates my point. there is a lot in involved here.
6. make sure all of the pricing/costing information is correct historically otherwise your NetSuite reports will never tie out to the reports from your prior system and the auditors will never be happy.
7. more steps and more steps after that.
To bring transactional data into NetSuite as Custom Records…. you create a custom record with text or number fields and import them. you can optionally create link to the new NetSuite customer records using External Ids and import the data. WAY less work for fewer failure points.
This is a BIT of a simplification but its likely weeks less work.