Zoho CRM’s five standard modules, Leads, Contacts, Accounts, Deals and Activities, cover the standard B2B sales model well. They do not cover everything. A property management firm needs a Properties module; a staffing agency needs Placements; a software company needs Subscriptions or Support Contracts. Building those structures is what turns Zoho CRM from a generic sales tool into a system that reflects how the business operates. This guide covers how to create custom modules, which field types to use, how subforms handle repeating data, and how to relate modules. It sits in the Data Architecture & UX section of our Zoho CRM guide.
What Custom Modules Are and When You Need One
A custom module is a new record type defined inside Zoho CRM, with its own fields, list views, workflows and relationships. The clearest signal you need one is finding important data in the Notes field of a contact or deal because there is nowhere proper to put it. Notes are unstructured, unsearchable and unsortable. If the data matters to the process, if you need to report on it, filter by it or trigger automation from it, it belongs in a structured module with proper fields.
Choosing the Right Field Type
| Field type | Best for | Avoid when |
|---|
| Single-line text | Names, reference numbers, short entries | You need to filter or group by it; use a picklist |
| Picklist | Status, category, stage, type: any defined set of options | Options change often or differ per user |
| Multi-select picklist | Tags, skills, interests: records that belong to several options | You need to report by individual option |
| Currency | Revenue, deal amounts, budgets | Percentages or ratios |
| Formula | Calculated values: margin, days since contact, remaining value | Users should edit the value by hand |
| Lookup | Linking records across modules | Simple reference data that does not need a module |
| Date and DateTime | Deadlines, renewals, appointments | Durations; use a formula |
| File upload | Contracts and signed documents on a record | Large media; the CRM is not a document system |
Subforms solve a specific problem: a single record that holds several instances of the same kind of data. A deal with line items, each with product, quantity, price and discount. A contact with phone numbers in several countries. A project with milestones that have dates, status and owner. Without subforms, teams create one deal per line item or cram everything into text, and both make reporting impossible and automation unreliable. A subform keeps the data on the parent record in a structured grid you can filter and report.
Relationships Between Modules
A lookup field creates a many-to-one relationship: many Projects point to one Deal, and each side can see the other. For many-to-many relationships, where a Contact belongs to several Accounts or an Event has many Contacts, Zoho CRM uses multi-select lookups or junction modules. Map these relationships before building, because they decide which reports and automation conditions are possible later.
Module Limits by Edition
| Edition | Custom modules |
|---|
| Standard | None |
| Professional | Up to 10 |
| Enterprise | Up to 50 |
| Ultimate | Up to 50 |
| Zoho One | As Enterprise or Ultimate, by edition |
Pricing checked October 2026. These are Zoho’s published rates at the time of writing. They change over time, vary by region and currency, and may differ inside Zoho One, so confirm the current figures on the official pricing page linked above before you decide.
Map the Data Model Before You Build
- List every type of record the business manages, including the ones living in spreadsheets.
- Write the fields for each, with types, from the table above.
- Draw the relationships: which records point to which, and how many to how many.
- Mark which fields drive reports and automation; those get picklists and formulas, not text.
- Build in a sandbox or on a quiet afternoon, one module at a time, and import a sample.
This usually takes two to four hours and prevents weeks of rework. ABR runs a data architecture workshop as the first phase of every Zoho CRM implementation; for an existing build with reporting or automation problems, the Zoho Platform Assessment audits the structure and lists the changes needed.
Common Mistakes
- Free-text fields for anything that should be a picklist.
- A custom module for data that fits a subform, or a subform for data that deserves its own module.
- Building without relationships, then exporting to spreadsheets to join the data.
- Copying a competitor’s structure instead of the business’s own process.
Questions People Ask About Custom Modules & Fields
Short answers, drawn from the guide above.
How many custom modules can I create in Zoho CRM?
Up to 10 on Professional and up to 50 on Enterprise and Ultimate; Standard has none.
When should I create a custom module instead of custom fields?
When the data is a distinct record type with its own lifecycle, such as Properties or Subscriptions, rather than an attribute of an existing record.
What is a subform in Zoho CRM?
A grid of repeating entries on one record, such as line items on a deal or milestones on a project, kept structured and reportable.
How do I link records between modules?
With lookup fields for many-to-one relationships, and multi-select lookups or junction modules for many-to-many.
Which field type should I use for a status?
A picklist. Free text cannot be filtered, grouped or used in automation reliably.
Does ABR help design the data model?
Yes. A data architecture workshop is the first phase of every ABR implementation, and existing structures can be audited through the Zoho Platform Assessment.
{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How many custom modules can I create in Zoho CRM?","acceptedAnswer":{"@type":"Answer","text":"Up to 10 on Professional and up to 50 on Enterprise and Ultimate; Standard has none."}},{"@type":"Question","name":"When should I create a custom module instead of custom fields?","acceptedAnswer":{"@type":"Answer","text":"When the data is a distinct record type with its own lifecycle, such as Properties or Subscriptions, rather than an attribute of an existing record."}},{"@type":"Question","name":"What is a subform in Zoho CRM?","acceptedAnswer":{"@type":"Answer","text":"A grid of repeating entries on one record, such as line items on a deal or milestones on a project, kept structured and reportable."}},{"@type":"Question","name":"How do I link records between modules?","acceptedAnswer":{"@type":"Answer","text":"With lookup fields for many-to-one relationships, and multi-select lookups or junction modules for many-to-many."}},{"@type":"Question","name":"Which field type should I use for a status?","acceptedAnswer":{"@type":"Answer","text":"A picklist. Free text cannot be filtered, grouped or used in automation reliably."}},{"@type":"Question","name":"Does ABR help design the data model?","acceptedAnswer":{"@type":"Answer","text":"Yes. A data architecture workshop is the first phase of every ABR implementation, and existing structures can be audited through the Zoho Platform Assessment."}}]}