What is a custom module in Zoho CRM?
A custom module is a new tab you design yourself, with its own records, layout, fields, permissions, list views and reports. It sits beside the standard modules and links to them through lookup fields, so a Property, a Vehicle or a Service visit can belong to an Account the same way a Deal does.
Zoho CRM ships with modules for the common sales objects: Leads, Contacts, Accounts, Deals, Activities, Products, Quotes and a few more. They cover the selling part of most businesses. What they do not cover is the thing your business is actually about. A property manager has units. An equipment dealer has serial-numbered machines. A training company has cohorts. Those objects deserve records of their own once you need to track more than one of them per customer.
Custom module or custom field: how do you decide?
Ask whether the thing can exist more than once per customer and whether it changes on its own schedule. If yes to either, it is a module. If it is a single value that describes a record you already have, it is a field.
We use four questions in workflow mapping sessions. Two or more yes answers point to a module.
- Can one customer have several of them? Three locations, ten machines, twelve policies. A field holds one value; a module holds as many records as you need.
- Does it need its own owner or status? If a technician owns the service visit while a salesperson owns the account, those are two records.
- Will someone report on it directly? "How many units are vacant this month" is a report on units, which needs units as records.
- Does it outlive the deal? A contract that renews for years should not vanish into a closed deal’s fields.
If all four answers are no, add a field. Fields are cheaper to build, easier to import into and simpler for your team to learn. A dropdown for "Contract term" on the Deal is better than a whole Contracts module nobody opens.
What does a good module map look like?
A short one. Keep the standard modules doing the selling, add custom modules only for the objects your operation runs on, and draw every lookup before anyone builds a field.
Standard moduleCustom moduleLookup field
Read the map from the bottom up. A service visit belongs to one machine, the machine sits at one site, the site belongs to one customer. Because each step is a lookup, the Account page shows every site, machine and visit in its related lists, and a technician opening a visit sees the full chain without searching. Notice what did not become a module: contract term is a field on the Deal, and the parts used on a visit are subform lines.
What are the custom module limits in each Zoho CRM edition?
On Zoho’s US price list, custom modules come with Enterprise (up to 100, at 2 per user license) and Ultimate (up to 500, at 5 per user license). Standard and Professional have custom fields but no custom modules.
| Edition | Per user / month, yearly | Custom fields per module | Custom modules | Subforms | Validation rules |
|---|---|---|---|---|---|
| Standard | $14 | 10 | None | No | No |
| Professional | $23 | 155 | None | No | 5 per layout |
| Enterprise | $40 | 300 | Up to 100 (2 per user license) | Yes | 10 per layout |
| Ultimate | $52 | 500 | Up to 500 (5 per user license) | Yes | 25 per layout |
The per-license rule matters for small teams. A 10-user Enterprise account can create 20 custom modules, not 100, which is plenty for most companies and a useful brake on sprawl. Billed monthly, the same editions cost $20, $35, $50 and $65 per user. The free edition for up to three users has no custom fields or modules at all. Zoho revises these limits from time to time, so we confirm them again on the day we scope your build. The full edition breakdown is on our Zoho CRM page.
How do custom modules connect to the rest of Zoho CRM?
Through lookup fields, which create the related lists you see on each record. Once linked, a custom module behaves like a standard one: workflow rules, Blueprint, reports, imports and permissions all work on it.
Three connections do most of the work:
- Lookups. A lookup on Equipment pointing to Sites puts a "Equipment" list on every site. Plan the direction carefully: the child holds the lookup, the parent shows the list.
- Automation. A workflow rule can create a Service visit when a machine’s next service date arrives, or alert the account owner when a site changes status. Blueprint can guide a visit from scheduled to completed.
- Reports. Because the records are linked, a report can start from Service visits and pull in fields from Equipment and Accounts, so "visits per customer this quarter" is one report, not a spreadsheet.
Custom modules also fit into the wider Zoho stack. When a process outgrows CRM entirely, with complex forms, offline field use or its own portal, a Zoho Creator app linked to CRM can be the better home.
What mistakes should you avoid with custom modules?
The common ones are building a module for every request, copying a standard module under a new name, and adding fields per year or per product instead of records.
- Rebuilding Accounts as "Clients". You lose the built-in links to Deals, Quotes and email. Every edition lets you rename tabs, so rename the standard module instead.
- Fields named "2025 renewal", "2026 renewal". Repeating fields are a sign the thing wants to be a module with one record per year.
- A module nobody owns. Each custom module needs an owner on your side who decides what its fields mean and who cleans it.
- Importing before mapping. Moving data into a structure you have not drawn means moving it twice. Map first, then import.
- Too many picklist values left as free text. If you will filter or report on a value, make it a dropdown from day one.
How do we set up custom modules for a client?
We draw the module map with your team, agree it in writing, then build and test it in a sandbox before your data arrives.
The map comes out of workflow mapping, the second step of our process. Every module, field, lookup and automation goes into the BRD you sign, together with a fixed price for building them. Enterprise and Ultimate accounts also include a sandbox, so we can test the new structure on copies before it touches live records. The full sequence is on How we work, and our Zoho customization service covers the deeper work: functions, widgets and custom buttons.
