Migrating Onto TriblockHR

Moving from a spreadsheet or another payroll system mid-year. The order, the data you bring, and the one safeguard that catches mistakes before employees do.

The shape of a migration

A migration is configuration plus three loads of historical data: your people, their leave balances, and their year-to-date pay figures. Do the setup sequence first so there's somewhere for the data to land, then load in this order.

Step by step

1. Configure first. Payroll country, org structure, employment levels, pay codes, allowance/deduction catalogs, time-off types and policies, payroll groups. The Setting Up TriblockHR guide is the full sequence.
2. Load your people. Create employees individually for a small team, or by bulk import for a large one — each with compensation, pay frequency, tax identifiers, time-off policy, and bank account.
3. Load opening leave balances. Use the bulk balance import with an effective date, so everyone starts with the leave they'd already accrued under the old system — not zero.
4. Load year-to-date figures. If you're going live partway through the year, the prior earnings, tax, and statutory contributions matter — annual caps and tax certificates depend on them. Bring the YTD totals over per employee so the rest of the year, and the year-end filings, reconcile. Talk to your TriblockHR contact about the right load method for your numbers.
5. Set the year-to-date start date in account settings so the system counts the year from the right point.
6. Parallel run. Run your first month in TriblockHR and your old system, then reconcile gross, statutory, and net per employee. This is the safeguard — see below.

What you don't need to bring

You don't have to migrate full historical payslips or closed pay runs — those stay in your old system as the record for periods before go-live. What TriblockHR needs is the opening position: who's employed, what they're owed in leave, and where their year-to-date numbers stand. The platform builds everything forward from there.