Custom CRM modules are the correct tool when: the data you are adding logically belongs in the sales and client management context, the users interacting with the data are internal CRM users, the interface provided by standard CRM module views is adequate and the automation you need can be handled by workflow rules, blueprints and cadences.
An Engagements module for a professional services firm — tracking individual consulting projects linked to their CRM account records — fits this description. The data belongs in the CRM context, the consultants using it are CRM users, the standard module interface is functional and the automation (task creation when an engagement is created, notifications when a milestone date approaches) fits within standard workflow rules.
The most common reason to use Creator instead of a custom CRM module is external access. CRM modules are only accessible to users with a Zoho CRM licence — internal staff. If clients, partners or contractors need to view or update data in the relevant module, a CRM module cannot provide that access. A Creator application with a portal component can.
A client portal that lets clients view the status of their projects, submit change requests and download completed deliverables requires Creator. That same data, managed internally by the team, could live in a custom CRM module — but the client-facing layer must be Creator or a separate custom software application.
Zoho CRM’s data model is designed for the standard CRM relationship structure: Accounts have many Contacts, Contacts have many Deals, Deals have Activities. Custom modules extend this model but remain within its conventions. When a data model requires many-to-many relationships, hierarchical structures that span more than two levels or data objects that relate to multiple standard modules simultaneously, Creator’s more flexible data modelling is more appropriate.
An inventory management requirement — where products relate to multiple suppliers, multiple warehouse locations and multiple client orders simultaneously — is better represented in a Creator app with a purpose-built data model than in a set of custom CRM modules that strain the CRM relationship conventions.
Standard CRM module views — list views, detail views, related lists — are functional and configurable with Canvas Builder. They are not fully customisable interfaces. When a user experience requirement goes beyond what Canvas Builder can produce — a guided multi-step data entry wizard, a map-based view showing records by geographic location, a custom calendar interface tailored to a specific workflow — Creator provides the interface flexibility that CRM module views cannot.
The most effective architecture for many businesses is a combination: standard CRM modules handling the sales and client relationship data, and a Creator app handling the operational process data that connects to it. The CRM is the system of record for commercial relationships. Creator is the operational layer for the processes that depend on those relationships.
A facilities management company might use standard Zoho CRM for their sales pipeline and account management, and a Creator job management app for their field operations — with the Creator app reading client and account data from Zoho CRM and writing job completion data back to CRM records. Each tool does what it does best, and Deluge scripting connects them seamlessly.
For help designing the right architecture for your specific data model and process requirements, the ABR consulting team can scope both the CRM configuration and Creator development components.
| // Creator Deluge: write job completion data back to linked CRM Account // Trigger: when Creator job record is marked “Complete” crmAccountId = input.CRM_Account_ID; // lookup field on Creator job record // Update the CRM Account’s last service date and job count updateMap = Map(); updateMap.put(“Last_Service_Date”, input.Completion_Date); updateMap.put(“Total_Jobs_Completed”, zoho.crm.getRecordById(“Accounts”, crmAccountId).get(“Total_Jobs_Completed”) + 1); zoho.crm.updateRecord(“Accounts”, crmAccountId, updateMap); |
|---|
What is the difference between a Zoho CRM custom module and a Zoho Creator module?
When should I build a custom module in Zoho Creator instead of Zoho CRM?
Can a Zoho Creator module sync data with Zoho CRM?
How long does it take to build a custom CRM module in Zoho Creator?
Can ABR build a custom CRM module in Zoho Creator for us?