NetSuite Integration Throughput Calculator
Before you promise a migration date, estimate how long the load will take. This calculator turns average call time, parallel threads and retry rate into records per hour and total load time, and shows how adding threads changes the answer.
Your numbers
Total records, including line items counted as separate calls if you send them separately.
Use 1 for record-by-record APIs, or the batch size if your call handles several.
Measure in sandbox with realistic payloads and scripts.
Do not exceed your account's concurrency allowance.
Share of calls repeated because of errors or timeouts.
Your results
A planning estimate only. Real throughput depends on scripts and workflows on the record, account concurrency limits, record complexity and time of day. Measure with a representative sample in sandbox first.
Load time (hours) vs parallel threads
Sweeps Parallel threads used from 1 to 20, holding your other inputs fixed.
Plan your migration load
Optional: talk to us about load strategy and validation for a large NetSuite data migration.
Optional. The tool and every export work without this. No spam.
How to use the calculator
Enter the number of records and how many go in each call. Measure the average call time in a sandbox with realistic data, since customizations on the record change it a lot. Set the number of parallel threads you plan to use and the share of calls you expect to retry. The result gives records per hour, total hours, and the number of days if you only load in a set window each day. The chart sweeps threads from 1 to 20.
- Measure call time with real payloads
- Count child lines as calls if they are sent separately
- Keep threads within your concurrency allowance
- Re-measure when scripts or workflows change
The formula
Effective call time is the average call time times one plus the retry rate. Records per hour is threads times 3600, divided by the effective call time, times records per call. Total time is records divided by that rate. The model assumes calls are independent and that threads do not slow each other. In practice, more threads can raise the average call time through lock contention and governance limits, so treat the high-thread end of the chart as an upper bound.
Reading the result and common mistakes
Use the result to compare loading strategies: more threads, larger batches, disabling nonessential scripts for the load where policy allows, or splitting the load across several nights. The usual mistakes are measuring on an empty sandbox, ignoring that user event scripts and workflows fire on each record, and forgetting that business users share the same account concurrency during the day.
- Test in a sandbox with production-like scripts
- Plan for a re-run of failed records
- Avoid loading during peak business hours
- Check concurrency limits for your account and service tier
Frequently Asked Questions
Why is my real throughput lower than the estimate?
Parallel calls to the same account can queue, scripts and workflows add time per record, and locks on shared records such as items or customers can serialize updates. Measure with the real thread count rather than extrapolating from one.
What is a good retry rate?
Start with a few percent for planning and measure in sandbox. A high retry rate usually points to a validation problem or lock contention that should be fixed rather than tolerated.
Does batching help?
It can, when the interface supports several records per call, because it cuts the per-call overhead. Compare the time per record, not the time per call, and check limits on payload size.
Is this specific to one NetSuite API?
No. It is a generic model that works for REST, SOAP web services, RESTlets or CSV import jobs, as long as you supply a measured call time and a concurrency you are allowed to use.
If you need to load or sync large volumes from another system, Netray can help design and build the integration and validate it against your account.
Related Tools
NetSuite Integration Field Mapping Worksheet
Map source system fields to NetSuite fields with transforms, defaults and validation notes, and export the table to Excel for the build team.
NetSuiteNetSuite RESTlet API Specification Template
Document a RESTlet endpoint with methods, payloads, authentication and errors so integration partners can build against it, and export to PDF or Word.
NetSuiteSuiteScript Code Review Checklist
A practical review checklist for SuiteScript 2.x covering structure, governance, error handling, security and deployment.
NetSuiteNetSuite Sandbox to Production Deployment Runbook Template
Plan a NetSuite release with scope, deployment steps, validation and rollback in one runbook, and export it as PDF or Word.
More NetSuite tools
See all- NetSuite Saved Search Formula Generator
- NetSuite CSV Import Template Guide
- NetSuite Role Permission Matrix Worksheet
- NetSuite Inventory Costing Method Reference
- NetSuite Month End Close Checklist
- NetSuite License Cost Estimator
- NetSuite User Access Request Form Template
- NetSuite Custom Record Design Spec Template
- NetSuite SuiteScript Deployment Handover Template