Skip to content
KuzhuHRMS Software

Switching to Kuzhu

Moving is a month.
Week three is the proof.

Whatever you run HR on today, the move follows one shape: we import what you have, configure your rules rather than our defaults, run one payroll in parallel and reconcile it to the rupee, and only then do you switch.

Plan my migration Where are you coming from?
  • No setup fee
  • No data retyped
  • Nobody switches on faith
A team reviewing the parallel payroll run together

4 weeks

from first call to first live payroll

1 parallel run

reconciled to the rupee before you switch

0 rows retyped

everything comes in through a validated import

90 days

to export everything after you leave, if you ever do

What stays exactly as it is

A migration is a month because most things do not move.

The parts of your setup that already work are connected, not replaced. That is the whole difference between a month and a project.

Your biometric devices

The machine at the gate keeps sending punches. It is repointed, not replaced.

Your accounting system

Tally or whatever you post to receives the same journals it does today.

Your policies

Leave rules, shifts, pay components and approval chains are configured to match, not replaced with defaults.

Your bank

Salary files go out in the format your bank already accepts.

Where you are coming from

Pick your starting point.

The source only changes what the import reads and which worry comes up first. Everything underneath is the same month.

Coming from

Spreadsheets

A muster in one file, a salary sheet in another, and a leave register that agrees with neither.

Takes
2 to 3 weeks
You keep
Your existing sheets, as the starting data.
Talk about moving from Spreadsheets

What changes

  • Your sheets become the first import, validated row by row before anything goes live
  • Attendance, leave and payroll read one employee record instead of three files
  • Employees see their own balances and payslips, so HR stops being asked

What people ask first

“Our sheets are a mess. Will the import cope?”

That is what validation is for. Every row is checked before it lands, and you get a list of exactly what is wrong and where. Most companies fix it in an afternoon.

“We have years of history in Excel.”

Bring balances and the last twelve months of salary; older history can stay archived. Nothing is lost, and nothing has to be retyped.

Coming from

Tally payroll

Payroll inside the accounting package, with attendance and leave collected by hand every month.

Takes
3 to 4 weeks
You keep
Tally for the books. Kuzhu posts to it.
Talk about moving from Tally payroll

What changes

  • Salary structures and statutory rules recreated, then checked in a parallel run
  • Attendance and leave flow into the run instead of being keyed in
  • Payroll journals export back into Tally each month, so accounting does not change

What people ask first

“Our accountant lives in Tally.”

They keep living there. Payroll journals export in a shape Tally posts without retyping, so accounting does not change at all.

“Statutory is already set up in Tally.”

We recreate PF, ESI, PT and TDS in Kuzhu and prove them in the parallel run, so the first live month matches what Tally would have produced.

greytHR logo

Coming from

greytHR

A working HRMS, but modules that still need exports between them and a payroll you double-check.

Takes
4 weeks
You keep
Your devices, your policies, your pay components.
Talk about moving from greytHR

What changes

  • Employee master, leave balances and salary history imported from your export
  • One parallel payroll reconciled to the rupee before you switch
  • Biometric devices repointed, not replaced

What people ask first

“We have a biometric machine wired to it.”

The device keeps sending punches; it just sends them to Kuzhu. ESSL, Realtime and any device that can push will do.

“Leave balances are mid-year.”

Opening balances come in as of the switch date, with the accrual rule taking over from there. The employee sees the same number the day after.

Keka logo

Coming from

Keka

Most of HR in one place, priced per module, with a payroll month that still takes a week.

Takes
4 weeks
You keep
Everything you can export, which is everything.
Talk about moving from Keka

What changes

  • Employee, attendance and payroll data imported from your export
  • Approval chains rebuilt the way you already run them
  • Your own database and your own domain, from day one

What people ask first

“Our approval chains are complicated.”

Complicated is normal. Chains are rebuilt by amount, department and role, with delegation for absences, and every decision stays on the record.

“Will payroll match?”

Week three is a full parallel run reconciled to the rupee. If a component differs, it is found there, not in a payslip.

Zoho People logo

Coming from

Zoho People

HR in Zoho, payroll somewhere else, and statutory returns assembled at month end.

Takes
4 weeks
You keep
The rest of your Zoho stack. Kuzhu has an API.
Talk about moving from Zoho People

What changes

  • Employee records and leave history imported
  • PF, ESI, PT and TDS computed inside the payroll run rather than after it
  • Registers, challans and returns produced from the same numbers as the payslips

What people ask first

“We use the rest of the Zoho stack.”

Keep it. Kuzhu has a documented REST API and webhooks, so CRM and books keep talking to HR.

“Payroll is somewhere else entirely.”

That is usually the reason people move. In Kuzhu, statutory is computed inside the run, and the registers come from the same numbers as the payslips.

How the data actually moves

“We migrate your data” means nothing. Here is what it means here.

  1. 01

    Export what you have

    A spreadsheet, or the export from your current system. Employees, salary structures, leave balances, open loans.

  2. 02

    We validate every row

    Missing PAN, a bank account with the wrong length, a date of joining after the confirmation. You get a list, not a surprise.

  3. 03

    You fix, we help

    Most fixes take an afternoon. Anything structural, like a pay component with no equivalent, we sort out on a call.

  4. 04

    Import into your own database

    Not a shared table. Your company, its own database, your own domain from day one.

  5. 05

    Run payroll twice

    Once where you run it now, once in Kuzhu. The two are reconciled line by line before anyone relies on the new one.

  6. 06

    Switch

    Employees get the app, managers get their approvals, and support stays on the phone for the first live month.

The same month, every time

What the four weeks look like

  1. Day 1

    Your workspace exists

    We create it while we are on the call. You sign in, see your company name on it, and start adding people.

  2. Week 1

    Your data comes across

    Employees, salary structures, leave balances and open loans, imported from spreadsheets or your old system. We show you what needs fixing before anything goes live.

  3. Week 2

    Rules, not defaults

    Your leave policy, your shifts, your approval chains and your pay components — configured to match how you already work, rather than how the software assumed.

  4. Week 3

    One parallel payroll

    We run your next payroll here as well as wherever you run it now, and reconcile the two rupee for rupee. Nobody switches on faith.

  5. Week 4

    Everyone else joins

    Employees get their app, managers get their approvals, and HR stops being the bottleneck. Support stays on the phone for the first live run.

The parallel run, from someone who did it

“We ran it in parallel for a month before switching. The numbers matched to the rupee, which is the only reason our CFO agreed to move.”

Anita Deshpande

Finance Controller, IT services

The honest bit

What you are
probably thinking.

The doubts that end most conversations are usually the ones nobody says out loud. So let's answer them directly.

It is a month, and week three is a parallel payroll run against your current system so you can see the numbers agree before you commit. Nobody is asked to switch on faith.

Most are. Pay components are yours to define — formulas, caps, prorating and which ones attract PF, ESI or tax. If a rule cannot be expressed, we would rather tell you on the call than after the invoice.

Applying for leave takes two taps and downloading a payslip takes one. HR gets a working session; nobody else needs training, and the ones who do get a two-minute guide.

You can export everything you own, in formats you can open, at any time — and for 90 days after you leave. A system you cannot walk away from is not one you should walk into.

Still have a question we haven't covered?

Call +91 82093 73274

Bring the export. We will show you the import.

Thirty minutes with your real data, and an honest answer on whether the move is worth it.

Book a demo +91 82093 73274