Leveraging Sandbox for CFM: Deep Dive
Updated
The Sandbox Support feature allows users to test survey projects comprehensively in a dedicated testing environment before moving them to the live environment. This ensures the surveys’ accuracy, distribution effectiveness, and alignment with organisational requirements.
With Sandbox, users can simulate the entire survey process, including distributions, and make necessary adjustments in a risk-free environment.

Business Use Cases
Sandbox here helps in eliminating the risk of error and ensures seamless distribution of surveys.
Setting Up
Sandbox support comes with general availability for all clients.

Set up a user for sandbox environment and add permissions as mentioned above in this article.
Login to the environment with user credentials.
How to use it?
Create a program followed by a survey in sandbox environment.
Setup the survey as you would have done in production environment.
Once setup, you can distribute the survey to check following survey components.
Survey look and feel.
Survey view in different devices/screen sizes.
Survey modes- normal and presentation.
Themes- OOTB and Custom.

Distribution channels.
Anonymous link.
Email distribution.
Social media distribution.
QR Code.
SMS and WhatsApp distributions.
Website and In-app surveys.
Personalised links.
Response collection.
Survey analytics- basic and custom.
Automations.
Quotas.

During this process, check for support of following entities as well.
Profiles
Profile lists
Samples
Segments
Transactions
Transaction Fields
Response Custom Fields
Profile Custom Fields
Creatives
Roles
Users
Custom Dashboards
Accounts
Once the survey testing is complete, the survey project can be migrated to production environment. Next few steps will guide us how to do so.
Go to Platform Settings. Access sandbox manager from left menu.

Since we are moving asset from the environment we are in, select Outbound Change Sets.

Click on create new on top-right to create a new outbound change set.
Provide the name, description, and tags, then choose the action type.
Action type can be selected based on the requirement.
Update if exists: New object(s) get created and existing object(s) get updated.
Skip if exists: Only new object(s) will be created. Any existing object(s) with same ID in the destination will be skipped during deployment.
User selected updates only: Only new object(s) get created and user selected object(s) get updated. Any dependent entity, if it exists, gets skipped in the destination.
Select the destination environment and then select the entities to transfer. In our case, this will be “CFM Projects”.
Use filters to search for the survey(s) to be shared.
Select the desired survey(s) from preview and click on save. Outbound change sets record manager reappear.
Now, switch to destination environment. Open sandbox manager there and select inbound change sets this time.
Recently created outbound change set in Sandbox environment will appear at the top.
From the Veritical Ellipsis on the left of outbound change set title, select deploy. Check the status to confirm deployment.

Access the Programs record manager within the CFM app to find your survey.
Key points to note
No data migration.
Deployment of assets in destination environment may take some time.
Best Practices
Replicate all steps in sandbox environment as you would have done in production environment.