Leaving greytHR without losing the record

Leaving greytHR is a reporting exercise before it is a migration. Almost everything you need exists as a report you can generate and download, so the work is not extracting it, it is knowing the full list and running it before your access ends. The two things that catch teams out are the year-to-date payroll position, which is not a single named report anywhere, and the timing, because the Indian financial year sets the boundary rather than your renewal date.

One note on sourcing before anything else. What follows about greytHR’s own product is our reading of their public help material and product update notes, read in August 2026, and gathered through search because direct access to their help sites is blocked from where this was written. Their help centre is the authority, screens move between releases, and you should confirm the current article before planning a week of work around a menu path. Everything else here concerns your obligations and your data, which do not change when a vendor ships a redesign.

Start by asking who actually holds your payroll

This question comes first for greytHR specifically, and it is the one most likely to be answered wrongly.

greytHR’s own admin help describes a workflow for payroll service providers: material about using customers’ data inputs, sharing report output with customers, and customers downloading reports and data shared by their provider (admin-help.greythr.com, read August 2026). That tells you something useful about the market the product serves. A large number of Indian businesses do not run payroll themselves. They engage a payroll service provider or a chartered accountant who processes it, and the software sits between them.

If that describes you, your data conversation has two counterparties and you should identify both before you do anything else:

• The software relationship. Whose subscription is it, who is the account owner, and who receives the renewal invoice.
• The processing relationship. Who runs the payroll, who holds the working papers, who signs the returns, and whose digital signature is on the Form 16 set.

Write both down. Then ask the processing party, in writing, for the full report set and the year-to-date pack described below. A provider who has done the work will produce it. A provider who resists is telling you something important about the relationship, and it is better to learn it now than in March.

What you are actually moving

• The directory. Who works here, in what capacity, at which location and under which entity. Your master index.
• Salary information. The current structure per person, and the revision history behind it.
• Payroll output, per closed month. The registers and the payslips, meaning the human-readable record of what you actually paid.
• Statutory output, per period. The PF and ESI returns, the professional tax statements, the income tax reports behind your quarterly TDS returns, and the remittance details for each, meaning bank, amount, date and filing location.
• The Form 16 set for each completed year, plus the annual computation behind it.
• Documents. Contracts, letters, forms, identity and education papers, anything held against a profile.
• Balances and policies. Leave balances as at your cutover, and the accrual rules that produced them.
• The year-to-date position, per person. This is rarely a single named report in any product, and it is the pile that costs you money if you skip it.

The export checklist, in order

Run all of it while the account is live and paid. Access to reports is a function of your subscription in every product.

1. Directory first, then salary. greytHR’s admin help describes a reports gallery under the reports section, where reports are generated by category and downloaded in spreadsheet, PDF or document formats, and a recently generated reports view alongside it; employee salary details are exported to a spreadsheet from the employee information area (admin-help.greythr.com, read August 2026). Take both. The directory is your index and the salary export is what you check every payroll figure against.
2. Work the reports gallery systematically, not by memory. This is the single most important habit for this migration. Open the gallery, go through each category rather than each report you happen to remember, and download everything that carries a fact you would miss. Payroll registers, payment registers, payroll control and difference reports, leave balance as at a date, attendance, claims, income tax. Save each one with its period in the file name, because a folder of reports named “report” helps nobody in eighteen months.
3. Payslips, by month. greytHR’s product updates describe employees downloading multiple payslips for a chosen period as a zip file or having them emailed, from the self-service portal (product-updates.greythr.com, read August 2026, describing a mid-2025 release). Whichever route you use, file payslips by month rather than by person. That is how anyone will ask for them later.
4. The statutory set, as filed. greytHR’s help material describes generating the PF electronic challan cum return from the reports gallery, income tax related report views, and a remittances area where the challan details of monthly statutory payments such as PF, ESI and professional tax are recorded (admin-help.greythr.com and support.greythr.com, read August 2026). Take the return and its challan together. The return alone is only half the evidence.
5. Form 16, both halves. greytHR’s help material describes Part A files being downloaded from TRACES and uploaded, with Part B generated from the payroll (support.greythr.com and admin-help.greythr.com, read August 2026). Keep three things: the TRACES source files, the issued documents, and the annual computation behind Part B. The first is recoverable from TRACES. The third is not.
6. Documents. greytHR’s product updates describe a bulk download of employee documents, letters and forms for one or more employees, delivered as a single zip through a download centre where the prepared file remains available for a limited period before it is removed (product-updates.greythr.com, read August 2026). If that is available to your user role, use it, and download the prepared archive promptly rather than leaving it sitting in the centre. Check the extracted file count against your headcount before you call it done.
7. Balances and policies. Export current balances, then write the accrual rules down in plain words. You will be keying both in somewhere.
8. The year-to-date pack, which you have to ask for. See below.

The pack nobody exports until it is too late

Whoever computes your payroll after the move has to continue the financial year rather than restart it. Restarting it means the tax deducted for every person for the rest of the year is wrong, and then corrected in March under deadline pressure.

Ask for one spreadsheet, one row per person, in these words:

• PAN, employee code, date of joining, and date of leaving where it applies
• UAN and PF member ID, and the ESIC insurance number where the person is covered
• Year-to-date gross, broken out by pay component rather than as one figure
• Year-to-date employee and employer contributions by head: PF, ESI, professional tax, labour welfare fund where it applies
• Year-to-date tax deducted, and the projected annual tax the last run was working to
• The tax regime each person elected for the year
• Investment declarations on file, and which proofs were accepted rather than merely submitted
• Previous-employer income and tax already taken into account for anyone who joined mid-year
• Perquisite values in progress
• Loss of pay days, arrears and prior-period adjustments already processed
• Outstanding recoveries: loans, advances, notice pay, asset recoveries

Then reconcile it. The year-to-date tax should tie to the TDS you have actually remitted, and the gross should tie to the registers you exported. A pack that does not tie to what you filed is a pack that will be argued about later.

Timing: the financial year decides, not your renewal date

The cheapest boundary is 1 April. Everybody starts at zero year to date, the previous year closes with one party responsible for it end to end, and the Form 16 for that year comes out of the system that computed every month of it. If you can wait for that boundary, wait.

The next best is immediately after a quarter has been filed and reconciled, because the quarterly TDS return is the unit the year is assembled from.

The window to avoid is the January to March run-in, when proof collection, the annual reconciliation and Form 16 production land together. A vendor change in that window competes for the same weeks as work that has a statutory deadline, which your migration does not.

When a mid-year move is worth it anyway. Waiting is the default, not a rule. Move mid-year when the present arrangement is failing, meaning filings have been late, corrections are routine, or nobody answers when a person’s pay is wrong. Move when a corporate event forces it, such as a new entity, an acquisition or a change of TAN, which is a far bigger reset than any change of software. Move when a renewal would otherwise commit you to another full year of something you have already decided against. And move when the cost of staying is being paid every month in manual work by someone whose time you are not counting. In each case the mid-year friction is the smaller number, and you should be able to say which number you chose.

Whichever date you pick, put the split in writing before anything is cancelled: which party files which return, for which period, and who issues Form 16 for the year in progress. That email is the cheapest insurance in the project.

The change that is smaller than it looks

There is a structural way to reduce a mid-year move, and it is worth understanding whichever vendor you choose next.

The system that holds your records and the system that computes your payroll do not have to be one system, and they do not have to change on the same day. Separate them and you can move the record when it suits you and change who computes at the year boundary, because the year-to-date arithmetic stays put. Two small changes on two sensible dates beat one large change on a date chosen by an invoice.

That separation is Capstan’s default rather than a workaround. Capstan compiles joiners and leavers, pay structures, leave, attendance and adjustments into a documented export for your payroll partner, and files the results the partner returns back onto each employee record. It holds no rate, slab, bracket, threshold or formula, computes no gross to net, and files nothing with any authority. The payroll module sets out what crosses the line in each direction, and why payroll should be a partner is the reasoning behind it. If you are weighing this against a suite built the other way round, payroll-first HR systems describes that shape plainly.

Where it tends to be hard

Completeness, not mechanics. When most facts live in a report gallery, the risk is not that a download fails. It is that you never ran the report at all, because nobody remembered it existed. Work the categories, not your memory, and tick them off a written list.

Prepared files expire. Where an export is assembled in the background and left in a download area, it is available for a window rather than forever. Download it to your own storage the moment it is ready. A file sitting in a vendor’s download centre is not your archive.

History flattens. A directory export gives you today’s salary, designation and manager and nothing behind them. Run the revision or history views separately. After cancellation, the answer to “can we still see the old figure” is no, in every product.

Leave balances mean nothing without their policy. A balance is the output of an accrual rule, and no two systems model accrual identically. Export the numbers, write the rules in words, expect to key opening balances in by hand.

Access ends on a schedule. Published terms in this category commonly require advance written notice to close an account, bill through to closure, and allow a limited retrieval window before deletion. Read your own contract for the dates, diarise all three, and finish the export well before the last one. Do not plan around a support exception you have not been granted in writing.

What you have to keep, whoever you buy from

Part of this is not a migration question at all. Indian employment and tax records carry retention obligations that follow the employer rather than the software: payroll registers, the returns you filed and their challans, Form 16 issued to each person, PF and ESI records, and the registers required under the shops and establishment or factories rules that apply to you. The periods differ by statute and change over time, so confirm them with your chartered accountant rather than with any vendor, ourselves included.

The practical consequence survives every switch: keep your own dated archive outside any vendor. A folder per financial year, sub-foldered by month, holding the registers, payslips, returns, challans and the Form 16 set. Build it whether or not you are switching. Records you hold are records nobody can revoke, suspend or reprice, and the day you need them is never a day you planned for.

Standing up the replacement

The order to configure a new system in, what to set up before you load anybody and what to test before you invite the team, is a checklist of its own: keep the implementation checklist open alongside this and read the steps below as the payroll-specific overlay.

1. Validate the export first. Open the files. Confirm the payslip count per month matches the headcount you actually paid, and that register totals tie to your bank. A file that will not open is not a backup.
2. Load the new system in parallel, while the old one is live. With Capstan that is a spreadsheet import for people, previewed by a dry run that shows exactly what would land and fails bad rows individually rather than sinking the batch. Be clear about what does not import: documents load per person, opening leave balances are entered as adjustments carrying a reason, contractors are created individually as their own identity class, and effective-dated history is not imported at all, so your export stays your archive of it. What imports and what does not lists this in full, and asking every other vendor the same question in the same words is the fastest honest comparison you can make.
3. Set a go-live date before anyone marks attendance. One company-wide date means working days before it count as not expected rather than absent, so a parallel run never becomes loss of pay on the first payroll you compile.
4. Give your payroll partner one period of inputs and compare. Compile a month you have already paid under the old system, hand over the export, and check the partner’s output line by line against the register you exported. If those agree, your inputs are right. The payable days calculator helps while checking prorations, and the CTC breakdown calculator while checking structures.
5. Reconcile ten people by hand, across different locations, entities and pay structures, including one joiner and one leaver. If those ten are right, the bulk probably is.
6. Cancel only after a full cycle has run cleanly and every register, return, challan and document is in the archive you control.

Who should stay where they are

Be fair to what you are leaving. A long-established India payroll and HR suite that computes statutory deductions, produces the returns, and carries the year through to Form 16 inside one login is doing a large and specific job. If payroll processing is the centre of your operation, if a service provider works inside it every month and that relationship is working, or if your team has years of muscle memory in it, the cost of change is a real number and it may well be the larger one. Count it honestly, including the hours nobody invoices you for. The real cost of switching HR systems is written for exactly that calculation.

A record-first system with partner-integration payroll is a different shape. It suits teams whose priority is a clean, portable system of record, who already trust a payroll partner or chartered accountant with the computation, or who expect to operate in more than one country and do not want an engine per jurisdiction. It does not suit a team that wants the software itself to compute and file. That is the design rather than a gap awaiting a release, and pretending otherwise would waste your time. The greytHR comparison puts the two published models side by side, including where Capstan is the wrong tool.

There is one more thing worth weighing that has nothing to do with features. Whatever you buy next, hold it to the test the last one set: what does it hand you on the day you leave, in what container, does it include the original document files, is there a manifest whose row counts you can check the archive against, and does the export still work if a payment lapses. Capstan’s export is one archive of documented JSON, a matching CSV and your original files, with a manifest, and it deliberately sits outside the billing check, so an unpaid invoice cannot stop you taking your data. Ask every vendor those four questions in those words. Its figures sit on one public pricing page, adjusted by country, and the complete core is on every plan including the free one.

Where to go next

If you want the components themselves explained, statutory payroll in India is the conceptual map, and the HR compliance calendar sets out what falls due when, which is what your timing decision is actually made of. If the move coincides with exits, the full and final settlement guide covers the calculation and who does which part. And the switching pillar covers the sequence that applies whichever tool you are leaving.