Q1) What are the advantages / disadvantages of using a sandbox vs. implementing the Connector directly into our Production Salesforce and NetSuite environments?
A1) Using a sandbox reduces risk and people tend to do more testing. You do not need to keep track of test data you create. If both sides are sandbox, there is no risk of the test data affecting your financial records. It is a recommended best practice. However, it increases the cost. It can also increase the timeline.
Q2) What is the alternative to use sandboxes?
A2) Using your production systems with “Test Mode”. This reduces the risk by only syncing over specific records that you flag specifically to be seen by the Connector.
Q3) Are there any testing complications if we use sandboxes?
A3) Test Mode has an extra complication when you test the Celigo flows that work with NetSuite Contract Renewals. Also, Salesforce creates pseudo e-mail addresses in the sandbox environment. This is something to keep in mind when testing a flow which syncs Salesforce owner to NetSuite salesrep, since the Connector uses the e-mails to associate these two fields.
Q4) What costs are involved for a sandbox implementation?
A4) You would need to purchase the sandbox(es) from Salesforce and/or NetSuite. You would also need a perpetual sandbox or temporary sandbox agreement with Celigo.
Q5) What do we need to do beside requisitioning the Salesforce and/or NetSuite sandboxes?
A5) The sandbox(es) need to be set up. Typically this means installing the Salesforce or NetSuite software. It could also mean refreshing the sandbox with the data in your Salesforce / NetSuite Production systems. Please work with Salesforce and/or NetSuite on these steps.
Q6) Tell me more about perpetual sandbox or temporary sandbox agreements with Celigo.
A6) For the Salesforce-NetSuite Connector, you can use:
- Salesforce Production or Salesforce Sandbox.
- NetSuite Production or NetSuite Sandbox.
If you want to use your Salesforce Sandbox and your NetSuite Sandbox, the next questions are:
- Do you want the Salesforce-NetSuite Connector to be installed/configured in the sandbox-to-sandbox environment temporarily (until the Connector is moved into production)?
- Or, do you want to continue to have the Connector available perpetually, even after the project is closed?
What Celigo calls a “perpetual sandbox agreement” is a second copy of the Connector. It’s a subscription, which would be co-termed with your production Salesforce-NetSuite Connector subscription.
What Celigo calls a “temporary sandbox agreement” is additional scope added to the project.
Q7) Can we use sandbox for one application and production on the other side?
A7) Yes, we call this a “mixed-mode” implementation. This is possible via a temporary sandbox configuration. After User Acceptance Testing (UAT), when you ready to move the Connector to production, the Connector will be switched so that it links both Production systems.
Q8) Other than the initial creation of the sandboxes, are there any other sandbox-related tasks that would affect our project timeline?
A8) There could be. If the sandbox is refreshed mid-project, that means that the production data and configuration over-writes the set up in sandbox. Therefore, Celigo asks for one week’s advanced notice of a sandbox refresh, so that we can prepare. In addition, after the refresh, there is some re-work to do. Also, moving to production is an extra step that is not needed in an implementation which starts in a production-to-production environment.