Connect customer relationships to a custom delivery process, with an owned application foundation for the workflows that make your business different.
MIT open source
1,928 stars on GitHub
50+ pluginsNutshell documents different pipeline, automation and customization allowances across its Sales Suite plans. If the required tier exceeds your needs elsewhere, compare a focused implementation on Open Mercato.
A sales lead is not the same as a contract, asset or service location. Extend Open Mercato with the business entities and handoffs your team needs after a deal is agreed.
Map People, Companies, Leads, pipelines, stages, activities, tags and custom fields. 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 sales automation, Scheduler, email sequences, marketing audiences 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 | NutshellSales Suite; 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 | ||
| Nutshell scheduling and engagement tools | ↗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: Nutshell product documentation · Open Mercato core · Customer records
| What matters | Nutshell | Open Mercato |
|---|---|---|
| Customer records | Nutshell provides CRM records and sales processes. | Companies, people, deals, notes and activities in the core application. |
| Customization | Sales Suite; 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 | Sales automation, scheduler, email sequences, marketing audiences 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 Nutshell: one account, its related records and the next operational step your team needs.
Explore Open Mercato CRM ↗
Inventory People, Companies, Leads, pipelines, stages, activities, tags and custom fields. Keep original identifiers and agree how each record maps to the new application.
Review sales automation, Scheduler, email sequences, marketing audiences 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. Nutshell can remain the better fit when its ready-to-use managed experience already matches your requirements.
No automatic feature transfer is assumed. Review sales automation, Scheduler, email sequences, marketing audiences 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.