What data is copied from Production during a Sandbox Refresh?

During a Sandbox refresh, NetSuite copies the vast majority of data and configuration from the production account to create a realistic testing environment. This includes master and transactional records, such as customers, sales orders, and invoices. System Notes, which provide an audit trail of changes on these records, are considered part of the record's data and are therefore copied along with the records themselves. For security and operational reasons, sensitive and environment-specific configurations like authentication tokens, user passwords, and SAML settings are explicitly excluded from the refresh process.

A. Token-based Authentication (TBA) tokens are security credentials tied to the production environment and are not copied to prevent unauthorized access.
B. User passwords are not copied to the sandbox for security. Users are required to set a new password upon their first login to the refreshed sandbox.
C. SAML configuration is specific to the production account's URLs and identity provider setup; it is not copied and must be reconfigured in the sandbox.

1. NetSuite Help Center. (2023). SuiteAnswers, Data Not Copied from Production to a Sandbox Account. (Answer ID: 9945). This document explicitly lists "User passwords," "SAML Single Sign-on configuration," and "Token-based Authentication (TBA) tokens" as data that is not copied during a refresh.

2. NetSuite Help Center. (2023). SuiteAnswers, Sandbox Accounts. (Answer ID: 10092). In the "Understanding the Sandbox Refresh Process" section, it states that a refresh replaces the sandbox with a "fresh copy of the production account," which includes the records and their associated data. Since System Notes are not on the exclusion list (Answer ID: 9945), they are included in this copy.