Bring relationship records and sales operations together in a CRM you control, with an explicit plan for the Google Workspace experience your team relies on.
MIT open source
1,928 stars on GitHub
50+ pluginsCopper ties contact allowances, workflows and custom reporting to its subscription levels. Assess your actual needs alongside an Open Mercato deployment whose data model and core licence are under your control.
Copper is built around convenient relationship management. When contracts, deliveries or industry records need their own screens, an owned application gives your team room to build those workflows.
Map People, Companies, Leads, Opportunities, Projects, custom fields and linked activities. Rehearse the relationships and daily workflow with a representative sample before committing to the cutover.
Link companies and people to deals, addresses, notes and activities. Extend the records with fields that describe your business.
Configure stages and track deal value, probability, expected close and ownership in board or list views.
Use the sales and catalog modules for quotes, orders, products, payments and shipment records. Implement the handoffs and provider connections your process needs.
Extend the TypeScript application with your own entities, modules and workflows. Assess Gmail extensions, Google Calendar, email history, enrichment and reporting as explicit migration work.
Green checks show available capabilities in the stated scope. Arrows identify implementation work, including the specialist features your team may need to retain.
| What your team gets | BUILT FOR YOUR WORKFLOWOpen MercatoCore CRM + configurable modules | CopperContacts and reporting: plan dependent |
|---|---|---|
| Where Open Mercato adds control | ||
| Run on your own infrastructure | ✓ | ×Vendor-hosted service |
| Application core under an MIT licence | ✓ | ×Commercial licence |
| No per-user core licence fee for self-hosting | ✓Hosting and services extra | ×Commercial licence / hosted service |
| Capabilities available in both | ||
| Company and contact records | ✓ | ✓ |
| Deals and sales pipelines | ✓ | ✓ |
| Notes and activities | ✓ | ✓ |
| Custom fields | ✓ | ✓Edition / plan scope applies |
| Business-specific automation | ✓Configure the workflow engine | ✓Capabilities vary by edition |
| Implementation and scope | ||
| Copper Gmail and Google Workspace experience | ↗Assess and connect required services | ✓Within product / plan scope |
| Your custom migration and data mapping | ↗Scoped pilot and validation | ↗Export and integration work |
Selected CRM capabilities; availability varies by plan. Open Mercato integrations, specialized reporting, implementation, hosting and maintenance are scoped separately. This is not a claim of complete product parity.
Reviewed 12 November 2026. Sources: Copper product documentation · Open Mercato core · Customer records
| What matters | Copper | Open Mercato |
|---|---|---|
| Customer records | Copper provides CRM records and sales processes. | Companies, people, deals, notes and activities in the core application. |
| Customization | Contacts and reporting: plan dependent. Existing configurations need a capability review. | Custom fields, entities and TypeScript modules; implementation scoped to the workflow. |
| Operational handoff | Review the modules and connected systems used after a sale. | Sales and catalog modules provide a starting point for quotes, orders and shipment records. |
| Hosting and cost | Commercial plans; check the edition and hosting model. | MIT-licensed core; hosting, implementation, maintenance and third-party usage budgeted separately. |
| Migration detail | Gmail extensions, google calendar, email history, enrichment and reporting. | Keep source identifiers, verify relationships and rebuild required behavior in a tested pilot. |
Explore customer records, deals, custom fields and configurable workflows in Open Mercato CRM. Then bring an example from Copper: one account, its related records and the next operational step your team needs.
Explore Open Mercato CRM ↗
Inventory People, Companies, Leads, Opportunities, Projects, custom fields and linked activities. Keep original identifiers and agree how each record maps to the new application.
Review Gmail extensions, Google Calendar, email history, enrichment and reporting. Decide what to retain, integrate or reimplement and agree acceptance criteria.
Load a representative sample, validate permissions and relationships, and test a real customer journey from first activity to the operational handoff.
Compare record counts and key totals, retain an accessible archive where needed, handle final changes and agree rollback, training and support ownership.
When you need an owned, extensible CRM and operational application, and have a team or partner to implement and run it. Copper can remain the better fit when its ready-to-use managed experience already matches your requirements.
No automatic feature transfer is assumed. Review Gmail extensions, Google Calendar, email history, enrichment and reporting. The core provides CRM and sales modules; specialized capabilities require configuration, integrations or development.
Compare the same scope over the same period: current subscriptions and administration versus implementation, migration, hosting, maintenance, support and provider usage. The MIT core has no licence charge; a production service still has costs.
Yes, a phased architecture can be scoped. Define the system of record for each entity, the synchronization rules and failure handling, then validate them before moving users.
Start with your record map, required integrations and the three changes that would make the biggest difference to your team.
Talk through your process, integrations and implementation needs with the Open Mercato team.