Copado Reviews and Ratings

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

Likelihood to Recommend

Very well suited if there are 3+ developers in the team. Very easy to maintain individual sandboxes and connect it to the pipeline. With just few clicks, it will create its git branches on its own and syncs with the sandboxes. Very helpful and time saving.

might be expensive for small teams

Use Cases and Deployment Scope

The Salesforce team used it for Data and Metadata deployments between Salesforce Instances. The development team will build a package and then run that package through to the second sandbox for testing. From there the Copado package goes to an administration team who move it into our third sandbox for testing, then to a sandbox used for user acceptance training. Finally, the package is deployed by the administration team into production.

Likelihood to Recommend

From my experience, Copado is a solid deployment tool. We used the query option for most deployments which is very helpful when moving Salesforce CPQ Data. Storing and reusing queries was the best bet. So long as the query didn't get lost when editing or deleted somehow things worked great. The deployment steps weren't extremely intuitive, and overall it takes a bit to get familiar with, but it is a capable tool for deployments.

Use Cases and Deployment Scope

At earlier times we use different ways to deploy the changes to the next org such as using the ANT migration tool, SFDX or changesets but now Copado is a managed package provided which will handle all the deployments stage by stage in a very organized way. We don't need to create package.xml files like earlier we do. We have to just select the metadata we want to push or deploy to the next org. All the credentials will be saved by the maintenance org and we can deploy the changes directly using the credentials. In a project, we do have multiple user stories created for development or for enhancement purposes those can be directly synced with Copado. Git operations can be performed from a specific feature branch to the main branch. People who don't have much knowledge of creating package.xml and how to deploy the changes Copado has made the deployments super easy in a few clicks. This gives more clarity to the client as well as about the pull request created and what is the stage of deployment. Overall it serves the deployment purpose very well within a few clicks.

Likelihood to Recommend

When we have a large organization and number of changes and deployments are more than we should go for Copado. As we know it is a paid managed package and the cost is high so for dealing with fewer deployments it is not preferable to buy. Copado is well suited for users who don't have much technical understanding. So those users can see the User interface select the changes that need to be deployed by selecting the metadata. From Git operation to deployment all is handled by Copado itself. Copado has reduced the efforts for creating the package.xml and direct deployments can be done within a few clicks. Another Major aspect is that it can be directly synced with Jira or Azzure board from where the user stories will be synced and actions can be performed accordingly. For small organization, Copado can be expensive and to set up and maintain we need a technical person to do so.