Copper is a customer relationship management (CRM) built as an integration into Google Apps.
$12
per month per user
Drupal
Score 7.0 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Pricing
Copper CRM
Drupal
Editions & Modules
Starter - Paid Annually
$9.00
per month per user
Basic - Paid Annually
$23.00
per month per user
Professional - Paid Annually
$59.00
per month per user
Business - Paid Annually
$99.00
per month per user
No answers on this topic
Offerings
Pricing Offerings
Copper
Drupal
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Up to 15% discount for annual pricing.
—
More Pricing Information
Community Pulse
Copper CRM
Drupal
Features
Copper CRM
Drupal
Sales Force Automation
Comparison of Sales Force Automation features of Product A and Product B
Copper CRM
5.2
54 Ratings
40% below category average
Drupal
-
Ratings
Customer data management / contact management
7.253 Ratings
00 Ratings
Workflow management
6.551 Ratings
00 Ratings
Territory management
5.04 Ratings
00 Ratings
Opportunity management
8.150 Ratings
00 Ratings
Integration with email client (e.g., Outlook or Gmail)
6.454 Ratings
00 Ratings
Contract management
5.29 Ratings
00 Ratings
Quote & order management
2.07 Ratings
00 Ratings
Interaction tracking
5.350 Ratings
00 Ratings
Channel / partner relationship management
1.07 Ratings
00 Ratings
Customer Service & Support
Comparison of Customer Service & Support features of Product A and Product B
Copper CRM
1.4
10 Ratings
138% below category average
Drupal
-
Ratings
Case management
1.29 Ratings
00 Ratings
Call center management
1.55 Ratings
00 Ratings
Help desk management
1.67 Ratings
00 Ratings
Marketing Automation
Comparison of Marketing Automation features of Product A and Product B
Copper CRM
5.7
41 Ratings
31% below category average
Drupal
-
Ratings
Lead management
7.038 Ratings
00 Ratings
Email marketing
4.431 Ratings
00 Ratings
CRM Project Management
Comparison of CRM Project Management features of Product A and Product B
Copper CRM
5.4
52 Ratings
35% below category average
Drupal
-
Ratings
Task management
7.850 Ratings
00 Ratings
Billing and invoicing management
1.75 Ratings
00 Ratings
Reporting
6.746 Ratings
00 Ratings
CRM Reporting & Analytics
Comparison of CRM Reporting & Analytics features of Product A and Product B
Copper CRM
7.0
48 Ratings
9% below category average
Drupal
-
Ratings
Forecasting
6.432 Ratings
00 Ratings
Pipeline visualization
8.045 Ratings
00 Ratings
Customizable reports
6.540 Ratings
00 Ratings
Customization
Comparison of Customization features of Product A and Product B
Copper CRM
4.3
51 Ratings
56% below category average
Drupal
-
Ratings
Custom fields
6.850 Ratings
00 Ratings
Custom objects
3.412 Ratings
00 Ratings
Scripting environment
4.13 Ratings
00 Ratings
API for custom integration
3.232 Ratings
00 Ratings
Security
Comparison of Security features of Product A and Product B
Copper CRM
8.1
42 Ratings
4% below category average
Drupal
8.1
74 Ratings
1% below category average
Single sign-on capability
8.712 Ratings
00 Ratings
Role-based user permissions
7.441 Ratings
8.174 Ratings
Social CRM
Comparison of Social CRM features of Product A and Product B
Copper CRM
2.0
12 Ratings
115% below category average
Drupal
-
Ratings
Social data
2.012 Ratings
00 Ratings
Social engagement
2.07 Ratings
00 Ratings
Integrations with 3rd-party Software
Comparison of Integrations with 3rd-party Software features of Product A and Product B
Copper CRM
2.4
33 Ratings
103% below category average
Drupal
-
Ratings
Marketing automation
3.933 Ratings
00 Ratings
Compensation management
1.01 Ratings
00 Ratings
Platform
Comparison of Platform features of Product A and Product B
Copper CRM
8.4
43 Ratings
10% above category average
Drupal
-
Ratings
Mobile access
8.443 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Copper CRM
-
Ratings
Drupal
7.7
69 Ratings
1% below category average
API
00 Ratings
7.264 Ratings
Internationalization / multi-language
00 Ratings
8.160 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Copper CRM
-
Ratings
Drupal
6.5
78 Ratings
18% below category average
WYSIWYG editor
00 Ratings
6.271 Ratings
Code quality / cleanliness
00 Ratings
8.175 Ratings
Admin section
00 Ratings
6.878 Ratings
Page templates
00 Ratings
5.577 Ratings
Library of website themes
00 Ratings
5.568 Ratings
Mobile optimization / responsive design
00 Ratings
6.572 Ratings
Publishing workflow
00 Ratings
6.776 Ratings
Form generator
00 Ratings
6.472 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
If you need to track contract expiration dates of your clients or your prospects that you're trying to sell - Copper is your tool. If you want to track specific products, solutions, vendors, etc. Copper can do it. I use it to track many brands of IT products and services with the use of custom fields to track which prospects/clients have any number of these items. Rather than taking notes, I can select the product from a drop down list that I created VERY EASILY within Copper.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
Allows for contacts to be synced and organized directly from Gmail.
Gives a flexible style and customizable settings to match our company's specific needs.
Does a great job of helping us keep track of projects. We easily created a customized "Status" field with several status options that help us update the many phases of our project.
Window change: for mobile - when you tap on a card from a pipeline it takes you to the lead’s basic info. I wish it would immediately just open all activities so I can quick see notes
I usually use Copper on the go. When you open the Copper app, it immediately opens a collab window. I wish it had some sort of easy dashboard….plus a notes area. I open Copper on mobile to quickly search for someone’s name or to take quick notes from a sales meeting
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
Copper is simple to use and it's simple to figure out the additional functionality you may need or want to use. There are a lot of support articles and the support itself is great. But it's also fairly simple to figure out on your own. It integrates easily with Google Workspace as well.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
There have been a few times when I contacted the "help desk" or "support team" and they just told me to watch a video or join a seminar to learn what I am looking to do. I would have expected someone to take a few minutes and literally walk me through the steps one by one until either I figured it out or accomplished the goal of my request.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
We selected Copper over these other CRMs mainly because of its ability to integrate with Google Workspace. Members of our team have used Salesforce in the past and found it to be a nightmare to work with/on. Candidly, Copper doesn't fill all of our needs so we supplement that with the use of Asana.
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.