Data Import & Migration

Rollback & Import History

Reading an import's result page, the row-by-row error log, and how to undo a completed import within the 72-hour rollback window.

Rollback & Import History

Every import is kept as a record — what was imported, by whom, how each row turned out, and whether it can still be undone.

Import history

The Import history table at the bottom of Settings → Data Import lists every import your organization has run:

Column	Shows
Source	The file name, or the platform for a direct connection
Type	Employees, Leaves, or Departments
Status	Where the import got to
Rows	Imported out of total, plus failed and skipped counts
Date	When it was started

Click any row to open its detail page.

Statuses

Status	Meaning
Pending / Parsing	The file has been uploaded and is being read
Mapping	Waiting for you to confirm the column mapping
Preview	A preview has been generated; nothing written yet
Running	Records are being created
Completed	Every row was processed, with no errors
Completed (errors)	Finished, but some rows failed — see the error log
Failed	The import could not run at all
Cancelled	Abandoned before it ran
Rolling back / Rolled back	The import is being, or has been, undone

The import detail page

Five counters across the top:

Counter	Meaning
Total	Rows in the file
Imported	Records successfully created
Errors	Rows that failed validation and were not created
Warnings	Rows that were created, but with something adjusted or dropped
Skipped	Rows deliberately not created — usually because the record already exists

Underneath: the source, the template used if one was detected, and the start and finish times.

A warning is not a failure. A row with a warning was imported. Warnings cover things like a value truncated to fit the field's maximum length, an unrecognized employment type replaced with the default, or a date more than five years in the future. Worth reviewing, not worth re-running.

The error log

If any rows failed, an Error Log lists them by row number with the field and the reason — email: Invalid email format, startDate: Invalid date format, firstName: firstName is required.

Because the row numbers match your file, the usual fix is to correct just those rows in a copy of the spreadsheet and import that smaller file. The rows that already succeeded will be skipped as duplicates if you accidentally include them again.

Rolling back an import

A completed import can be undone. Open its detail page and click Rollback.

BookYourPTO deletes every record the import created, in reverse order — employees before the departments that were auto-created for them — so nothing is left orphaned. Where the import only changed something, such as setting a manager on an employee who already existed, that change is reversed rather than the person being deleted.

The confirmation dialog tells you how many records will be removed.

The rollback window

Rule	Detail
Window	72 hours from when the import completed
Who	The person who ran the import, or an Executive
Eligible	Imports that finished — Completed or Completed (errors)
Repeatable	No. An import can be rolled back once

The detail page shows Rollback available until … while the window is open, and the button disappears once it closes.

Rollback is itself permanent. It deletes the imported records outright — it does not archive them. If an imported employee has since logged in, booked leave, or had documents attached, think before rolling back: you're removing that person. For a small mistake, editing the affected records is usually safer than undoing the whole import.

What a rollback does not do

It does not restore records that existed before the import — those were never touched.
It does not undo an import outside the 72-hour window; after that, remove records individually from Managing Users or the departments settings page.
It does not remove a platform connection or a saved template.

Rollbacks are recorded in the audit log alongside the original import.

Leave history is not de-duplicated. Unlike employees and departments, an imported leave record is created every time. If you run the same Leave History file twice you'll get two copies of each request — so roll the second import back rather than deleting them by hand.

Custom Templates

Save your own column mapping as a named, reusable template, and manage the built-in and custom templates available to your organization.

Troubleshooting

What each import error means and how to fix it — upload failures, unmapped columns, validation errors on individual rows, and imports that finish with the wrong result.