Data Not Copied from Production to Sandbox in NetSuite 2026.1

TL;DR Opening

Starting in NetSuite 2026.1, several critical elements, including domains, customer role assignments, and SAML configurations, are not copied from the production environment to the sandbox during refreshes. This impacts how administrators set up and manage testing environments, necessitating careful planning.

What's New

In NetSuite 2026.1, when performing a sandbox refresh, administrators and developers must be aware that certain essential data and configurations will not transfer from production to sandbox. Understanding these exclusions is crucial for maintaining seamless operations and effective testing in the sandbox. Below is a detailed overview of what is not copied:

Data Not Copied During Refreshes

1. Websites and Web Store Domains
   Domains from your production account are not transferred to the sandbox account. You must set up unique domains in each sandbox to avoid errors during functionality tests.

2. Hard-coded Link Behavior
   Hard-coded internal and external links remain unchanged post-refresh. It's advisable to use dynamic tags or placeholders to ensure links work correctly in the sandbox environment.

3. Customer Center Role Assignments
   Customer role assignments are not copied over. To restore these functionalities, administrators should CSV import customer records post-refresh and enable the necessary access settings.

4. SAML Configuration
   SAML settings for single sign-on do not transfer, and reconfiguration is necessary to ensure authentication works as expected. Note that while some configurations might appear to carry over, they may not function correctly after refresh.

5. System Notes on Records
   System notes are not included in sandbox environments. This lack can impact auditing and tracking change history within sandbox testing.

6. Deleted Records
   Any records marked as deleted in production will not appear in the sandbox, emphasizing the importance of handling deletions carefully.

7. SuiteFlow (Workflow) History Logs
   Workflow instances and their history are also excluded, which could impact process testing.

8. Token-based Authentication (TBA)
   Tokens can't be transferred, requiring administrators to recreate them in the sandbox after each refresh.

9. OAuth 2.0 Applications
   Authorized applications must be reauthorized in the sandbox after each refresh to function correctly.

10. Eliminate Intercompany Transactions
    Status results of these tasks will differ across environments and may lead to inconsistent data.

11. Campaign Response History
    Historical data on campaign responses is not copied over, which could affect marketing analytics in the sandbox.

Who This Affects

• Administrators: Need to reconfigure multiple settings, notably domains and user roles, after sandbox refreshes.
• Developers: Must adjust workflows, code paths, and authentication settings according to what is available in the sandbox.
• Customer Support Teams: Should be aware of missing data to avoid misinformation regarding sandbox capabilities.

Key Takeaways

• Domains must be set up uniquely after each sandbox refresh.
• Hard-coded links should be avoided; prefer dynamic tags.
• Essential role assignments may require CSV imports post-refresh.
• SAML configurations and OAuth applications need reauthorization in sandboxes.
• Deleted records, system notes, and workflow histories will not be replicated in sandbox environments.