For facilities & property platforms
Migrate a portfolio without losing the asset register
Vern imports buildings, lots, owners, assets, work orders and compliance certificates — reconnected to each other and validated before a portfolio moves onto your product.
Onboarding teams at startups and publicly listed companies run their customer migrations on Vern
Why Vern
An asset register that is complete, and compliance dates that survive the move.
What breaks in a manual Facilities Management move — and what Vern does about it.
The hierarchy is implicit
Portfolio, building, level, lot, asset — the relationships often exist only in a naming convention or a spreadsheet tab, not in a key.
Compliance dates are load-bearing
Certificate expiry, inspection intervals and warranty periods drive scheduling. Lose one and a statutory inspection quietly stops happening.
Contacts wear several hats
The same person is an owner in one building, a committee member in another, and a tenant in a third. Flatten that and you lose who can approve what.
Maintenance history arrives as documents
Years of work orders, invoices and certificates are a folder of PDFs, not a table — and the history is what makes the new system usable on day one.
How it works here
What Vern does differently on this data
Hierarchy inferred from the data
The agent works out how lots roll up to levels and buildings — including when the only evidence is a filename or a merged header — then confirms it with you before importing.
Your mapping rules, not ours
Split names, normalise formats, recalculate derived fields, merge records — described in plain English and saved as a recipe you can read and re-run.
Bulk document extraction
PDFs and scanned attachments are parsed into structured rows and linked back to the record they belong to, instead of arriving as a folder nobody opens.
Compliance dates preserved
Certificate and inspection dates are normalised to real dates rather than strings, so scheduling works from the moment the portfolio lands.
Self-healing imports
After a run, the agent inspects every cell that failed validation, fixes what it can in the recipe, and re-runs. What it can’t fix is reported with an exact count, never silently dropped.
A full audit trail
Every clarification, mapping choice and automated fix is logged with a before and after, attributed to a person or the agent, all the way back to the original upload.
What moves
What comes across, and what Vern adds on the way
- Buildings, levels & lots
- The hierarchy reconstructed, not flattened into one table.
- Owners, tenants & committees
- One contact record per person, with every role they hold intact.
- Assets & maintenance history
- Work orders and invoices reattached to the asset they belong to.
- Compliance certificates
- Extracted from PDFs with expiry dates that scheduling can use.
Extractors
67 connectors for this space, and the agent writes the rest
Connect a source once and every customer you onboard off it reuses the same connection and everything Vern already learned about it.
Ready to migrate your next Facilities Management customer?
See Vern turn a real export — whatever shape it arrives in — into validated, customer-approved records in your product.