Trusting an import: the verification summary and undo
After an import, Nexxus checks the database against your files (each tenant's ledger to the cent) and gives a verdict, plus when owner payouts start. Any batch can be undone from Settings → Data & Imports; the confirmation lists exactly what will be removed, including later work that depends on it.
An import you can't check is an import you can't trust. Nexxus checks every import as part of the import itself.
The Summary step
After writing, the importer re-reads the database and compares it against your source files:
- Verified against your files means every tenant, property, owner and lease was found, and each tenant's ledger charges and payments match their statement to the cent.
- Verification found differences — review before relying on this data lists exactly what's off. For example, a missing tenant by name, a count that came out different, or a tenant whose ledger totals differ from their statement.
Only leases the import created are checked. Months the importer filled from lease terms are left out of the comparison.
The Summary also says Owner payouts start with the [month] run, along with the date it pays and the rent it covers. Rent your owners were already paid through your previous system counts as settled and never pays out again (see The payout baseline). A Payout coverage check flags property-months where rent was collected but no matching owner payment was imported. Those are worth a look before your first run.
The health report
Below the verdict, the report groups what the importer did: Needs your review (for example a stay that may be a duplicate lease, with Same stay — remove the duplicate lease, Wrong unit — move stay… or Keep both), Cleaned up automatically, Not imported (with reasons), and which way refund-shaped lines moved. You can reopen the report later from Data & Imports with Report.
Reading a mismatch
A difference usually comes from the export, not the import. Typical causes: a statement export that stops short of today, a missing page, or a history range that doesn't reach far enough back. Fix the export and run it again.
Undo
Every import is a batch. Settings → Data & Imports lists them, and completed batches have Undo. The Undo this import? dialog shows what the batch created and warns about anything else that will go:
- Later imports on the same properties (for example an Airbnb import on top of your PMS import) are undone first, newest to oldest. The button then reads "Undo N imports in the right order".
- This also deletes work you did afterwards lists photos you added and property edits you made since the import. It also lists owner payout runs whose lines sit on these leases, including approved or sent runs, and notes that the payout baseline un-freezes if none remain. Re-importing won't restore them.
- This undo will be refused appears if a payout run on those leases moved real money through Stripe or is still in flight. The Undo button then stays greyed out.
- Will be deleted with this import names, one by one, what was added after the import that the undo deletes too: every draft owner payout on the import's owners or leases (with any hand adjustment and its reason, or manual line, you added to it) and every generated document, such as a 1099 or an owner statement, filed on its residents or owners. Each is marked "will be deleted" and the undo goes ahead. Re-importing doesn't bring back hand adjustments or manual lines, so note them first. Generate a document again from Reports if you still need it.
- This import can't be undone yet appears when records were added after the import that can't be recreated: a payment or refund entered by hand or through Stripe, a deposit holding money or notes, a deduction, release, refund or note recorded on the import's own deposits or its residents' deposits, an uploaded document, another lease or stay on its residents, an approved or sent owner payout of its owners, an owner payment recorded outside the import, an owner of the import who can sign in to the owner portal, or money recorded on one of the import's own stays after it (a payout marked received, a payout from another import or from a booking-site checkout, a Stripe payment or refund, a booking-site card checkout). The dialog lists them and the Undo button stays greyed out. Delete or correct them in the app first (for an owner's portal login, use Revoke access on the owner's Portal access card, and invite them again after you re-import; for a payout you marked received yourself, use Undo on the stay's Payout schedule), or keep the import: the undo cannot remove other money on the import's own stays. A deduction (reversed or not), a release, a refund or a note on one of those deposits is different: nothing in the app clears it, so that import stays, and the dialog says so. Contact support if it has to be undone.
A document counts as generated when Nexxus made it (a 1099, an owner statement or a report PDF from Reports), even if the teammate who generated it has since left your team. A file someone uploaded, including one a resident added from the portal, is not generated: it is listed as a document under "can't be undone yet".
If something the undo would also delete is added after you open the dialog, the undo stops without changing anything and asks you to open it again, so it never deletes what you didn't see.
The records the batch created are removed in one transaction, so you never end up with a half-undone import. Undo also puts back what the import changed in records it did not create (an absorbed lease, an updated stay and its payout schedule, a No longer managed flip, a building conversion), listed under Puts back in the dialog. If one of those records was changed again after the import, the undo stops and names it, so it never erases that later change. A pending owner payment the import marked settled stays settled, and a Stripe-confirmed record is never reverted.
The Undo this import button on the importer's final screen opens the same confirmation dialog, so you see the full list there too before anything is removed.
The rhythm for a tricky migration: import → read the Summary → if something's off, undo → fix the export → run it again.
When to ask for help
If the Summary passes but a number still looks wrong, ask the assistant or post privately on NexxusHub with the batch date. Don't patch it with manual edits.
Related guides
Importing your data from Buildium, Airbnb, and other systems
How the Import data page works: the two tabs (PMS · VRBO · bank · spreadsheets, then Airbnb), what to export from Buildium and other systems, the Go back history range, the Review step, the verified Summary, re-imports, and undo.
What imported history can and can't do
Imported history counts as closed business: it powers reports and occupancy, but late fees are never charged for days before a lease existed in Nexxus, owners are never re-paid for months your old system settled, past leases are never charged rent, and filled-in months never count as payout cash.
Importing Airbnb and short-term rental history
The Airbnb tab on the Import page reads your Airbnb reservations and payout CSV exports to bring in PAST stays, with payouts on the dates Airbnb actually paid, reconciled to the cent and undoable as one batch. It's safe to re-run. For ongoing two-way sync of upcoming reservations, connect Airbnb on the Channels page instead — the two work together.
The payout baseline: "Payouts through Nexxus began X"
The baseline is the line between owner money your previous system already settled and money Nexxus runs own. It freezes when you approve your first run, browsing never moves it, and only an owner-admin's Reset payouts (before real money moves) clears it.