Let your customers migrate their own data
Drop Vern into your onboarding flow and the agent does the migration inside your product — reading whatever they can export, asking them when it’s unsure, and writing validated records. Your team approves the result instead of doing the work.
- ISO 27001 certified
- GDPR compliant
- US & AU data residency
- Audit-ready logs
Importing from PropertyIQ
Reading what you uploaded…
Your files
owners_export.xlsx
2 sheets · 1,204 rows
lots.csv
486 rows
invoices_2019-2024.zip
312 files
insurance_certificates.pdf
18 pages
Reading your uploaded files. Extracting tables from your file. Profiling your source data. Checking the target templates. Searching the web about this source. Saving what we learned about this source. Drafting the import. Testing the recipe on your data. Reviewing the preview output. Importing your data. Checking which fields came across
A real migration, replayed — every step your customer sees, and nothing they don’t.
Onboarding teams from startups to listed companies run on Vern
The problem
Your customers can't finish their own migration
Getting the export is easy. Getting it correct is where onboarding timelines go to die — and why your team is still in the loop.
An importer stops at the upload
Mapping columns is the easy half. Joining three files, applying your rules, decoding a legacy export — that lands back on your team.
Every ambiguous field becomes an email
Your customer knows what settled means in their old system. They just have no way to tell the importer, so they ask you and wait days.
Every new source is a ticket
Transformation logic lives in your codebase, so a new export format needs a deploy — and the backlog gates every onboarding behind it.
How it works
You set it up once. Your customers run it. You approve what lands.
Not a mapping wizard with an AI button — an agent that does the migration end to end. Each screen below is labelled with whose it is. The customer-facing ones sit inside your product, not ours.
It compounds
Migration #50 takes a fraction of the time migration #1 did
Vern writes down what it learns — per source system and per customer — and reads it before every run. You decide what compounds: turn memory off for a test or a one-off and that migration teaches it nothing.
PropertyIQ writes settled for invoices closed before 2022 — map to Paid.
What Vern knows about this source
- Field formats, enums, ID and date patterns — taught once.
- Every customer on this source starts from what you already know.
Brightside’s lot 13 doesn’t exist. Blank levies mean nil, not unknown.
Teach Vern about this customer
- Decisions you made together, recorded — never asked twice.
- Vern writes here too, building memory as it learns.
Extractor library
0source systems — and the agent writes the ones we don’t have
Connect a source once; every customer on it reuses the recipe. Obscure system? The agent reads the docs and writes the connector.
Migration API
This runs inside your onboarding flow, not ours
Everything the app does, over an API — including the parts that need a human answer. Create the migration, stream the agent's thread into your own UI, let your customer answer its questions and approve the result. They never see Vern.
API=https://app.vern.so/api/v1
KEY="x-api-key: $VERN_API_KEY"
JSON="Content-Type: application/json"
# 1 — create the migration
ID=$(curl -sX POST $API/migrations \
-H "$KEY" -H "$JSON" \
-d '{"name":"Brightside","source":"PropertyIQ"}' \
| jq -r .migration.id)
# 2 — the agent drafts a plan, stopping at a preview
curl -X POST $API/migrations/$ID/runs \
-H "$KEY" -H "$JSON" -d '{"kind":"generate"}'
# 3 — see exactly what it would produce
curl $API/migrations/$ID/preview -H "$KEY"
# 4 — approve, and write the rows
curl -X POST $API/migrations/$ID/runs \
-H "$KEY" -H "$JSON" -d '{"kind":"execute"}'Trust
Built for the security review, not just the demo
You are handing us your customers' data. Everything below is a product feature you can inspect, not a promise in a slide.
Records supported per migration
Records imported since inception
Customer clarifications actioned
ISO 27001 certified & GDPR compliant
An ISO 27001-certified security program with enterprise-grade encryption and access controls, and data handling that is GDPR compliant.
Every decision is on the record
Every clarification, mapping choice and fix is logged with a before and after — attributed, back to the original upload.
Data residency you choose
Tenants are pinned to the United States or Australia. Nothing crosses regions.
Retention you set
Workbooks auto-delete on your schedule — 7 to 365 days, or never — with a preview of what each setting removes.
Pricing
Pricing that scales with migration volume
Usage is metered in credits — how many a migration consumes depends on the volume of data and the extraction method. No per-user fees.
Partnerships
CustomFor companies that don’t treat migrations as core business and hand them to us end to end.
- Fully managed migrations
- White-label delivery
- A dedicated migration team
- Per-project pricing
- Priority turnaround SLAs
Need more? Add pay-as-you-go volume at any time, or talk to us about a committed onboarding program.
FAQs
The questions that come up on every call
Ready to migrate your next customer?
Watch Vern turn a real export into validated, approved records in your product.