Copado - A solid DevOps environment for Salesforce
Use Cases and Deployment Scope
We use it for deploying our work in multiple orgs across the company. Used it for migrating data between two completely different orgs ( Sales & Service) by creating data templates. Used it for metadata deployments as well to migrate all the layouts, fields, validation rules etc. We use it as our CI/CD pipleline manily
Pros
- Capturing latest changes accurately in the commit window
- Auto resolving conflicts
- gate checks for apex code coverage.
- Giving insights into the validation errors
- very easy to migrate data & metadata between orgs, just with few clicks
Cons
- For data migration, they can increase the limitations
- The table of components in the build section can be improved
- Hard to understand how to destructive changes. Sometimes facing issued after deleting the field or component that need to be deleted with destructive changes
Return on Investment
- biggest positive impact is speed and consistency of our releases. With all the git operations managed by its own. Very easy to maintain. Easy to track all the changes within the Copado org. Before we used to track down everything on excel sheet
- Very helpful with the mass back promotions. Before we used to refresh our sandboxes and some projects which are not ready were wiped off and we had take backups and then build them again. with the back promotions, our life became very easy
- only negative is with the team size growing, we need to buy more licenses. This doesn’t fall under the devops process that our company has. It is in a siloed environment.
Usability
Other Software Used
Bringg, Five9, Odaseva, Snowflake, Atlassian Confluence, Atlassian Jira

