Item: Copado
Rating: 10
Author: Verified User

Overall Satisfaction with Copado

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 and Cons

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

very good user interface. It has reduced tons of manual efforts for the developers. Very easy to validate the release work. Easy to club multiple stories into one deployment. We can integrate Copado with our JIRA and all the PR’s are visible under the user story on JIRA board. But this can be overwhelming for beginners

Key Insights

Do you think Copado delivers good value for the price?

Yes

Are you happy with Copado's feature set?

Yes

Did Copado live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Copado go as expected?

Yes

Would you buy Copado again?

Yes

Other Software Used

Bringg, Five9, Odaseva, Snowflake, Atlassian Confluence, Atlassian Jira

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

Comments

Please log in to join the conversation

Copado - A solid DevOps environment for Salesforce