Leaving Darwinbox without losing the record

Leaving Darwinbox is an enterprise extraction before it is a migration, and it has two outputs, not one. The first is your data: the directory, the payroll history, the filed returns, the documents. The second is your configuration: the workflows, approval chains, custom fields and letter templates that someone spent an implementation shaping to how you work. The data you can export. The configuration you have to write down, because it leaves as knowledge rather than as a file, and rebuilding it is most of the work of standing up whatever comes next.

One note on sourcing. What follows about Darwinbox’s own product is our reading of their public material, read in September 2026, and gathered through search because direct access to their help sites is blocked from where this was written. Their documentation 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 is about your obligations and your data, which do not move when a vendor ships a redesign.

Start by asking who holds your configuration

This question comes first for an enterprise HCM, and it is the one most likely to be answered wrongly. Enterprise HR is frequently configured, and sometimes run, with an implementation or managed-services partner rather than by the in-house team alone. If that describes you, your data conversation has two counterparties:

• The software relationship. Whose subscription it is, who the account owner is, and who receives the renewal.
• The configuration and operations relationship. Who built the workflows and who runs the monthly cycle. That party may be the only one who can hand over the configuration in a usable form, or generate the reports you need.

Write down which company holds which obligation before you do anything else, and get the report set and the year-to-date pack in writing while the relationship is still warm. After notice you are negotiating with less leverage than you will ever have again.

What you are actually moving

• The directory, with every custom field. On a configured system this is wider than a standard export, so take every column you can select.
• Payroll output, per closed period, meaning the pay register and the payslips for each run, held for every market you process in.
• Statutory output, per period, meaning the returns you actually filed, their challans and acknowledgements, and the year-end forms for each completed year, for each country.
• Performance and goals, the review and appraisal history, which is rarely one clean export.
• Leave balances and policies, the numbers and the accrual rules that produced them.
• Documents, everything uploaded to a profile.
• The configuration itself, written down: workflows, approval chains, letter and email templates, custom fields and the logic behind them.
• The year-to-date position, per person, the running totals that carry through the tax year, in each country you run payroll in.

The export checklist, in order

Do all of this while the account is active and paid, and while any partner relationship is intact.

1. Directory first, full master with every custom field, as your index.
2. Pay registers and payslips, per closed month, per country, filed by month.
3. The statutory set, per period, each return paired with its challan or acknowledgement, and the year-end forms per completed year.
4. Performance and goals, exported as far back as you want to carry. Test on one person first.
5. Leave balances and policies, the numbers exported and the rules written out in words.
6. Documents, tested on one profile before you size the job across headcount.
7. The configuration, captured in writing. Walk every workflow and approval chain and record it in plain language, with screenshots where a path is complex. This is the single most valuable artefact you will take, because it is the specification for rebuilding, and nobody can generate it for you after the account closes.
8. The year-to-date pack, which you have to ask for, one spreadsheet per country, one row per person, reconciled against your filed returns and your bank before you accept it.

Timing: the tax year decides, not your renewal date

For each country you run payroll in, the cheapest boundary is the start of that country’s tax year, with everyone at zero year to date and the prior year closed end to end by the system that computed it. The next best is straight after a filing period has been reconciled. The window to avoid is the year-end run-in, when reconciliation and the year-end forms land together and carry statutory deadlines the migration does not. An enterprise with people in several countries will not have one neat boundary, so sequence the payroll cutover country by country and hold the record move separate from it.

The separation that makes a staged move possible

The system that holds your records and the system that computes your payroll do not have to be the same system, and on a multi-country enterprise move that separation is what lets you stage the work instead of attempting one cutover across every market at once. Move the record when it suits you; change who computes at each country’s tax-year boundary.

That separation is Capstan’s default. 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 in any country, 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.

Where it tends to be hard

The configuration is the project. On a lightly configured product the data is the work. On a configured enterprise HCM the data comes out and the configuration does not, so budget most of your time for rebuilding the workflows, not for moving the records.

History flattens. A directory export gives you today’s salary, grade and manager and nothing behind them. Pull whatever change-history report exists as a separate step; after cancellation the answer to “can we still see the old figure” is no.

Multi-country means multiple statutory sets. Each market has its own filings, its own year-end and its own retention rules. Treat each one as its own export and its own timing decision.

Access ends on a schedule. Read your contract for the retrieval window and the deletion process, diarise both, and finish your export well before the first.

What you have to keep, whoever you buy from

Employment and tax records carry retention obligations that follow the employer, not the software, and they differ by country and by statute. Payroll registers, filed returns and their challans, year-end forms, and the registers each jurisdiction requires all have to be kept for periods your accountant, not any vendor, should confirm. Keep your own dated archive outside any vendor, a folder per country and tax year, sub-foldered by month. Records you hold are records nobody can revoke, suspend or reprice.

Standing up the replacement

Use the implementation checklist for the general order, and read this as the overlay. Validate the export first: open the files, confirm payslip counts match headcount, confirm register totals tie to your bank. Load the new system in parallel while the old one is live. With Capstan that is a spreadsheet import with a dry run that previews every row and fails bad rows individually; documents load per person, opening leave balances are entered as adjustments with a reason, and effective-dated history is not imported, so your export stays your archive of it. What imports and what does not is written out in full. Set one go-live date per entity, hand your payroll partner a past month of inputs per country and compare, and reconcile ten people by hand across locations and pay structures before you cancel.

Who should stay where they are

Be fair to the product you are leaving. An enterprise HCM that carries a deeply configured lifecycle across many countries, with computed payroll and statutory content maintained by the vendor, is doing a large, specific job, and if that scale and configurability are the centre of your operation, staying is a reasonable answer and we would say so in your position. A lean, record-first system with partner-integration payroll is a different shape. It suits teams who have decided the enterprise suite is heavier than they need, who want a portable record and a price they can total themselves, and who work with a payroll partner by choice. It does not suit an organisation that genuinely needs enterprise-scale configuration. The Darwinbox comparison sets the two published models side by side, including where Capstan is the wrong tool, and statutory payroll in India is the conceptual map if India is one of your markets.

Where to go next

If you run in more than one country, multi-entity HR covers holding one record across entities. Whatever you buy, start your shortlist with the export is the habit worth keeping, and read how to read an HR pricing page before you compare totals so you get every candidate’s all-in number at your real headcount. Capstan’s figures are on one public pricing page.