By Alpit Patel and the aibrevo team · October 21, 2026 · 13 min read
What Is Blueprint in Zoho CRM?
Quick answer
Blueprint is Zoho CRM's process builder. You draw a sales or service process as states and transitions, and each transition can require fields, checklists, notes and approvals before a record moves on. It starts on the Professional edition.
Key takeaways
- Blueprint is Zoho CRM's process builder. A state is a stage of the process, a transition is the step that moves a record between two states, and each transition can require fields, checklists, notes and validations first.
- Zoho's feature list shows Blueprint from the Professional edition: 3 blueprints, 10 transitions per blueprint and 2 common transitions. Enterprise raises that to 50, 100 and 10, and Ultimate to 100, 300 and 25.
- Once a record enters a blueprint, the field it runs on (Stage on Deals, for example) is locked to manual edits until the blueprint finishes. Only a short list of channels, including the Transition API and workflow field updates, can change it.
- A common transition is available from every state (Deal Lost is Zoho's example). A parallel transition puts several checks side by side between two states, and all of them must be done before the record moves on.
- An SLA caps how long a record may sit in a state and fires an escalation. Custom SLA actions need Enterprise or above.
Your reps say a deal is in Negotiation, nobody can tell whether the discount was approved, and the Stage field gets edited by hand whenever someone is in a hurry. Blueprint is Zoho CRM’s answer to that: you draw the process once, and the CRM refuses to move a record until the required steps are done.
What is Blueprint in Zoho CRM?
Blueprint is the Zoho CRM feature that models a business process as states and transitions and enforces it on every record that enters it. Zoho’s own help describes it as “simply an online replica of a business process”, meant to support automation, validation and team collaboration. Typical uses are a deal follow-up process (qualification, negotiation, discount approval, closing), lead qualification and order handling.
It is built on a picklist field of one module and layout, such as the Stage field on Deals. Each value of that field becomes a state. Zoho’s own wording for the whole thing is short: define each stage, assign the right people to it, guide them through the steps, validate key information and automate the routine actions.
Two permissions matter. Users with the Manage Automation permission in their profile can build blueprints, and team module admins can build them for their team modules.
Which Zoho CRM editions include Blueprint, and what are the limits?
Blueprint starts on the Professional edition. Zoho’s feature availability page shows it as unavailable on Free and Standard, and sets these limits above that.
| Limit | Free | Standard | Professional | Enterprise | Ultimate |
|---|---|---|---|---|---|
| Blueprints (includes default blueprints) | Not available | Not available | 3 | 50 | 100 |
| Common transitions per blueprint | Not available | Not available | 2 | 10 | 25 |
| Transitions per blueprint | Not available | Not available | 10 | 100 | 300 |
| Fields during a transition | Not available | Not available | 4 | 10 | 50 |
| Approval processes | Not available | Not available | Not available | 10 active per module, 5 rules each | 50 active per module, 5 rules each |
Source: Zoho CRM feature availability and limits, checked Oct 21, 2026.
The Professional numbers are tight. Four fields during a transition and ten transitions per blueprint are enough for a simple deal process and not much more, so a team with two pipelines and a quote step can hit the ceiling quickly. Work out which edition you need before you design the process, not after; use our Zoho CRM pricing calculator to price the editions, and our CRM pricing comparison puts Zoho’s tiers next to the other platforms.
How do states and transitions work in a Zoho CRM blueprint?
A state is the condition a record is in at a given time, and a transition is the link between two states that sets what must happen before a record can move. In Zoho’s building blocks article, Qualification, Negotiation and Discount approval are states, and “Negotiate” is the transition from Qualification to Negotiation.
Each transition shows up as a button on the record’s detail page. Clicking it opens a form, and the settings behind that form are in three parts.
| Part | What you set | Examples from Zoho’s help |
|---|---|---|
| Before | Owners (CRM users or portal users who can run the transition) and criteria that must be true for the button to appear | Show “Negotiate” only when Product Demo is Completed |
| During | What the owner must or may supply: fields, checklists, associated items (tasks, notes, attachments, meetings, calls, quotes, sales orders, cases), tags, widgets, messages | Discount not above 20%; closing date not more than 30 days out |
| After | Actions that run when the transition completes | Email alert, assign tasks, create a meeting, schedule a call, update fields, create a record, webhooks, custom functions, add tags, convert a record (Leads and Quotes only) |
Source: Zoho CRM Help, Design a Blueprint, checked Oct 21, 2026.
Items in the During tab are mandatory by default. A field counts as mandatory if the module field is mandatory, a layout rule makes it so, or the transition setting does. Multi-select lookup and multi-user fields can sit in a During tab but cannot be validated. Adding a widget removes every other item from that tab, which catches people out.
Two special cases are worth knowing. A transition can loop back to the same state, for example “Retry contacting” until the customer picks up. And an automatic transition moves a record on by itself after a wait time you set, such as moving a deal from Contacted to another state after 5 days with no qualification action.
How to create a blueprint in Zoho CRM
Go to Setup, Process Management, Blueprint, click Create Blueprint, and work through three steps: basic info, process flow, transition settings.
- Choose the module, layout and field. Zoho’s example is Deals, Standard layout, Stage field.
- Add optional entry criteria, for example Amount >= 50000. With no criteria, every record created in that layout enters the process. Check Advanced Configuration if you want a continuous blueprint, which runs in one pass with no pause.
- Open the Blueprint Editor and drag the states in. The Start state corresponds to the “None” value of the picklist. Connect states by their nodes, then click the + between two states to add a transition. Transition names can be up to 50 characters.
- Open each transition and set Before (owners, criteria), During (fields, checklists, validations) and After (actions).
- Add SLAs to states that need a time limit (see the SLA section below).
- Enable the blueprint. New blueprints are disabled by default, which is the most common reason records do not enter one.
Zoho offers sample flows for Education, Real Estate, Insurance and Banking and Finance, and says you can test a blueprint in the Sandbox without touching live data. If you have more than one blueprint matching a record, the one listed first runs, and you can reorder them. To pull existing records into a new blueprint, use the Filters tab on the Blueprint page and its Include or Exclude buttons.
What does an example blueprint look like?
Here is a deal follow-up blueprint on the Deals module, laid out by transition. It is illustrative: the stage names, owners and the 20% rule are ours, loosely based on the deal follow-up process in Zoho’s help, and nothing here was exported from a live account.
| # | From state | Transition | Before (who, when) | During (required) | After (automatic) |
|---|---|---|---|---|---|
| 1 | Qualification | Negotiate | Deal owner, after demo is marked Completed | Next-step note, decision maker field | Task to prepare proposal |
| 2 | Negotiation | Request discount | Deal owner | Discount % (validation: not above 20%), reason note | Email alert to sales manager |
| 3 | Discount requested | Approve discount | Sales manager | Checklist: margin checked | Update Discount status field |
| 4 | Discount requested | Reject discount | Sales manager | Reason note | Task to deal owner |
| 5 | Negotiation or Discount approved | Send quote | Deal owner | Quote associated to the deal | Email alert to deal owner |
| 6 | Quote sent | Close as won | Deal owner | Signed contract attachment | Create a record in the next module |
| 7 | Any state | Deal Lost (common transition) | Deal owner | Loss reason | Notify manager |
No transition here asks for more than one field, which fits the 4-field Professional limit, and seven transitions is under the 10-transition ceiling (Zoho’s pages do not say whether common transitions count toward it, so check). Add a second quote path and a renewal branch and you are close to that ceiling.
Illustrative example, built on Zoho’s published deal follow-up scenario. Edition limits from Zoho CRM feature availability, checked Oct 21, 2026.
What is a common transition in Zoho CRM Blueprint?
A common transition is one that is available from every state, so you set it up once instead of drawing it from each state. Zoho’s example is Deal Lost: whatever stage a deal is in, the owner should be able to close it out. You turn one on with a checkbox when you create the transition.
They are also how you step backwards. Zoho’s blueprint FAQ says you cannot edit the blueprint field to return to an earlier state while a record is in the process, because that would skip required steps. The workaround it gives is a common transition named “Roll Back” that removes the record from the blueprint so the field can be edited, then re-enters it at the stage you choose. Remember the cap: 2 common transitions per blueprint on Professional, 10 on Enterprise and 25 on Ultimate.
What is a parallel transition in Zoho CRM Blueprint?
Parallel transitions are several separate transitions between the same two states, all of which must be completed before the record moves to the target state, in any order. Zoho’s announcement uses a property inspection: between “Under inspection” and “Inspection completed” sit Mold inspection, Water Damage check, Structural damage and Pest Inspection, and different people can do them in whatever order suits.
That is different from multiple transitions, where several alternatives lead from one state to the same next state and the user picks one. Zoho’s example is sale, rental and lease contracts that all lead to “Contract Signed”. The two can be combined, and a transition can have sub-transitions under it. The feature started as early access and became available to all users in all data centres on August 2, 2023. The announcement does not give setup steps or limits, and we did not find them on the pages we fetched, so build a test blueprint before you promise a client a parallel flow.
How does SLA work in a Zoho CRM blueprint?
An SLA sets the longest a record can stay in one state and what the CRM does when the time runs out. In the Blueprint Editor, click a state, set the maximum time (Zoho’s example is 5 days) and the escalation notification and its timing, such as escalating to the record owner on day 5. You can add an optional alert before or after the limit, for instance 2 hours before it expires.
User-defined SLA actions are the Enterprise-and-above version: custom emails, tasks, field updates, webhooks and custom actions. Zoho’s example changes an Urgency field from Mild to Severe after 5 days in Negotiation. SLAs sit well alongside automatic transitions, which move a stalled record on after a wait time instead of only warning someone about it.
How to use a blueprint in Zoho CRM
Open a record that has entered the blueprint, look at the Blueprint strip for its current state, and click one of the transition buttons it offers. Buttons show only for records that meet the transition’s Before criteria and only for its owners. Administrators see transitions owned by other users as well.
On the transition form, fill in the required fields, tick the checklist items, attach what is mandatory and add any associated items. Validation rules stop the save when a value fails: Zoho’s example is a discount above 20%, which “throws an error.” Save as Draft keeps partial progress without moving the record, though it is not available for continuous blueprints, forms with only message fields, forms with a widget, or when layout rules run.
To find your own queue, open My Jobs and select the Blueprint tab. The mobile apps can run transitions too, from Zoho CRM for Android v3.2.16 and iOS v3.2.9. See Zoho’s executing a blueprint page for the full flow.
Blueprint vs workflow rules vs approvals: which one do you need?
Use a blueprint when people must follow steps in order, a workflow rule when something should happen automatically, and an approval process when a manager must sign off on a record. The three overlap, and Zoho says that other than Workflow, no automation tool can override a Blueprint action.
| Blueprint | Workflow rule | Approval process | |
|---|---|---|---|
| Starts on | Professional | Free | Enterprise |
| Limit | 3 / 50 / 100 blueprints (Pro / Ent / Ultimate) | 80 / 125 / 150 rules per module (Pro / Ent / Ultimate), 40 / 75 / 100 active | 10 / 50 active processes per module (Ent / Ultimate), 5 rules each |
| Who acts | Transition owners, step by step | Nobody, the CRM runs it | Approvers |
| Locks the record’s stage | Yes, until the blueprint is executed | No | Not covered on the pages we read |
| Good for | Enforcing a sales or service process | Emails, tasks, field updates, housekeeping | Discounts, big deals, exceptions |
| Verdict | Process | Automation | Sign-off |
Source: Zoho CRM feature availability and limits and Zoho CRM Blueprint FAQs, checked Oct 21, 2026. Free edition allows 10 workflow rules per module, 5 active.
A common pattern is to use all three: a blueprint for the stages, workflows for notifications and data tidy-up, and an approval step for discounts. If you are weighing Zoho against another CRM mainly for its process control, our Zoho vs Salesforce and Zoho vs Pipedrive comparisons cover where each one is stronger. If you are coming from Pipedrive, the Pipedrive to Zoho migration guide covers rebuilding stage rules and automations in Zoho.
What breaks or gets blocked in a Zoho CRM blueprint?
The common problems come from the stage lock and from the setup flags. Here is what Zoho’s pages give for each.
| What you see | Cause | Fix |
|---|---|---|
| The Stage field cannot be edited | The record is in a blueprint; the field is locked until it is fully executed | Run a transition, or build a common transition such as Roll Back that exits and re-enters the blueprint |
| Records do not enter the blueprint | Blueprint is disabled, the layout differs, or the entry criteria use a state outside the blueprint | Enable it, match the layout, fix the criteria |
| A transition button is missing | The record fails the Before criteria, or you are not a transition owner | Check the criteria and owners; administrators can see the transition |
| Save is blocked on a transition | A validation failed, for example a discount above 20% | Correct the value, or change the validation |
| Save as Draft is unavailable | Layout rules ran, the form has only messages or a widget, or the blueprint is continuous | Redesign the form if you need drafts |
| Cannot edit picklist values after deleting a blueprint | Records are still in the deleted blueprint | Move those records out or delete them |
Source: Zoho CRM Help, Blueprint FAQs, Design a Blueprint and Executing a Blueprint, checked Oct 21, 2026.
On mass update, import and the API, Zoho’s design article is specific about one thing: the primary field can be updated only through the Transition API, the Workflow API, custom functions in workflows, a workflow field update or a Command Center field update, and no other channel can update it. Mass update and import are not on that list. The pages we fetched do not say what happens when either one touches that field, so we are not going to guess. Test with a few records in the Sandbox before you run a bulk update or a data load into a module that has an active blueprint. Zoho’s developer page for the Blueprints API only documents reading blueprint configuration.
Before moving CRM data, take an export first; the Zoho CRM export guide covers it, and our CRM import limits research compares import caps across platforms.
When to get help
A single three-stage blueprint on one pipeline is an afternoon of clicking. Bring someone in when the process crosses modules, when approvals and workflows need to work with it, or when you are bumping into the edition limits and need to decide whether to upgrade. Our Zoho CRM implementation service designs blueprints as part of a rollout, and you can contact us with your process written down and we will say whether it fits your edition.
Founder’s note, Alpit Patel. A blueprint is only as good as its stage list. I’d draw the stages with the sales team on paper before opening Setup, and keep the first version small. I founded aibrevo in San Francisco in 2021, and through autoesta I have overseen 320+ GoHighLevel implementation projects across med spas, real estate, healthcare, dental, home services, SaaS and professional-services clients in the US, UK and UAE. About Alpit
Sources
- Zoho CRM Help, Blueprint: an overview, checked October 21, 2026.
- Zoho CRM Help, Understanding the building blocks, checked October 21, 2026.
- Zoho CRM Help, Design a Blueprint, checked October 21, 2026.
- Zoho CRM Help, Executing a Blueprint, checked October 21, 2026.
- Zoho CRM Help, Blueprint FAQs, checked October 21, 2026.
- Zoho CRM Help, Feature availability and limits, checked October 21, 2026.
- Zoho Community, Blueprint enhancements: parallel and multiple transitions, checked October 21, 2026.
- Zoho CRM API v8, Blueprints, checked October 21, 2026.