What a Zoho CRM setup checklist for a UK firm covers, and why the order matters
This Zoho CRM setup checklist for a UK firm covers the decisions you make in the first weeks of a new system. These are modules, pipeline stages, roles, layouts, mandatory fields, email, data import and the settings a UK business needs for VAT, addresses and consent. It is written for owners and managers who will do the build themselves or oversee whoever does.
A CRM, or customer relationship management system, is the shared record of every company, person and sale your business deals with. If the term is new, read our plain explanation of what a CRM is first. The basics of Zoho CRM shows the screens you will be working in.
The order of the work matters more than any single setting. Structure comes first, then people and permissions, then data, then automation. When a firm reverses that order, it usually has to go back and rebuild. One practitioner in a Reddit discussion of Zoho CRM setup put it in four words: "Bad structure = endless workarounds."
Each section below says what to decide, why it matters and where setups usually go wrong. A summary table near the end brings the steps together, so you can print it and tick items off as you go.
Step 1: Define outcomes, then fix the data model
Start with what you want to improve, not with features. The same Reddit checklist recommends naming three to five measures before you configure anything. Its examples are speed to lead, win rate, cycle time and retention. Write yours down. Every later decision should help you measure one of them.
Next, decide what kind of record lives where. In Zoho CRM a module is a list of records of one kind, much like a tab in a spreadsheet. The four you will use most are these:
- Leads: enquiries you have not yet qualified.
- Contacts: named people you deal with.
- Accounts: the companies those people work for.
- Deals: sales in progress, each with a value and a stage.
Some firms also need custom modules, which are lists you create for things the standard modules do not cover, such as sites, contracts or equipment. The Reddit checklist advises settling this split "before automation", and that is sound. Once workflows depend on a field in the wrong module, moving it means rebuilding the workflow as well.
A quick test helps. For each item of information, ask whether it belongs to the person, the company or the sale. A delivery address belongs to the company. A job title belongs to the person. A quoted price belongs to the deal.
Step 2: Build a short pipeline with real stages
A pipeline is the sequence of stages a deal passes through from first contact to won or lost. The common mistake is copying the stages from a demo instead of mapping how your firm actually sells. The Reddit checklist advises keeping stages minimal, so that each one means "a different decision/action happens here."
For a UK services firm, a workable first pipeline might look like this:
- Enquiry received
- Site visit or discovery call booked
- Proposal sent
- Negotiation
- Won or Lost
Test each stage with your sales team. If two people describe the same stage differently, or cannot say what happens next, merge it with its neighbour. Every extra stage is another place for deals to sit unexamined. It also makes your win rate and cycle time figures harder to trust.
If your firm is small and the pipeline is the whole process, consider whether you need full Zoho CRM at all. Zoho describes Bigin as "a simple pipeline-centric CRM, built and priced for small businesses." Our page on Zoho Bigin for UK businesses sets out when it is enough. The worked example later in this guide uses Bigin's stage checklists, because Zoho documents that feature step by step.
Step 3: Set roles, profiles and mandatory fields early
Permissions are easiest to set before anyone has data to lose. The Reddit checklist says "roles, profiles, field permissions, and required fields should match how your team works". It names sales, operations and admin as the usual groups. Treat access as two separate questions. The first is whose records a person can see. The second is what they may do with those records: create, edit, delete or export.
Keep the structure flat to begin with. A director, a sales manager and the sales team is enough for most small firms. Add field permissions only where they protect something specific, such as margin or a customer's bank details. They should not be a way to hide clutter.
Mandatory fields
A mandatory field is one a user must fill in before a record can be saved. Mandatory fields protect your reporting, but each one adds friction. Limit them to the fields your measures from step 1 depend on, such as lead source, deal value and expected close date.
At Svennis we set mandatory fields only after watching a salesperson create a real deal on the mobile app, because a field that is easy to fill at a desk can stall a rep standing outside a client's office. If people cannot save a record quickly on a phone, they stop recording, and the data gaps return.
Step 4: Shape layouts and the UK-specific fields
A layout is the arrangement of fields on a record's screen. Put the fields people fill in most at the top, group the rest under clear headings and remove anything nobody uses. A shorter layout gets filled in more completely than a long one.
A UK firm should settle a handful of fields and settings before any data goes in:
- Currency: make pounds sterling the home currency, so deal values and reports read in GBP.
- Date format and time zone: set day, month, year order and UK time. Otherwise imported dates such as 04/05 are read the wrong way round.
- Address fields: use Street, Town, County, Postcode and Country. Default Country to United Kingdom and keep County optional, since many UK addresses do not need it.
- VAT registration number: store it on the Account, because it belongs to the company, not to a person or a deal.
- Consent and lawful basis: add fields on Contacts and Leads for the basis you rely on, the date consent was given and where it came from. Step 8 covers this.
Use a dropdown list, not free text, wherever you will want to filter or report. "Referral", "Website" and "Trade show" in a dropdown can be counted. Twenty spellings of the same source typed by hand cannot. Our guide on how to customise your CRM covers field types in more detail.
| UK choice | Why it matters | |
|---|---|---|
| Home currency | Pounds sterling | Deal values and reports read in GBP |
| Date format and time zone | Day, month, year and UK time | Imported dates such as 04/05 read the right way round |
| Address fields | Street, Town, County, Postcode, Country | Country defaults to United Kingdom, County stays optional |
| VAT number | A field on the Account | Tax details sit with the company, not the person |
| Consent fields | Lawful basis, consent date and source, review date | UK GDPR records live in the CRM, not a separate file |
A worked example: a stage checklist that blocks incomplete deals
Here is one control you can follow step by step. A checklist in Bigin is a set of items that must be completed before a deal moves from one stage to the next. Zoho's Bigin checklist guide sets it up in ten steps. The version below is condensed.
Say a small UK facilities firm wants every won deal to carry the client's purchase order and signed quote before the job is handed to operations.
- Open Settings and go to the Stages option.
- Choose Stage Transition Rules.
- Pick the Team Pipeline and Sub-Pipeline the rule applies to, for example "Sales" and "Contract work".
- Set the From Stage to "Negotiation" and the To Stage to "Won".
- Add a Field item for the purchase order number, a File item for the signed quote and a Notes item for handover instructions.
- Name each item in your own words. Zoho lets you name checklist items to suit your requirements.
- Mark the items as mandatory. Zoho notes that Notes, Fields and File can each be mandated.
- Save the rule.
From then on, a rep cannot mark the deal won until all three items are in place. The principle carries over to full Zoho CRM. Put the requirement at the moment it matters, not on every save. A purchase order number is irrelevant at enquiry stage, so making it mandatory there only produces placeholder text.
| Step | What you do | In the example |
|---|---|---|
| 1. Open the rule screen | Settings, then Stages, then Stage Transition Rules | Rule is set up once by the admin |
| 2. Choose where it applies | Pick the pipeline and sub pipeline | Sales and Contract work |
| 3. Set the transition | From Stage and To Stage | Negotiation to Won |
| 4. Add checklist items | A Field item and a File item | Purchase order number and signed quote |
| 5. Make items mandatory and save | Click Save to apply the rule | Operations only receives complete deals |
Step 5: Connect email, calendar and Zoho Books
A CRM that does not see your email becomes a second inbox nobody checks. Firms on Microsoft 365 should look at Zoho CRM's Office 365 integration first. Zoho's help centre says it "currently" allows user import, calendar synchronisation and contacts synchronisation. Test all three with one user before you switch them on for the team, and check that shared or personal calendars are not pulled in by mistake.
For other tools, Zoho lists two routes. Zoho Flow is its integration platform for connecting cloud applications and automating workflows between them. The Zoho Marketplace is an online store of ready-made extensions for Zoho products. Try a Marketplace extension before paying for custom work.
Zoho Books
For most UK firms the key link is between CRM and accounts. Before you connect Zoho Books, decide which system owns each shared item. Our usual answer is that CRM owns the customer name, contacts and deal. Books owns invoices, payments and VAT treatment. The company address and VAT number are entered once, and one system is the master.
Write that down as a one-page rule and give it to whoever edits records in either system. Most sync problems come from two people correcting the same address in two places. Our intermediate Zoho CRM guide goes further into connected apps.
Step 6: Clean and import your data
Zoho has refreshed the CRM import feature, and its release notes say the new version "has been released for all users in all DCs". File storage for new Zoho CRM signups now runs on WorkDrive, Zoho's file storage service. Existing accounts are moving over in phases. If you attach documents to records, check which storage your account uses before you plan a bulk upload.
The import tool is not the hard part. The data is. Work through your spreadsheet in this order:
- Remove duplicates: merge rows for the same company or person first.
- Standardise values: make lead sources, counties and industries match the dropdown lists you built in step 4.
- Fix formats: put dates in day, month, year order and keep phone numbers in one style.
- Drop what you cannot justify keeping: old contacts with no lawful basis for holding their data should not move across.
Import companies before the people linked to them, and people before their deals, so the links resolve. Run a small test batch first. Open a few imported records and check every field landed where you expected. Then set a date after which the old spreadsheet is read-only. While both are live, some of the team will keep using the spreadsheet.
Step 7: What to switch off, or leave off, on day one
A new system is at its most fragile in its first weeks. The Reddit checklist advises automating "only the repetitive, high-confidence actions". Its examples are lead assignment, follow-up tasks, status changes, notifications and handoffs. Everything else can wait until you have watched the process run.
On day one, leave these off or keep them minimal:
- Automatic emails to customers: send them to an internal address until you have tested every trigger.
- Complex assignment rules: an assignment rule gives new leads to a named person automatically. Start with one simple rule, such as by region, and add others once it works.
- Dashboards: build them only after fields and stages are stable. The same checklist warns that otherwise "you'll rebuild reports repeatedly."
- Unused modules and tabs: hide them so people see only what they need.
- Field creation rights: keep them with one administrator, so the layout does not grow a new field every week.
- Noisy notifications: switch off alerts people will learn to ignore.
Install the mobile app on a test phone before launch. Create a lead, log a call and move a deal through a stage. Anything that is awkward on a small screen will be skipped in the field.
| At launch | Once proven | |
|---|---|---|
| Customer emails | Send to an internal address | Switch on after every trigger is tested |
| Assignment rules | One simple rule, such as by region | Add further rules once the first works |
| Dashboards | Leave off | Build once fields and stages are stable |
| Other automation | Only repetitive, high confidence actions | Extend after watching the process run |
What this means for a UK firm
Three decisions are specific to running a CRM in the UK.
Where the data sits
Zoho runs its services from more than one data centre, which is why its release notes refer to "all DCs". Confirm which data centre your account sits in before you import personal data. If it is outside the UK, check that Zoho's data processing terms cover the transfer, and record both answers in your data protection records.
Consent and retention
Under UK GDPR, you need a lawful basis for holding each person's data and a reason for how long you keep it. Build this into the CRM, not a separate file. Add a dropdown for lawful basis, a consent date and source, and a review date for records that go quiet. Then set up a saved view of contacts due for review.
Money and tax
GBP as home currency and VAT numbers on Accounts keep your CRM consistent with your accounts system. VAT treatment belongs in your accounting software, so do not recreate tax rules in CRM fields.
Budget for the whole job, not only the licence. A software cost guide on a Hampshire County Council site defines total cost of ownership as upfront and recurring costs plus hidden costs: training, customisation, data migration and support. These are the costs most often left out, so price them into your plan before you commit.
The checklist at a glance
The table brings the steps together. Work down it in order, and do not start a row until the one above it is settled.
| Step | Decision | UK note | Where it goes wrong |
|---|---|---|---|
| 1. Outcomes and data model | Three to five measures; what lives in Leads, Contacts, Accounts, Deals | VAT number belongs on the Account | Fields placed in the wrong module |
| 2. Pipeline | Few stages, each a different action | Match how UK clients buy, such as a PO before work starts | Stages copied from a demo |
| 3. Roles and fields | Who sees what; who can do what; minimal mandatory fields | Restrict exports of personal data | Mandatory fields that stall mobile users |
| 4. Layouts | Short screens, dropdowns for reporting | GBP, UK dates, Postcode, consent fields | Free text where you need counts |
| 5. Integrations | Email, calendar, Zoho Books, one master per item | Books owns invoices and VAT treatment | Two systems both editing addresses |
| 6. Import | Clean, test batch, then full import | Leave out data with no lawful basis | Old spreadsheet left in use |
| 7. Day one | Simple automation only | Consent review view in place | Customer emails fired untested |
Keep a copy with your launch notes. When something breaks after go-live, the fault usually traces back to a row that was skipped.
Next steps
Turn this guide into a short plan you can act on this week.
- Write your measures: agree three to five with whoever owns sales, and put them at the top of a one-page brief.
- Draw the data model: list the fields you need and mark each as belonging to a person, a company or a deal.
- Agree the stages: run the list past two salespeople and cut any stage they describe differently.
- Settle the UK settings: currency, date format, time zone, address fields, VAT number and consent fields, before any import.
- Clean one spreadsheet: take your largest customer list, remove duplicates and prepare a small test import.
- Write the master data rule: one page saying which system owns each shared field between CRM and Zoho Books.
- Book two review points: one a few weeks after launch and one a few months later, to adjust fields, stages and automation.
If you would rather have the build scoped and configured for you, our Zoho CRM implementation page explains how we approach a UK setup. Bring your one-page brief, and the first conversation can start from your process, not from the software.