CRM. Zoho CRM and Zoho One
Replacing Zoho CRM and Zoho One with a system built around how you sell
Zoho CRM is a capable sales system, and Zoho One wraps it in dozens of other apps for one bill per employee. We implemented and supported both for years, for sales teams and for whole companies that ran everything on the suite. For a certain kind of business it's still a fair choice.
Then your process stops matching Zoho's. Every fix becomes a Deluge function, a Creator app, or one more app switched on in the bundle. A year later your team is maintaining a small software project on top of the subscription and owns none of it.
Where it fits
Where does Zoho fit?
We implemented and supported Zoho CRM and Zoho One for years, so this is not a hit piece. These are the cases where keeping it is the honest advice, and if yours is one of them, we will say so on the call.
A small sales team with a conventional pipeline (lead, contact, deal, quote) that fits Zoho's standard modules without much reshaping.
A company that wants email, books, help desk, and forms from one vendor and will accept the seams between those apps in exchange for one invoice.
A business with an admin who's comfortable in Zoho and has kept the configuration clean. A working Blueprint, sensible workflow rules, no shadow spreadsheets beside it.
Anywhere the CRM is a contact and pipeline record and nothing more. Zoho does that job well.
Where it breaks
Where does Zoho break down?
The failure modes below come from years of implementing and supporting the tool, and they are the ones that show up again and again as a company grows.
Zoho One is licensed for every employee, or at a higher rate if you only license some of them. A company that needs the CRM pays for the suite. A company that needs the suite pays for people who never log in.
Customization runs through Deluge, Zoho's own scripting language. It works. But few developers know it, so every custom function ties you tighter to the one person who wrote it, which is the exact risk custom software used to be accused of.
Zoho One is a lot of apps sharing a login and a bill. They don't share a data model. Books, Desk, Projects, and CRM each have their own admin panel, their own fields, and their own idea of what a customer is, so cross-app reporting turns into Zoho Analytics work or an export.
Features are gated by edition. The thing you need next (a sandbox, more workflow rules, deeper permissions, higher API limits) usually lives one tier up, and the upgrade applies to every seat.
Quoting is where most sales teams hit the wall first. The quotes module handles line items and standard discounts. Anything with real pricing logic (tiers, options, margins, dependencies between lines) ends up in a spreadsheet next to the CRM, re-keyed by hand.
We saw the same pattern over and over. Zoho for the record, a spreadsheet for the pricing, a second tool for the part Zoho couldn't do, and someone re-keying between them.
The replacement
What does replacing Zoho CRM and Zoho One look like?
A custom CRM has the objects your business actually talks about (accounts, sites, projects, contracts, whatever they are), named the way your team names them. The pricing logic lives inside the quote instead of in a spreadsheet beside it. The pipeline is yours, the fields are yours, and the reporting is built for the questions you ask, so there's no separate analytics product to license.
Migration is real work and we treat it that way. Zoho's export and API let us pull accounts, contacts, deals, notes, attachments, and activity history into the new system, mapped field by field. We usually run both side by side, the new one importing from Zoho on a schedule, so your team can check the numbers match before anyone stops using the old one.
If Zoho Books or Zoho Desk is doing its job, it stays. A custom system can sync with the parts of the suite that work, so nobody has to leave all of them at once. That's often the difference between a migration your team accepts and one they fight.
You own the result. The code lives in a repository in your name, the database and hosting sit on accounts in your name, and there's no seat count and no edition tier. We're added as administrators to build and support it, and you can remove us at any time.
The stakes
What does it cost to get this wrong?
More than the software. A replacement that goes badly costs you the one thing the old system was still doing, a single place your team agrees on. The failures below each turn a rebuild into a year of parallel systems, so they are the ones we plan around.
Zoho One is one login over a dozen separate data models. Move the CRM without deciding what a customer record means in Books and Desk and you end up with two customer lists that disagree, billing and support each certain the other is wrong.
Deluge is where the rules live, and they're written down nowhere else. Copy the functions across without reading them and nobody can say why a deal changes stage. The first argument about a commission then has no answer in the system.
Attachments and notes are the part teams forget. Contracts, signed change orders, the note explaining why a discount was given. All of it sits inside Zoho, and a migration that carries only fields leaves your account history with a hole in it.
The order of work
What happens, in what order, when you leave Zoho?
Each step exists because skipping it is how the previous attempt failed. The sequence is fixed. The runway is not, and it goes in your written scope once we know the shape of your data rather than on this page as a calendar promise.
- 01
Suite usage audit
We list every Zoho app on the bill and check which ones have actually been written to. Opened doesn't count. Creator apps, Analytics workspaces and Desk queues get counted, along with every Deluge function and Blueprint that still fires. Most companies find they're paying suite pricing for three or four apps in real use.
- 02
Export and shape check
Zoho exports each CRM module to CSV and exposes the rest through its bulk read API. We pull a sample and check the shape. Lookup fields come out as names where you wanted ids, notes and attachments take separate calls, and no export anywhere contains your layout rules, validation rules or Blueprint transitions. Whatever won't come out gets named right there.
- 03
Rules read out of Deluge
Every custom function, workflow rule and Blueprint transition gets read for the rule it enforces, written down in plain language, and confirmed with the person who relies on it. The ones that only patch a Zoho limit get dropped. What survives is rebuilt in a mainstream language, tested and version controlled.
- 04
Build against live Zoho
The new system is built while Zoho stays the system of record, importing accounts, contacts, deals, notes and attachments through the API on a schedule. Your team keeps selling in Zoho the whole time. Books and Desk are left alone at this stage, synced into the new system, so finance and support see no change.
- 05
Parallel, then the seats go
Both systems run together while your team checks the pieces they care about. Record counts per module, pipeline totals by stage, the reports the owner reads. Once those reconcile, and people have stopped opening Zoho out of habit, the cutover happens. The seat count on the renewal drops to nothing.
Limits
What we will not do
Saying this out loud is cheaper for both of us than finding out in month two. If one of these is what you actually want, we are the wrong firm and we will say so on the first call.
- We won't rebuild your Zoho configuration as it stands. If the pipeline has stages nobody uses and three fields that mean the same thing, that gets settled in discovery. Copying it forward buys you a new tool and the same confusion.
- We won't take over your Zoho login or hold any account we build on. Every repository, database and hosting account is created in your company name, and we're invited in as administrators you can remove.
- We won't leave you running two systems forever. A migration that stalls halfway costs more than the subscription ever did, so the written scope names the point where Zoho stops being the record and what has to be true to get there.
Questions
What people ask about leaving Zoho CRM and Zoho One
Do we have to leave all of Zoho One at once?
No. Most teams replace the CRM first, because that's where the workarounds pile up, and keep Books or Desk running with a sync in between. Every remaining app is its own decision, made once the new system has settled.
Can you move our data out of Zoho CRM?
Yes. Zoho supports bulk export and has a real API, so records, notes, attachments, and history all come across, with a field-by-field mapping you approve before cutover. Anything Zoho won't export cleanly gets flagged early, while there's still time to deal with it.
We have a lot of Deluge functions. Do those come with us?
The logic does. The code doesn't. We read what each function actually does, decide with you which rules still matter, and rebuild those in a mainstream language any developer can maintain. Functions that only existed to patch a Zoho limitation usually just disappear.
Is a custom CRM more work to keep running than Zoho?
It runs on managed hosting and a managed database, so there's no server to babysit. Small changes get made in code rather than on a settings screen, which is a change of habit for an admin who liked Zoho's configuration pages. You can keep an optional support plan with us for that. And you stop paying per seat.
What does replacing Zoho cost?
It depends on how much of the suite you use, how many records you have, and what the new system has to connect to, so we don't publish figures. After a strategy call you get a written scope listing what will be built and what it costs. The conversation starts from what you already pay Zoho every year.
What happens to our historical data when we leave Zoho?
It comes with you and stays queryable. Accounts, contacts, deals, notes, attachments, email history and the audit trail all get pulled through Zoho's export and API into tables you own, with the original record dates kept, so nothing arrives stamped with the day of the import. We also keep a read-only archive of the raw export, so if a question comes up about a record from years back the answer exists in two places. Nothing has to stay subscribed for your history to be readable.
Our team has used Zoho for years. Do they have to relearn everything?
Most of them will notice less than you expect. The screens get built around the way your team already works, in your own words for records and stages, so a salesperson opening a deal sees a familiar layout with the workarounds taken out. The big change lands on the admins who lived in Zoho's setup pages, because configuration moves into code and requests come to us or to whoever maintains the system. Training runs on your real process.
What if we decide we want to go back to Zoho?
You can, and the migration is designed so that stays possible. Zoho doesn't get deleted at cutover. The account is downgraded or left dormant with your data still in it, which is your fallback while confidence gets built. Going back later means importing from your own database into Zoho's API, and that's ordinary work, because your data sits in a standard SQL database that any developer can read. Nothing in the design locks you in. That's the point of owning the database.
From the knowledge base
Guides for people weighing up Zoho CRM and Zoho One
Reference pages, not sales pages. Each one is useful even if you decide to stay exactly where you are.
How to export your data out of Zoho CRM
Every export path Zoho CRM gives you, in the order to use them, plus the things that never come out in a file and have to be captured another way.
How to tell whether your business actually needs custom software
Seven tests you can run against your own operation this week. Most businesses that run them find a configuration problem, not a build.
Related
Coming from a different tool?
The same honest treatment for the other platforms we used to implement, and the pages that explain the custom model itself.
Tell us where Zoho CRM and Zoho One stopped fitting
Book a strategy call, or send a short note about the workarounds your team runs today. If keeping Zoho CRM and Zoho One is the right answer, you will hear that first.