Reading Your Import Report

When an import finishes, URBI emails a report to whoever ran it. It is the record of what actually happened, row by row, and it is worth two minutes of your time before you close the file.

Where it goes

To the email address on the account that pressed Import, with the subject Unit Import Report. It is not sent to residents, the board, or anyone else on the property.

What it looks like

The top of a report:

The summary line counts rows, not units and not people. A building of 168 units with 320 people in it produces a report of 320 rows.

How to read it in two minutes

1. Check the total. The number after "out of" should match the row count on the confirmation screen. If it does not, some rows were skipped on the Review step.
2. Go straight to the errors. Search the email for [ERROR]. Those are the only rows that need you.
3. Skim the warnings. Most say "already existed", which is expected on a re run. What you are looking for is a warning you did not expect, for example a unit that should have been new.
4. Ignore the successes. They did what you asked.

Matching a report line back to your file

Row 12 is the twelfth row that was sent, not the twelfth line of your spreadsheet. If you skipped rows on the Review step the numbering shifts. The unit number in brackets is the reliable anchor, so search your file for that instead.

What the counts really tell you

• Successful rows created something new: a unit, a person, or an emergency contact entry.
• Warnings are almost always "this was already here". A re run of the same file produces a report that is nearly all warnings, and that is the correct outcome, not a failure.
• Errors mean part of a row did not land. The message says which part. Import Errors and What They Mean covers each one.

After you have read it

Open the Units list and spot check three things:

• The unit count matches what you expected.
• A few units show the right status (Owner, Rented, Vacant).
• A unit with several people on it shows all of them.

Then fix the error rows. The safest way is to correct just those rows in a small CSV and import that file on its own. Re importing does not email anyone twice: a person already invited to a unit is reported as an existing invite and left alone.

If the report did not arrive

Check spam first. The import itself is unaffected, so the Units list still tells you what happened. Reports are sent once, at the end, and cannot be re sent from the interface.