Zoho People, Projects & Operations

THE OPERATIONS PROBLEM

Every Hire and Every Exit Is a Manual Checklist Somebody Forgets

A new person starts Monday. Somebody creates their email, then their CRM login, then their project tool seat, then their file storage access, then their chat account, then their password manager invite, then adds them to payroll — across seven admin panels, from a checklist in a document, hoping nothing is missed.

The exit is the same sequence in reverse, and it is the one that actually matters. Months after someone leaves, their file storage account is usually still active, because de-provisioning depended on a person remembering every system rather than on a system enforcing it.

Meanwhile the work itself is scattered too. Projects in one tool, support tickets in another, the HR record in a third, and the one process that is genuinely specific to your business living in a shared spreadsheet with seventeen tabs that one person understands.

What it costs you

Onboarding that takes an admin most of a day across seven separate consoles
Former employees retaining access to systems nobody remembered to revoke — a real security exposure
Time-off requests in email, approvals in chat, and the balance tracked in a spreadsheet
Project profitability nobody can calculate because time tracking and costs live in different tools
Support tickets with no visibility into whether the customer is in a renewal
The critical business process that runs on a spreadsheet only one person can maintain

THE APPLICATIONS

What You Get, In Detail

Every one of these is included in a Zoho One licence — no per-app upsell, no separate contract, no additional integration bill.

Zoho People

The HR system of record: employee database, org chart, time-off policies and accruals, attendance and shift scheduling, timesheets, performance reviews and goals, and onboarding workflows with document collection and e-signature built in.

Replaces BambooHR, Namely, Rippling

Zoho Recruit

Applicant tracking with one-click posting to the major job boards, resume parsing, candidate pipelines, interview scheduling, scorecards, and offer management. An accepted offer becomes an employee record in People without anyone re-typing a name.

Replaces Greenhouse, Lever, Workable

Zoho Projects & Sprints

Project management with Gantt charts, task dependencies, resource utilization, budgets, timesheets, and issue tracking — plus Sprints for agile teams running backlogs, scrum boards, and velocity reporting. Billable time posts straight into Books.

Replaces Asana, Monday.com, Jira

Zoho Desk

Omnichannel help desk covering email, chat, phone, and social in one queue, with SLA policies, escalation rules, a self-service knowledge base, and customer portal. Every ticket carries full CRM and billing context inline.

Replaces Zendesk, Freshdesk, Help Scout

Zoho Creator

The low-code builder for the process no vendor sells software for — your inspection workflow, your compliance log, your equipment tracker. What you build inherits the same users, permissions, and data as everything else instead of becoming another island.

Replaces Airtable, Retool, custom development

Zoho Directory

The identity spine underneath all of it: single sign-on, enforced MFA, Active Directory sync, conditional app assignment by role, and mobile device management. Provisions and de-provisions every app in one action.

Replaces Okta, JumpCloud, OneLogin

IN PRACTICE

One Workflow, End to End

The difference between a suite and a stack is what happens between the applications. Here is a single process moving through several of them without a hand-off.

A hire, onboarded and fully provisioned, in one sequence

A candidate accepts an offer in Zoho Recruit; the record converts into an employee in Zoho People automatically.
Zoho Directory provisions their identity in one action — email, SSO, MFA, and exactly the app permissions their role calls for.
WorkDrive grants team folder access by role and Cliq adds them to the right channels.
Onboarding documents go out through People with Zoho Sign collecting signatures and filing them to the employee record.
Zoho Learn assigns the role-specific training path and tracks completion.
Payroll picks them up on the next run with the correct tax setup and deductions.

One sequence, one system, nothing forgotten. And when they eventually leave, a single action revokes access to all 45 applications at once — which is the half of this that your security posture actually depends on.

MIGRATION REALITY

What Moving Actually Involves

The honest version, including where it is genuinely painful. Anyone who tells you a migration is effortless has not run one.

Coming from BambooHR or Namely

Employee records, org structure, and time-off balances export and import cleanly. Plan carefully for two things: historical performance review data, which often needs manual handling or a decision to archive rather than migrate; and time-off accrual balances, which must be reconciled exactly as of the cutover date or you will be fielding disputes for months.

Coming from Asana, Monday, or Jira

Active projects and tasks move over with reasonable fidelity. Completed project history is usually the sticking point — and often the right answer is to archive it in the old system for reference rather than pay to migrate work nobody will reopen. Jira migrations need the most thought where teams have built elaborate custom workflows and automation rules.

Coming from Zendesk or Freshdesk

Tickets, contacts, and knowledge base articles migrate through native tooling. The real work is rebuilding SLA policies, business hours, escalation rules, and macros — these do not port, and they are exactly the accumulated configuration that makes a help desk useful. Run both systems in parallel for a week or two and route new tickets to Zoho while the old queue drains.

Coming from Google Workspace or Microsoft 365

The identity migration is the consequential one, and it deserves its own plan. Email and files move with established tooling, but SSO cutover affects every employee simultaneously and a bad cutover locks people out of everything at once. Many companies keep Microsoft 365 for email and use Zoho for everything else, which is a perfectly sound architecture and often the lower-risk path.

COMMON QUESTIONS

HR & Operations FAQs

The questions that come up when teams evaluate this part of the suite.

Can Zoho Creator really replace custom development?

For internal business applications, frequently yes — and that is a genuinely underrated part of Zoho One. Creator handles data models, forms, workflows, role-based permissions, reports, and mobile apps without writing much code. The equipment tracker, the inspection log, the approval process specific to your industry: these are exactly what it is for.

It is not the right tool for customer-facing products, anything needing a highly bespoke interface, or systems with serious real-time or scale demands. The advantage over Airtable or Retool is not raw capability — it is that a Creator app shares users, permissions, and data with your CRM and accounting rather than sitting beside them.

Is Zoho People a full HRIS or just a time-off tracker?

A full HRIS: employee records, org charts, attendance and shift scheduling, timesheets, performance management with goals and review cycles, onboarding and offboarding workflows, document management, and a self-service portal.

Where it is thinner than a dedicated enterprise HR platform: sophisticated compensation planning, succession planning, and some deep compliance reporting for large regulated employers. For companies under a few hundred employees it covers the ground comfortably.

How does the SSO and device management actually work?

Zoho Directory is the identity layer for the whole suite. It supports SAML SSO with third-party identity providers, syncs with Active Directory, enforces MFA policies, and assigns app access conditionally by role or department.

The device management side handles enrollment, policy enforcement, and remote wipe for company devices. The practical payoff is the one in the workflow above: provisioning and de-provisioning happen once, for all 45 apps, instead of once per application.

Can Desk handle a real support operation?

Yes for most support organizations. Omnichannel queues, SLA policies with escalation, round-robin and skill-based assignment, a knowledge base with a customer portal, satisfaction surveys, and workflow automation are all standard.

Zendesk still has a larger third-party app marketplace and more mature enterprise features at the very top end. The compensating advantage is meaningful, though: every ticket in Desk carries the customer's CRM and billing context inline, without buying and maintaining an integration to get it there.

What if our process doesn't fit any of these apps?

Then you build it in Creator, and that is a normal outcome rather than a failure of the platform. Nearly every implementation we run includes at least one custom application for something genuinely specific to that business.

That is the actual argument for a platform over a collection of tools: when the off-the-shelf app does not fit, you are not stuck choosing between contorting your process and buying a sixteenth vendor.

Onboard in an Afternoon. Off-board in Five Minutes.