Five ways agencies set up Zoho CRM wrong (and how to fix them)
1. Treating every policy as a deal and forgetting it after it closes
Zoho's Deals module is built for sales that end. Policies don't end when they're issued. They renew, lapse, pay commissions for years, and get reviewed. If a policy vanishes into "Closed Won," your service team loses track of it. Fix: give policies a place to live after the sale, whether that's a Policies module or a clear post-sale stage structure.
2. No carrier module
When the carrier is a picklist or a text field, you can't track appointments, contacts, commission schedules, or product lists per carrier. Fix: make carriers their own records and link policies and agents to them.
3. A pipeline built for sales, not underwriting
"Qualified, proposal, negotiation" doesn't describe a life insurance case. Fix: stages that match how a case actually moves: application, underwriting, approved, issued, placed. Now the pipeline tells you where the bottleneck is.
4. Everyone is an admin
It's the fastest way to get started and the fastest way to get fields deleted, layouts broken, and records visible to people who shouldn't see them. Fix: a small set of profiles based on job: admin, agent, service, commissions.
5. Importing before the structure is ready
Data imported into a half-built CRM has to be moved again later. Fix: design modules and fields first, test with a small sample, then import.
Common questions
Can I fix these without starting over?
Usually, yes. Most fixes are adding a module, moving fields, and migrating records into the new structure. The earlier you do it, the less data you have to move.
Should policies be Deals or a custom module?
It depends on how you sell. If one sale always becomes one policy, Deals can work. If a client can have several policies, or policies outlive the sale, a separate Policies module is cleaner.
How many admins should an agency have?
One or two. Everyone else should have a profile that fits their job.