How to Migrate Leave Balances Into a New Singapore HR System

Introduction

Moving employee leave records from spreadsheets, paper forms or an existing HR platform into a new Human Resource Management System (HRMS) requires careful planning. Leave balances affect employee entitlements, approval decisions, payroll inputs and workforce scheduling. If the migration is inaccurate, employees may see incorrect balances, managers may approve leave based on outdated information, and HR teams may spend considerable time correcting records.

For Singapore businesses, leave migration also needs to account for different leave categories, statutory entitlements, company-specific policies, carry-forward arrangements and part-time employee calculations. A successful migration should transfer not only the final balance but also the information needed to explain how that balance was calculated.

The best approach is to audit existing records, standardise leave policies, prepare a clean employee data file, test calculations, reconcile balances and obtain formal approval before switching to the new system.

1. Review the Existing Leave Records Before Migration

The first step is to identify where the organisation currently stores leave information.

Records may be spread across:

• Excel or Google Sheets.
• Paper leave application forms.
• Email approval conversations.
• An existing HR or payroll system.
• Attendance management software.
• Department-level leave trackers.
• Historical employee records maintained by HR.

Collect the latest available records from every relevant source. Do not assume that one spreadsheet contains the complete leave history.

HR should identify the following information for each employee:

Information	Why it is needed
Employee ID	Links leave records to the correct employee
Employee name	Helps identify and validate records
Employment start date	Supports eligibility and service calculations
Employment status	Identifies active, inactive and separated employees
Leave category	Separates annual, sick, childcare and other leave
Annual entitlement	Establishes the employee's applicable allowance
Leave taken	Identifies approved leave already used
Pending applications	Prevents requests from being lost during migration
Carry-forward balance	Preserves eligible unused leave
Manual adjustments	Explains corrections to previous balances
Leave year	Identifies the period to which each balance relates

The organisation should also record the source of each balance, such as an HR spreadsheet, payroll report or approved adjustment form.

2. Identify All Leave Categories Used by the Business

Before importing balances, create a standard list of leave categories in the new HR system.

Singapore businesses may manage several statutory and contractual leave types.

Leave category	Migration consideration
Annual leave	Import entitlement, leave taken, current balance and eligible carry-forward
Outpatient sick leave	Preserve the relevant entitlement and usage records
Hospitalisation leave	Keep the correct entitlement and usage classification
Maternity leave	Preserve applicable leave records and approved periods
Paternity leave	Retain the applicable entitlement and usage information
Shared parental leave	Preserve the relevant leave category and approved records
Childcare leave	Distinguish applicable childcare leave categories
Extended childcare leave	Keep separate from ordinary childcare leave where applicable
Unpaid leave	Record approved periods separately from paid leave
Compassionate or marriage leave	Treat according to the company's contractual policy
Time off in lieu	Preserve separately if the organisation operates this arrangement

Do not combine different leave types into a single generic balance. For example, annual leave and childcare leave have different eligibility and usage conditions. Similarly, outpatient sick leave and hospitalisation leave should not be treated as interchangeable categories.

The new system should reflect the employer's actual policies and the applicable statutory rules.

3. Confirm the Applicable Leave Policies and Entitlements

A migration is an opportunity to review whether the existing leave configuration is correct.

For annual leave, HR should check each employee's eligibility, length of service, contractual entitlement and applicable carry-forward arrangement. Under the Employment Act, eligible employees generally qualify for statutory annual leave after three months of continuous service. The minimum entitlement starts at seven days in the first year and increases by one day for each subsequent year of service, up to 14 days from the eighth year onwards.

The organisation should also distinguish between statutory entitlements and additional contractual leave. An employee may receive more annual leave than the statutory minimum under the employment contract or company policy.

For sick leave, verify eligibility and the applicable outpatient and hospitalisation entitlements. Eligible employees generally receive graduated statutory entitlements after three months of service, increasing with completed service up to the applicable six-month entitlement.

For childcare and parental leave, verify the employee's eligibility and the applicable scheme conditions rather than simply importing a balance from an old spreadsheet.

Before migration, HR should document:

• The leave categories used by the company.
• The applicable entitlement rules.
• The leave year or entitlement period.
• Accrual frequency and calculation method.
• Proration rules for new joiners and employees leaving during the year.
• Carry-forward rules and expiry dates.
• Treatment of part-time employees.
• Rules for half-day or hourly leave.
• Approval requirements.
• Company-specific benefits above statutory minimums.

This prevents incorrect historical settings from being carried into the new platform.

4. Separate Opening Balances From Leave Transactions

One of the most important migration decisions is whether to import only the current balance or the full leave transaction history.

An opening balance represents the employee's leave available at the migration cut-off date. A transaction history explains how that balance was reached.

For example:

Annual leave calculation	Days
Opening balance at start of leave year	4
Entitlement credited during the year	14
Additional approved adjustment	1
Approved annual leave taken	-5
Available balance before migration	14

The new system should receive the final balance of 14 days, together with the supporting information wherever historical data is available.

Importing only the final figure may be sufficient for some organisations, but it can make later audits and employee queries difficult. Where practical, transfer historical transactions as well.

A good migration file should distinguish:

• Opening balance.
• Leave credited.
• Leave taken.
• Leave cancelled or reversed.
• Manual adjustments.
• Carry-forward.
• Expired or forfeited leave, where legally and contractually permitted.
• Final available balance.

The new system should not calculate a second entitlement on top of an already imported opening balance unless that is part of the agreed migration design.

5. Check Annual Leave Carry-Forward Rules

Carry-forward balances require particular attention because different employees may be subject to different arrangements.

For employees covered by Part 4 of the Employment Act, unused statutory annual leave must generally be carried forward and taken within the following 12 months. MOM identifies the relevant coverage by reference to workmen earning a monthly basic salary of S2,600 or less.

For employees outside Part 4, the treatment of unused annual leave should be checked against the employment contract and company policy. Additional contractual leave above statutory entitlements may also have different treatment.

During migration, HR should record:

• The number of days carried forward.
• The leave year in which the days were earned.
• The applicable expiry date.
• Whether the balance is statutory or additional contractual leave.
• Any approved exception or extension.
• The policy or contractual basis for the treatment.

For example, an employee may have 3 days carried forward from the previous leave year and 10 days available from the current year's entitlement. The new HR system should preserve these as separate balance components if they have different expiry or usage rules.

Do not apply one universal expiry rule to every employee's annual leave balance.

6. Prepare a Standardised Employee Leave Migration File

After reviewing the existing records, prepare a structured spreadsheet or CSV file for importing into the new HR system.

A typical migration file may contain the following columns:

Field	Example
Employee ID	EMP001
Employee name	Alex Tan
Employment start date	15 January 2022
Leave category	Annual Leave
Leave year	2026
Annual entitlement	14 days
Leave credited	14 days
Leave taken	5 days
Carry-forward	3 days
Adjustments	0 days
Available balance	12 days
Carry-forward expiry	31 December 2026
Source record	HR leave tracker
Verified by	HR administrator

The figures are illustrative. The actual fields should match the new system's import template and the company's leave policy.

Before importing, standardise:

• Employee IDs and names.
• Date formats.
• Leave category names.
• Decimal precision.
• Units of measurement.
• Leave year definitions.
• Balance signs and adjustment descriptions.
• Blank and missing values.

For example, one spreadsheet may use "AL", another may use "Annual", and a third may use "Annual Leave". These should be mapped to one consistent category in the new platform.

7. Handle Part-Time and Shift-Based Employee Balances Carefully

Part-time employees and employees working different shift patterns may have leave entitlements that cannot be migrated accurately by copying full-time day balances.

Under Singapore's part-time employment rules, statutory leave entitlements such as annual leave and sick leave are calculated in hours based on the employee's annual working hours relative to a comparable full-time employee. The applicable leave pay also depends on the employee's working hours.

For employees working long shifts, one leave day may represent the employee's actual scheduled working day. MOM gives the example of a 12-hour shift, where one day of annual leave is equivalent to 12 hours.

Before migration, HR should verify:

• Whether the new system stores leave in days or hours.
• The employee's normal working schedule.
• The comparable full-time working hours, where relevant.
• The employee's annual working hours.
• The conversion between days and hours.
• The treatment of variable shifts and part-day leave.

For example, an employee who works four hours per day should not automatically receive the same number of leave hours as an employee who works eight hours per day.

Where the old system stores leave in days but the new system uses hours, convert balances using the employee's applicable working schedule and entitlement rules. Keep the original values and calculation method for audit purposes.

8. Map Old Leave Categories to the New HR System

Different HR platforms may use different names and configurations for the same type of leave.

Create a category mapping sheet before importing records.

Existing system category	New HR system category
AL	Annual Leave
MC	Outpatient Sick Leave
Hospital Leave	Hospitalisation Leave
Maternity	Maternity Leave
Paternity	Paternity Leave
Childcare	Childcare Leave
Extended Childcare	Extended Childcare Leave
NPL	Unpaid Leave
C-Off	Compensatory Time Off

The mapping should be reviewed by HR and the system administrator.

Pay particular attention to categories that have similar names but different eligibility requirements. Do not map all medical leave into one category if the new system distinguishes outpatient and hospitalisation leave.

Similarly, distinguish statutory leave from company-specific benefits so that reports and entitlement calculations remain meaningful.

9. Clean Duplicate, Missing and Incorrect Records

Historical leave data often contains errors. Migrating without cleaning the records may transfer these problems into the new system.

Common issues include:

• Duplicate leave applications.
• Approved requests recorded as pending.
• Cancelled requests still deducted from balances.
• Missing approval dates.
• Incorrect employee IDs.
• Leave recorded under the wrong category.
• Negative balances without explanations.
• Inconsistent half-day calculations.
• Incorrect carry-forward figures.
• Leave transactions entered twice in different spreadsheets.

HR should compare employee-level records against available approval emails, application forms, attendance data and payroll records.

Create an exception report for records that cannot be verified immediately. Do not silently change disputed balances to make the spreadsheet appear complete.

Each correction should have a reason, supporting evidence, date and authorised approver.

10. Choose a Migration Cut-Off Date

A clear migration cut-off date prevents leave applications from being counted twice or missed during the transition.

For example, an organisation may decide that the old system will manage leave applications up to 30 November, while the new HR platform will become the official system from 1 December.

The migration plan should specify:

• The final date for entering leave in the old system.
• The date and time when the final data export will take place.
• How applications submitted during the transition will be handled.
• Whether pending applications will be imported.
• Who can approve leave during the transition.
• When employees can begin using the new platform.
• Who is responsible for resolving discrepancies.

If employees submit or take leave after the initial data export but before the new system becomes operational, those transactions must be captured and reconciled.

A short freeze on non-essential data changes may help, but urgent leave applications should still have a clear manual process.

11. Test the Imported Balances Before Going Live

Do not assume that a successful file upload means the migration is accurate.

Run a test migration using a sample group of employees before importing the entire workforce.

Include employees with different circumstances:

• New joiners.
• Long-serving employees.
• Part-time employees.
• Shift workers.
• Employees with carry-forward balances.
• Employees with pending leave applications.
• Employees with negative or adjusted balances.
• Employees who have used several leave categories.
• Employees who have transferred between departments or locations.

After the test import, compare the old and new balances.

Employee	Leave category	Old balance	New balance	Difference
EMP001	Annual Leave	12	12	0
EMP002	Annual Leave	8	8	0
EMP003	Sick Leave	10	10	0
EMP004	Childcare Leave	3	2	-1

The example highlights an issue that needs investigation before go-live. The difference should be explained and corrected rather than accepted without review.

Test not only the displayed balance but also how the system deducts leave, restores cancelled applications and handles new entitlement credits.

12. Reconcile Leave Balances With HR and Payroll Records

Leave data may affect payroll, particularly when employees take unpaid leave or when leave information is used for salary processing and reporting.

Before go-live, HR should compare the migrated records with relevant payroll and attendance information.

Reconciliation should cover:

• Approved unpaid leave.
• Leave taken during the latest payroll period.
• Salary deductions associated with no-pay leave.
• Approved leave that overlaps with attendance records.
• Leave encashment or final settlement information, where applicable.
• Outstanding corrections.
• Employees who have left the organisation.
• Leave records used in payroll reports.

Do not treat every leave balance as a payroll deduction or payment. The payroll impact depends on the leave category and applicable rules.

A signed-off reconciliation report should identify the opening balance for each employee and any unresolved exceptions.

13. Preserve Historical Leave Records and Audit Trails

Migrating opening balances does not mean the organisation should delete its old leave records.

Historical records may be needed to answer employee questions, investigate disputes, review past approvals and support employment recordkeeping.

MOM requires employers to maintain employment records for employees covered by the Employment Act. These records include dates and details of public holidays and leave taken. The general retention guidance is to keep the latest two years of records for current employees and the last two years of records for former employees for one year after they leave.

Employers should therefore retain the required historical information in an accessible format, even if the new HR system does not import every old transaction.

Preserve:

• Historical leave applications.
• Approval and rejection records.
• Leave taken by date and category.
• Opening and closing balances.
• Carry-forward calculations.
• Manual adjustments.
• Supporting documents where retention is justified.
• Migration and reconciliation reports.

The new system should also maintain audit logs showing who changed a balance, when the change occurred and why.

14. Protect Employee Data During Migration

Leave records contain personal information. Some supporting documents, such as medical certificates, may contain sensitive health-related details.

Employers should limit access to authorised HR personnel and other staff who genuinely need the information for their roles.

Good migration practices include:

• Use secure file-transfer methods.
• Restrict access to migration spreadsheets.
• Avoid sending unencrypted employee data through ordinary email.
• Confirm the new provider's security and access controls.
• Check how the provider handles data storage and overseas transfers.
• Avoid importing unnecessary medical details.
• Keep a record of who accessed or changed migration data.
• Securely dispose of temporary working files when no longer required.

Singapore's Personal Data Protection Act (PDPA) requires organisations to protect personal data through reasonable security arrangements and to manage retention appropriately. Employers should assess the responsibilities of the HR software provider and document relevant data-processing arrangements.

15. Communicate the Migration to Employees and Managers

Employees should know when the new leave system will become available and where they can check their balances.

Before go-live, communicate:

• The migration date.
• The date from which the new system becomes the official application channel.
• How employees can log in.
• Where to view opening leave balances.
• How to submit new leave applications.
• How pending applications will be handled.
• Who to contact if a balance appears incorrect.
• Whether any temporary manual process will apply.

Managers should receive separate instructions explaining how to review pending applications, approve requests and check team availability.

Give employees a reasonable opportunity to review their opening balances and report discrepancies. HR should provide a clear process for investigating and correcting errors.

16. Complete the Go-Live and Post-Migration Review

Once testing and reconciliation are complete, HR can approve the final migration.

A practical go-live process includes:

1. Take a final backup of the old leave records.
2. Export the approved final employee balances.
3. Import the data into the new HR system.
4. Check employee profiles and leave categories.
5. Reconcile a sample of records and all identified exceptions.
6. Confirm pending applications and recent leave transactions.
7. Obtain HR and payroll sign-off.
8. Activate employee and manager access.
9. Communicate the new application process.
10. Monitor the first leave and payroll cycles.

During the first few weeks, review employee queries, balance corrections, failed imports and approval workflow issues. Keep the old system's records available until the organisation has confirmed that the migration is stable and historical records remain accessible.

17. Common Mistakes to Avoid During Leave Migration

Businesses should avoid these common migration problems:

• Importing only the balance without supporting details: This makes it difficult to explain how the balance was calculated.
• Using inconsistent employee identifiers: Records may be assigned to the wrong employee or rejected during import.
• Combining different leave categories: Statutory and company-specific leave may have different rules.
• Ignoring carry-forward expiry dates: Employees may lose visibility of balances that must be tracked separately.
• Applying full-time calculations to part-time employees: This can create incorrect leave entitlements.
• Forgetting pending applications: Requests may be lost or approved twice during the transition.
• Ignoring recent leave transactions: A balance can become outdated between the first export and go-live.
• Failing to reconcile payroll inputs: Unpaid leave and other relevant records may not match payroll data.
• Deleting the old records too early: Historical information may still be needed for audits and employee queries.
• Allowing unrestricted access to migration files: Employee information may be exposed unnecessarily.

Conclusion

Migrating leave balances into a new Singapore HR system requires more than uploading a spreadsheet. Employers need to verify employee entitlements, standardise leave categories, preserve carry-forward information, handle part-time calculations correctly and reconcile balances against historical records.

A structured migration process reduces errors, protects employee information and helps HR teams maintain reliable leave records. Testing the new platform with different employee scenarios and obtaining formal HR and payroll sign-off before go-live are particularly important.

The objective is to make the new HR system the trusted source for future leave applications and balances while keeping historical records accessible for audits, payroll reviews and employee queries.

Reconcile opening balances, adjustments and employee IDs before switching systems. Pilot an InnBuilt import with a sample of Singapore staff.