At what revenue should we move off Zoho?

The trigger is not revenue alone. It is the combination of revenue past ₹10cr, more than 4 Zoho modules in use, a single Zoho admin who owns the custom-field knowledge, and founder reports being answered via Excel exports. When two or more of these are true, the math has usually flipped.

How long does a Zoho-to-custom migration take?

8 to 16 weeks for a typical mid-market manufacturer. The first 2 to 4 weeks are the diagnostic and schema design. The next 6 to 10 weeks are build. The last 2 to 4 weeks run Zoho and the new system in parallel before cutover. We document the schema, write the migration scripts, and train the team.

Can we keep Zoho's CRM and replace only the ERP?

Yes, and this is sometimes the right answer when the sales pipeline is genuinely generic and the operations are specific. We integrate Zoho CRM with the custom ERP via webhooks or a sync layer. This is the cheaper path when the CRM is not the breaking constraint.

What does a custom ERP cost over five years compared to Zoho?

A custom build at ₹5L to ₹15L plus hosting at ₹1500 to ₹15k a month, with an optional retainer at ₹50k to ₹1.5L a month, runs ₹10L to ₹40L over 5 years. A growing Zoho One subscription at 20+ users with 5+ modules and addons commonly runs ₹15L to ₹45L over the same window. The crossover is around year 2 to 3 for most firms above ₹10cr.

What if we hire a Zoho consultant instead?

A good Zoho consultant solves the configuration problem. They do not solve the structural problem of the data model not fitting the workflow. The custom-field maze grows. Eventually the consultant recommends moving off Zoho, which is when most founders call us.

Do you support hybrid setups where Zoho stays alongside custom?

Yes. The honest pattern for firms above ₹15cr is often Zoho CRM plus a custom ERP plus Tally accounting, integrated where the data crosses. We design for that integration, not against it.

Compare · Zoho vs Custom

Zoho One vs custom ERP for Indian manufacturers.

Zoho One is excellent in the entry tier. Past about ten crores of annual revenue, the custom-field stack starts to bend in ways the founder cannot fully audit. Here is the honest framing.

Start a Conversation See the case

Side by side

The comparison in one table.

Honest framing. Where one wins, we say so. Where the other wins, we say that too.

Dimension	Zoho One	Custom ERP
Time to first usable system	1 to 4 weeks of configuration	4 to 12 weeks of build
Year-one cost	₹1L to ₹6L subscription depending on users and modules	₹5L to ₹15L build, hosting ₹1500 to ₹15k/month
Five-year total cost	₹15L to ₹45L of subscription. Increases with users and addons.	Build cost amortises. Retainer ₹50k to ₹1.5L/month optional.
Pricing models	List price + discount fields. Custom fields for tiered pricing get fragile.	Tier slabs, scheme discounts, customer-specific rate cards modelled directly.
Multi-warehouse + stockyard	Zoho Inventory treats warehouses as containers. Bin location is a custom field.	Bin location, batch movements, FIFO accounting modelled as first-class objects.
Vertical-specific workflows	Force-fit into the lead, deal, and quote objects. Reports break.	Schema designed for the workflow. Reports query what was modelled.
Reporting depth	Native reports work for the standard objects. Custom-field reporting via export to Excel.	Every operational question becomes a SQL query or a saved view.
Data ownership and exit	CSV export. Custom logic and workflows do not export. Schema documentation rare.	Postgres dump, source code, infrastructure all in your accounts.
Vendor lock-in	Switching costs measured in months of founder attention.	Switching costs the time to find a new shop. Code and data stay yours.
Right-fit revenue band	Under ₹10cr, generic operations, small custom field set.	₹10cr to ₹100cr+, specific workflows, custom calculations.

DimensionTime to first usable system
Zoho One1 to 4 weeks of configuration
Custom ERP4 to 12 weeks of build
DimensionYear-one cost
Zoho One₹1L to ₹6L subscription depending on users and modules
Custom ERP₹5L to ₹15L build, hosting ₹1500 to ₹15k/month
DimensionFive-year total cost
Zoho One₹15L to ₹45L of subscription. Increases with users and addons.
Custom ERPBuild cost amortises. Retainer ₹50k to ₹1.5L/month optional.
DimensionPricing models
Zoho OneList price + discount fields. Custom fields for tiered pricing get fragile.
Custom ERPTier slabs, scheme discounts, customer-specific rate cards modelled directly.
DimensionMulti-warehouse + stockyard
Zoho OneZoho Inventory treats warehouses as containers. Bin location is a custom field.
Custom ERPBin location, batch movements, FIFO accounting modelled as first-class objects.
DimensionVertical-specific workflows
Zoho OneForce-fit into the lead, deal, and quote objects. Reports break.
Custom ERPSchema designed for the workflow. Reports query what was modelled.
DimensionReporting depth
Zoho OneNative reports work for the standard objects. Custom-field reporting via export to Excel.
Custom ERPEvery operational question becomes a SQL query or a saved view.
DimensionData ownership and exit
Zoho OneCSV export. Custom logic and workflows do not export. Schema documentation rare.
Custom ERPPostgres dump, source code, infrastructure all in your accounts.
DimensionVendor lock-in
Zoho OneSwitching costs measured in months of founder attention.
Custom ERPSwitching costs the time to find a new shop. Code and data stay yours.
DimensionRight-fit revenue band
Zoho OneUnder ₹10cr, generic operations, small custom field set.
Custom ERP₹10cr to ₹100cr+, specific workflows, custom calculations.

Comparison framed for founder-led Indian businesses, ₹5cr to ₹50cr.

When zoho one wins

Pick this when these are true.

+You are under ₹5cr in revenue with under 10 users.
+Your operations look like a generic B2B sales pipeline.
+You do not have unusual pricing rules or warehouse logic.
+You need a working CRM and basic accounting in under a month.
+You are not paying for more than 4 modules.

When custom erp wins

Pick this when these are true.

+You are above ₹10cr and Zoho's reports stop matching your workflow.
+Your sales team manages tier discounts, scheme rates, or customer-specific pricing that needs auditing.
+Your stockroom or stockyard has FIFO, batch tracking, or bin-location requirements.
+Your founder asks operational questions that get answered via Excel exports.
+You have hit the Zoho admin bottleneck where one person owns the custom-field knowledge.

The longer answer

Reasoning, in plain language.

The pattern is consistent across the manufacturers and distributors who bring us in to replace Zoho. The product itself is well-built. The problem is not the product. The problem is that Zoho One was designed for the operating system of a generic mid-market business, and your business is not a generic mid-market business by year five.

The first symptom is reports. The founder asks for revenue net of scheme discounts by customer tier for the last quarter. The Zoho admin opens the report builder, finds the custom fields where the scheme rate is stored, finds out the field is a text field because the original schema did not allow a decimal, exports to Excel, builds a pivot table, sends it across the next afternoon. By the time the answer arrives the question has moved on.

The second symptom is pricing. Tier discounts and scheme rates encoded as workflow automations and custom price lists work until they do not. Quotes start going out with margins the founder cannot reconstruct. The Zoho ceiling for mid-market Indian manufacturers essay walks through this in detail.

The third symptom is the admin bottleneck. One person knows the system. They leave or get promoted. The next person inherits a Zoho instance they cannot fully read. The documentation, even when written, rarely captures the why.

A custom ERP solves these by modelling your workflow directly. The schema knows what a scheme discount is, what a customer tier is, what bin location 4A means. Reports query what was modelled rather than scraping custom fields. This is what we mean by decision infrastructure. The honest comparison is not "Zoho is bad" but "Zoho was designed for a different problem". Once you are past it, the cost of staying is larger than the cost of leaving.

If you are still inside the band where Zoho fits, stay. We will say so on the diagnostic call. The decision is structural, not aspirational.

The customisation works, in the narrow sense that data gets entered. The reasoning behind it lives in the Zoho admin's head.

From the Zoho ceiling essay

From the work

Real engagement, not a sales scenario.

Three cutting-tool manufacturers in Mumbai were running on Zoho One. Each business had its own custom-field maze, its own admin, its own broken reporting. We built CFX, a multi-tenant ERP on AWS with isolated schemas, a dedicated Android sales rep app, and Gemini AI for RFQ parsing. The three businesses now share one platform with consolidated reports for the holding group.

Read the Carbiforce case →

Engagement structure

Every comparison ends in the same decision. Either you have outgrown the off-the-shelf and need a fitted system, or you have not. The diagnostic answers it honestly.

Diagnostic · ₹1L–₹3L · 1–2 weeks

How we work →

Questions founders ask

FAQ.

At what revenue should we move off Zoho?: The trigger is not revenue alone. It is the combination of revenue past ₹10cr, more than 4 Zoho modules in use, a single Zoho admin who owns the custom-field knowledge, and founder reports being answered via Excel exports. When two or more of these are true, the math has usually flipped.
How long does a Zoho-to-custom migration take?: 8 to 16 weeks for a typical mid-market manufacturer. The first 2 to 4 weeks are the diagnostic and schema design. The next 6 to 10 weeks are build. The last 2 to 4 weeks run Zoho and the new system in parallel before cutover. We document the schema, write the migration scripts, and train the team.
Can we keep Zoho's CRM and replace only the ERP?: Yes, and this is sometimes the right answer when the sales pipeline is genuinely generic and the operations are specific. We integrate Zoho CRM with the custom ERP via webhooks or a sync layer. This is the cheaper path when the CRM is not the breaking constraint.
What does a custom ERP cost over five years compared to Zoho?: A custom build at ₹5L to ₹15L plus hosting at ₹1500 to ₹15k a month, with an optional retainer at ₹50k to ₹1.5L a month, runs ₹10L to ₹40L over 5 years. A growing Zoho One subscription at 20+ users with 5+ modules and addons commonly runs ₹15L to ₹45L over the same window. The crossover is around year 2 to 3 for most firms above ₹10cr.
What if we hire a Zoho consultant instead?: A good Zoho consultant solves the configuration problem. They do not solve the structural problem of the data model not fitting the workflow. The custom-field maze grows. Eventually the consultant recommends moving off Zoho, which is when most founders call us.
Do you support hybrid setups where Zoho stays alongside custom?: Yes. The honest pattern for firms above ₹15cr is often Zoho CRM plus a custom ERP plus Tally accounting, integrated where the data crosses. We design for that integration, not against it.

Begin

The answer lives inside your operation.

Comparison pages help frame the choice. The choice itself is made against the workflows, the team, and the data you already have. That is what the diagnostic surfaces.

Start a Conversation