A customization may work correctly in sandbox, but production can still behave differently if roles, permissions, data, forms, scripts, or workflows are not aligned.
Before moving a customization to production, it is important to review the setup carefully and confirm that it is ready for real users and live data.
Scenario
An administrator finishes testing a customization in sandbox.
The customization may include:
- custom fields
- custom forms
- custom records
- workflows
- scripts
- saved searches
- role-based permissions
The customization works during testing, but the admin wants to reduce risk before deploying it to production.
Solution
Complete a production-readiness review before deployment.
The goal is to confirm that the customization works not only in sandbox, but also with the actual users, roles, forms, data, and business process used in production.
What to Review Before Production
Roles and Permissions
Confirm that the correct roles can access the customization.
Review whether users can:
- see the needed fields
- edit the correct records
- access related records
- run related searches or reports
- complete the process without administrator access
A customization that works for an admin may not work for end users if permissions are different.
Forms and Field Placement
Review the production forms where the customization will appear.
Confirm that:
- fields are placed clearly
- required fields are not hidden
- form assignments are correct
- old or duplicate forms will not confuse users
- the customization appears only where needed
Data Differences
Sandbox data may not always match production data.
Before deployment, consider whether production has:
- missing values
- inactive records
- different subsidiaries, locations, or departments
- larger record volume
- older records with incomplete data
These differences can affect how the customization behaves.
Workflows and Scripts
If the customization includes workflows or scripts, confirm when they run and what they update.
Review:
- trigger timing
- affected record types
- field dependencies
- error handling
- execution logs
- interaction with existing workflows or scripts
This helps avoid conflicts with existing automation.
Saved Searches and Reports
If the customization supports reporting, confirm that related searches or reports are ready.
Check that:
- filters use the correct fields
- results show the expected data
- roles can access the search
- status or dropdown values are consistent
- reports support the intended business process
Suggested Deployment Review
Before deploying, prepare a short checklist:
- What is being moved?
- Which record types are affected?
- Which roles will use it?
- Which forms will show it?
- Which workflows or scripts are involved?
- Which reports or searches depend on it?
- Has it been tested with realistic data?
- Has the business owner approved the result?
This helps make the deployment more controlled.
References
- SA: NetSuite Sandbox (ID: 19468)
- SA: SuiteBuilder – Customization (ID: 1045873)
- SA: SuiteCloud (ID: 1014757)
Notes
- Test with the same roles that will use the customization.
- Do not rely only on administrator testing.
- Review production data conditions before deployment.
- Check whether existing scripts or workflows may conflict.
- Communicate the change to affected users.
- Have a rollback or correction plan when possible.
- Deploy during a low-risk time when appropriate.
Summary
A customization that works in sandbox still needs a careful review before production. Roles, forms, data, automation, and reporting can all affect how the customization behaves in a live account.
A production-readiness review helps reduce deployment risk, avoid user disruption, and make the customization easier to support after release.
Share your insights and experiences in the NetSuite Admin Corner.