Employee database software: records, access and exports

Which employee database software should a small business choose?

This guide covers a software buying exercise. The records and document labels below are fictional, and the proposed checks are not completed vendor trials. Recruitment applications, employee administration and HR reporting have different requirements; links to those separate guides are included below.

What should an employee database hold?

Start with information needed for the agreed process. A field’s presence does not show that it is current, required or visible to the correct person. A people directory and a complete personnel-record export are also different outputs.

Compare the product boundaries, not just the database label

BambooHR’s employee-records page describes the central database, custom fields, tabs and tables, and self-service. The feature description alone does not settle a particular quote or prove that an export recreates the same structure elsewhere.

Breathe’s HR user guide explains people types and manager references. Zoho People’s account guide distinguishes users from non-login profiles and describes import mapping. Keep those meanings with the proposed product; “employee”, “user” and “profile” are not interchangeable billing units across vendors.

Six stored records are not six active employees or six logins

Use this fictional snapshot as a shared demonstration brief. It is a reconciliation exercise; add the required fictional fields using the vendor’s import template before any trial import. Current and Archived are the fixture’s own agreed statuses. An empty manager reference for R01 means no manager is assigned within this small example. All other manager references point to R01.

The fixture contains 6 stored records, 4 current employees, 5 current people including the contractor and 2 enabled logins. R05 is the one archived employee record; R06 is the current contractor. These counts describe different scopes and do not establish any vendor’s billable total.

Zoho’s users and Employee Profiles FAQ says non-login profiles are maintained by the organisation, with permitted managers or administrators acting on their behalf. Storing R03’s record therefore does not by itself give R03 self-service. Ask which supported account type and licence would apply instead of assuming an uninvited person costs nothing.

Test permissions with the actual plan and role

Write the intended result before opening a demo. The following are proposed requirements for our fictional exercise, not claims that a vendor’s default role has these permissions.

There is a concrete plan boundary in Breathe’s permissions guide: HR users on Micro and Starter can see salary information, while HR and Finance permissions are separate on Regular and above. The same role label is not a promise of identical access on every band. If your brief requires a separation, confirm that the quoted arrangement provides it.

Zoho’s account FAQ also distinguishes module, record and field permissions when troubleshooting access. A visible menu, an editable field and permission to export its value need separate checks. Record the observed result and unresolved questions rather than treating the word “role-based” as a completed test.

Separate person documents from company-wide reading

The three document references below show a one-to-many relationship: R01 has two linked documents and R04 has one. The labels describe imaginary files; no signed contract or private employee file is included.

• D01 → R01: Agreement example. Intended audience: Approved HR role.
• D02 → R01: Equipment handover example. Intended audience: R01 and approved HR role.
• D03 → R04: Starter checklist example. Intended audience: Assigned manager and approved HR role.

A company handbook may instead need a group audience and a reading record. Breathe’s company-documents guide describes audience selection, tags and read-required documents. It also distinguishes initial read-required notifications from later changes to the audience or requirement, so adding a person does not justify assuming a new email was sent.

Ask separately whether a person’s file, the document label, the stored attachment and the acknowledgment history are included in the relevant export. A link or filename in a spreadsheet is not the file itself, and a read acknowledgment is not a claim about the person’s understanding or every other approval process.

Reconcile exports by IDs and relationships

An export that repeats a person for every document may contain more rows than people. A flat left join of our six records to the three linked document references produces this illustrative output. People without a document remain in the fixture.

The output has 7 rows but 6 distinct person IDs and 3 distinct document IDs. R01 appears twice because it has two documents. Deduplicating on the entire row will not turn these into one row per person; separate the person and document relationships during reconciliation.

Breathe’s People Data Export guide describes an Excel download containing the majority of profile information and the choice to include or exclude ex-employees. It does not claim that this is a complete attachment backup. In our fixture, a current-people export and a historical export should be checked against different expected populations.

Export with the intended role and filters, then compare identifiers, statuses, manager links and linked-document counts. The joined table is our own illustration, not an assertion that Breathe, BambooHR or Zoho exports that exact format.

Use a small import, change and exit exercise

1. Map the six records: agree person IDs, worker types, status meanings and the two proposed login accounts. Map required vendor fields without using real employee information.
2. Retain manager links: R02–R06 refer to R01 in this fixture. Breathe’s HR user guide says its import uses the manager reference number, rather than the manager’s name; follow the current vendor template.
3. Check a rejected reference: propose a trial copy of R04 with manager R99, which is absent from the fixture. Record whether it is rejected, held or accepted and what correction is required.
4. Review a duplicate: submit a controlled duplicate in an isolated evaluation and inspect matching behavior before making bulk changes. Zoho’s account guide documents duplicate detection and field mapping, but that does not establish which rule fits your data.
5. Change one field: update an allowed fictional detail and inspect approval, history and visibility as the intended employee, manager and HR role.
6. Review the archived person: inspect disabled-login behavior, visibility and the historical export for R05. Do not treat disabling access, archiving and deleting as equivalent actions.
7. Reconcile the output: explain six stored records, four current employees, five current people, two enabled logins and the three linked documents before approving the proposed migration.

Keep the product, retained package, settings, expected result, observed result and exception owner beside each check. Leave observations blank until the evaluation is actually performed.

Price the required record workflow and connect the next step

Request a quote using the vendor’s actual units: current and archived people, employee versus non-login profile types, enabled self-service accounts, administrators, required document scope, modules and integration work. Two logins in the fixture do not establish a two-seat quote. A low headline price does not show that every record, role or export is included.

Use the Breathe HR versus BambooHR comparison or Zoho People versus Factorial to frame a shortlist. For headcount definitions and dashboards, read the HR reporting tools guide. For applications and the hired-person handover, use the HR recruitment and ATS guide.

The HR software directory gives the broader category. For a small business, the useful result is a record workflow that your people can maintain, control and hand over—not the largest untested feature list.

Frequently asked questions