Is your team interested in developing and testing new functionality within your HubSpot NetSuite integration without worrying about adversely affecting your live production? A sandbox environment may be right for you. Keep reading for more information on this feature available to HubSpot NetSuite integration users.
A sandbox is a safe and isolated account where you can test specific actions that do not affect your live integration. You can freely make changes without altering any production data.
In NetSuite, sandbox users access the sandbox account from the same URL they use to access their production account. In HubSpot, you can also set up a sandbox to test integrations and ensure they’re working as intended. Super admins can add them to any Enterprise software subscription by navigating to settings and selecting “Sandboxes.”
For this blog, we’ll focus on NetSuite sandboxes, but the benefits of using a sandbox in either NetSuite or HubSpot are the same.
Sandboxes have several benefits that can enhance your HubSpot NetSuite integration experience. You can use them to:
Because a sandbox is the same as your production environment, any update that runs without issue here should also work without any problems once live. A sandbox can help you feel confident in moving forward with new features, customization, or functionality.
For HubSpot NetSuite integration users, the sandbox environment is an add-on feature that is useful for companies looking to do a lot of testing. When going through SyncSmart’s implementation consultant process (one of your options when selecting a SyncSmart integration), the SyncSmart team will install the sandbox with the SyncSmart bundle in NetSuite. To access the bundle, users can go to: Customization > SuiteBundler > Search & Install Bundles > List > ~ look for “SyncSmart HubSpot <> NetSuite.”
To log in to your NetSuite sandbox account, you will need a NetSuite administrator to give you access. Sandbox account IDs are always the same as your production account, appended with _SB and the number. For example, if you have a production account ID that is 567890, your sandbox would be 567890_SB1.
Administrators can also label them something that fits your company’s naming convention. Once you’re sure you have access, head to system.sandbox.netsuite.com and log in and have fun setting up new functionality or making edits without the risk of damaging your live integration. You’ll know you’re in your sandbox environment because a logo will be visible on the top toolbar in NetSuite.
You will need to perform a sandbox refresh to bring the latest data and setups from your live integration into your sandbox so you can tinker with the most up-to-date configurations. Refreshing a sandbox account copies everything currently in your production account into the sandbox. Any changes you’ve made to your sandbox account will be overwritten during a refresh, and you cannot restore your sandbox to its initial state.
If a sandbox refresh occurs before repointing what you’ve worked on for SyncSmart to your production environment, your SyncSmart bundle will be deleted from the sandbox. This can result in increased time to re-install, so it is recommended not to do a refresh during important implementation phases.
Suppose a sandbox refresh does occur after your implementation. In that case, you will need to clear out the SyncSmart Webhook URL from your sandbox instance as the URL from production gets copied into the sandbox, resulting in a potential duplicate record being created during a sync. A SyncSmart consultant can help with this!
If you’re a HubSpot NetSuite integration user looking to ramp up operations and explore new features without risking the loss of downtime or production errors, sandboxes are a solid choice. Without them, you may damage the valuable contact and company data you need to propel your business forward. Ultimately, it’s a safe route if you’re looking to improve testing and scale.
Want to know a little more about how it works with SyncSmart? Reach out today.