Deploying sandbox changes to production
- Create a blueprint, simulate a process, and deploy it to the parent CRM account without making any changes to the live environment until everything is running smoothly.
- As an admin, you can change the organization's hierarchy to test the behavior of the CRM data, check whether the data sharing properties in the organization are affected, and deploy only the changes you need to the parent account.
View Changes before deployment
- Components and items: Shows all the changes made (items) for each feature (component). For example, if a group is created in the sandbox, then Group will be the component and the name you entered for that group in the sandbox will be the item.
- Record type: Shows which module the changes were made in.
- Actions: Shows whether the items were added, updated, or deleted.
- Users: Shows who made the changes.
- Date: Shows when the changes were made.
- Linked: Shows other items associated with the selected item. For example, in the screenshot below, the link icon shows that the Pacific Contacts layout is associated with the changed item Secondary Contact.
Types of deployment
- Complete Deployment: All the components or items listed in the change set will be deployed.
- Partial Deployment: Only specific components or items that you select in the change set will be deployed.
Deploy changes to production
- If your changes are Qualified, there will not be any issues when the changes are deployed in the production setup.
- If your changes are Conflicted, you cannot proceed with the deployment as the changes may cause issues like overriding names, missing parent items, or exceeding feature limit.
- Go to Setup > Data Administration > Sandbox.
- Click on the sandbox you want to deploy.
- In the Change Set list, select the changes you want to deploy.
- If you want to deploy all changes to production, select the checkbox at the left of Components and item header and click Deploy Changes to Production button.
- If you want to deploy the changes partially, select the checkbox of the specific components and click the Deploy Changes to Production button.
- View the details of all the qualified and conflicted changes on the Start Deployment page, rectify any conflicts, and click the Yes, Proceed button.
Points to remember:
1. You can deploy the following configurations for production from the sandbox account:
- Profiles
- Roles
- Data Sharing Settings
- Groups
- Multi-currency
- Territory Management
- Automation
- Customization
- Templates
- Custom Schedules
- Webforms
- Auto Response Rules
- Workflow Rules
- Blueprint
- Translations
- Wizards
- Tags
- Map Dependency Fields
Note: Changes made to Translations will sometimes reflect inside production account in a delayed manner depending on the file size.
2. However, Sandbox currently does not support Scoring Rules.
3. Sandbox allows you to test what happens not only when you add new configurations, but also when you edit or delete an existing configuration.
4. Emails sent from the Sandbox environment will not be delivered to the recipients, it is only for the testing purpose.
5. Emails triggered through Workflow Rules or Blueprints will not be delivered to the recipients, however, these emails will be displayed in the Email related list of the record.
6. Data cannot be migrated to Sandbox from other CRM sources You can however, import records or populate sample data or selected number of records from the live CRM account to specific modules.
7. Updating a field in sandbox and deploying the changes to production will overwrite the existing field properties. For example, if the email field is marked as "mandatory" in sandbox and as "unique field" in production. Then, after deployment the field property will be overwritten to mandatory.
8. To know whether you are working on the Sandbox environment or production setup, look out for a bright orange Sandbox ribbon. This is used to differentiate Sandbox from your production setup.
9. Sandbox is used to test and validate configurations before they are moved onto the production account, therefore, records populated, imported or manually added to the Sandbox account cannot be deployed to production.
Track the deployed changes
The date of the deployment
The name of the sandbox environment the changes were deployed from
The changes that were deployed
The user who deployed the changes
- In Sandbox, if any configuration is assigned or associated with a Developer, then the changes can't be deployed to the production account.
Say an assignment rule configured is in Sandbox such that the records that match the criteria will be assigned to the Developer. In that case, a conflict will be displayed while deploying the changes to the production account. The user should be changed in order to deploy the changes
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
Still can't find what you're looking for?
Write to us: support@zohoforms.com
Zoho Sheet Resources
Zoho Forms Resources
Zoho Sign Resources
Sign, Paperless!
Zoho SalesIQ Resources
Zoho TeamInbox Resources
Zoho DataPrep Resources
Design. Discuss. Deliver.
Related Articles
Creating Sandbox
Creating sandbox account CRM admins can create multiple sandboxes in one account to test different configurations independently. While creating a sandbox you need to do the following: 1. Choose the sandbox type: There are two types of sandboxes to ...Sandbox Overview
As your organization grows so does the complexity in your sales processes. At such a juncture, any small error in a process could have a domino effect. No organization can afford such a situation. To help overcome this hassle, Zoho CRM offers ...Working with Sandbox
Rebuilding a sandbox Note: Rebuild was earlier referred to as refresh When your Sandbox setup is not in sync with the Production setup, any testing that you conduct in Sandbox will not be relevant when deployed to production. So it is important that ...Using multi-org feature I am unable to create a sandbox account, why is that?
The possible reasons for not been able to create Sandbox account could be: You may not have create permission in the production CRM org. You are already part of 10 sandbox orgs. You are already super admin in 5 sandbox orgs.Will Canvas Builder be available in Sandbox to design and test before pushing to production?
This is a part of our roadmap and we will make this available soon.