All posts
11 min read

How to Import Employees From a Spreadsheet Without Carrying Over Its Mistakes

By the Redstone HR team · Published

Subscribe to our newsletter

Read about our privacy policy.

To import employees from a spreadsheet safely, fix the records before you move them. Agree each person's opening annual leave balance, choose one source of truth for every holiday request from a fixed date, then import a clean employee list. The file format is the easy part. The real risk is turning numbers that were already wrong into numbers that look official.

Why moving staff out of a holiday spreadsheet feels risky (and where the real risk is)

Moving off a holiday spreadsheet feels risky because people fear losing data, but the bigger risk is importing data that was already wrong. In many small businesses, the spreadsheet, the email threads and the paper forms stopped agreeing some time ago. Balances drift, payroll gets corrected after the fact, and staff dispute what holiday entitlement they are owed.

Holiday records drift for a simple reason. Leave is usually handled by an office manager, operations lead or founder alongside everything else, and no single record holds every holiday request, approval, balance and local rule. A request agreed in an email never reaches the sheet. A paper form sits in a drawer. A carryover agreed in a corridor exists only in someone's memory.

The pressure on that person is not easing. According to HRO Today, reporting a survey by AbsenceSoft, leave and absence requests are outpacing HR capacity, with many HR teams missing deadlines. In a small business without an HR team, that load lands on someone who already has a full job.

The outcome worth aiming for is one accurate record of every request, approval and balance that everyone trusts, without reconciling three sources each month. If you are still deciding how to track time off at all, start with a guide to tracking employee time off for growing teams.

Is your spreadsheet ready to import? A five-minute self-check

Your holiday spreadsheet is ready to import only when its balances are agreed and match every other record. Answer these five questions honestly:

  • Do the balances in the spreadsheet match what is in email threads and paper forms for every employee?
  • Has each employee agreed their opening annual leave balance?
  • Do you have more than one site, or staff in different UK nations with different bank holidays?
  • Do different groups of staff have different carryover rules?
  • Has payroll been corrected after the fact in the last few months because of leave figures?

How to read your answers: a "no" to question 1 or 2 means you have tidying to do before any import. A "yes" to questions 3, 4 or 5 means you have probably reached the point where a spreadsheet costs more time than it saves.

There is no fixed headcount at which a holiday spreadsheet stops working. A ten-person practice with two sites can outgrow it sooner than a thirty-person office on one site. Extra sites, different bank holidays and differing carryover rules are better signs of the tipping point than the number of staff.

What should you fix before importing? Opening balances and one source of truth

Before importing, fix two things: agreed opening balances and a single source of truth for leave. Everything else in the tidy-up builds on those two steps.

  • Agree opening balances with each employee. Send each person their annual leave balance as you have it, including any carryover, and ask them to confirm or query it. Settling disputes now is far easier than settling them after go-live, when the figure carries the weight of a new system.
  • Choose one source of truth from a fixed date. Decide that from a named date, every holiday request and approval goes through one place only. Tell staff and managers that email threads and paper forms are retired from that date.
  • Build the rest on top. Change logs, monthly payroll figures and reporting all depend on the first two steps being right.

Timing matters. Pick a quiet week as the cut-off, with no large holiday approvals in progress, so nothing is half-agreed in the old system while you switch to the new one.

What information should your employee spreadsheet include before import?

An employee spreadsheet ready for import should hold the basics any leave system needs to route requests and calculate balances. Plan for these columns:

  • Full name
  • Work email address
  • Manager or approver
  • Site or location
  • Holiday entitlement for the leave year

Also record anything that changes entitlement or bank holidays: which site or UK nation each person works in, and any carryover agreed for the current leave year. If carryover was agreed by email, add it to the sheet now.

Before you import, run these clean-up checks:

  • Remove leavers.
  • Fix duplicate or misspelt names.
  • Use one email address per person.
  • Keep each column consistent, for example the same date format and the same site names throughout.

Keep the original file untouched as an archive and work on a copy. If a query comes up later, you can show exactly what the old record said.

How do you handle bank holidays for staff in England, Scotland and Northern Ireland?

One spreadsheet can hold bank holidays for staff in England, Scotland and Northern Ireland, but only through manual upkeep, such as a separate calendar for each region. That upkeep is easy to get wrong.

The quiet danger is the copied formula. Someone copies a row for a new starter in Glasgow from a colleague in Manchester, and the balance is now calculated from the wrong nation's calendar. Nobody notices until the employee queries their entitlement. Before importing, check which bank holiday calendar each employee's balance was calculated from.

A better setup sets each location's bank holidays, holiday entitlement and carryover rules once, so they apply automatically to everyone at that site from then on. New starters inherit the right rules by being assigned to the right location, not by copying a formula.

Common mistakes when moving employees off a spreadsheet

The common mistakes when moving off a spreadsheet all come from carrying the old drift into the new system:

  • Importing balances nobody has agreed. Old disputes arrive in the new system looking official.
  • Running the old spreadsheet alongside the new system. You are back to two records that disagree.
  • Forgetting carryover agreed by email. It was never entered in the sheet, so it never reaches the import.
  • Assuming everyone shares the same bank holiday calendar. Staff in different UK nations do not.
  • Leaving managers to approve leave the old way. If managers keep saying yes by email after go-live, the new record is incomplete from day one.

Spreadsheet, shared calendar or leave software: which approach fits a small business?

For a small business, the right approach is the one where the checks happen as part of the decision to approve, not afterwards. Here is how the main options compare:

Approach Shows who is off Holds balances and applies rules Warns of coverage gaps at approval Cost as you hire Tidier spreadsheet Only if kept up to date Manually, by formula No Free, but costs someone's time Shared calendar Yes No No Usually low Full HR suite or HR hire Yes Yes Varies Often rises with every hire Leave software built around one record Yes Yes, automatically Yes Depends on pricing model

A tidier spreadsheet is free and familiar, but it cannot warn you about a coverage gap at the moment you say yes, apply the Bradford Factor consistently or keep each site's rules straight. The checking, chasing and correcting simply move onto someone who already has a full job.

A shared calendar shows who is off, but it holds no balances, does not apply holiday entitlement or carryover rules and does not score sickness. Most small businesses end up keeping a spreadsheet alongside it, which brings back the two-record problem.

A full HR suite or a dedicated HR hire is often more than a 1–50 person team needs, and suites that charge for each employee cost more every time you hire.

Leave software built around one record puts the checks inside the approval itself. For a side-by-side view, see how leave tracking in Redstone HR compares with Excel spreadsheets.

What good looks like after the import

After a good import, leave largely runs on its own and the person in charge only handles genuine exceptions. In practice, that means:

  • Cover is visible before you say yes. Managers see who else is out and get coverage warnings before approving a holiday request, so key client or patient days keep enough cover.
  • Balances update themselves. Each approved request adjusts the balance automatically, with no end-of-month reconciling.
  • Fewer interruptions. Employees check their own balances and can ask an AI policy assistant questions such as whether they can carry holiday over, so the office manager is not answering the same questions all week.
  • Payroll figures in minutes. Monthly figures come out as payroll-ready exports in CSV, Excel or PDF, which you can send to any payroll provider. Direct payroll integrations are on the roadmap and not available today.
  • Time off where people already look. Leave can appear in the calendars your team already uses; here is how to add an iCalendar feed to Google Calendar.

How long does it take to set up, and what does it cost?

With Redstone HR, most teams are up and running in under 15 minutes: import your employee list, set your leave policies and you are live. The preparation in this guide, agreeing balances and cleaning the list, is what makes those 15 minutes produce a record you can trust.

Redstone HR is a web app used in any desktop or mobile browser, with no download. There is no native iOS or Android app today.

Redstone HR charges a flat monthly fee per company, set by headcount band, not per user or per seat:

Plan Employees Price Relevant to importing Starter 1–15 $49 a month 1 location, up to 3 leave policies Growth 16–50 $99 a month Up to 5 locations, unlimited leave policies Scale 51–150 $199 a month Unlimited locations

A 30-person team on Growth pays $99 a month in total. If you cross a headcount band, the upgrade is prorated, so you only pay the difference for the remaining billing period. Hiring one more person within your band does not change the bill.

The AI policy assistant, smart approvals, team calendar, employee self-service and balance tracking are included in every plan. There is a 14-day free trial with no card required.

Your next step: assess your own process before you move

Go back to the five-minute self-check. If you answered yes to different bank holidays, differing carryover rules or payroll corrections, your holiday spreadsheet is costing more time than it saves.

Whichever approach you choose, start with the two fixes: agree opening balances with every employee, and pick one source of truth for every holiday request from a fixed date. Those two steps make any move cleaner, including a better-kept spreadsheet.

If you are weighing what to move to, browse alternatives to managing annual leave in a spreadsheet. Then, with your self-check answers to hand, compare your current process point by point on the RedstoneHR vs Excel Spreadsheets leave tracking comparison.

Frequently asked questions

What should I fix before importing employees from a holiday spreadsheet?

Agree opening annual leave balances with each employee and choose one source of truth for every holiday request and approval from a fixed date. Change logs and monthly payroll figures build on those two steps.

How many staff before a holiday spreadsheet stops working?

There is no fixed headcount at which a holiday spreadsheet stops working. Extra sites, different bank holidays and differing carryover rules are better signs of the tipping point than the number of staff.

Can one spreadsheet handle bank holidays for staff in England, Scotland and Northern Ireland?

One spreadsheet can hold bank holidays for different UK nations, but only through manual upkeep such as separate calendars per region. A copied formula can apply the wrong calendar without anyone noticing.

Is a shared calendar enough for planning cover?

A shared calendar shows who is off, but it does not hold balances, apply holiday entitlement or carryover rules, or score sickness, so most small businesses still keep a spreadsheet alongside it.

How long does it take to set up Redstone HR after cleaning the spreadsheet?

Most teams are up and running in under 15 minutes: import your employee list, set your leave policies and you are live. Pricing is a flat monthly fee per company by headcount band, from $49 a month.