Skip to main content
Vern helps SaaS teams move customer data from a customer’s old system into yours, fast. Start on Home: describe the migration, attach the customer’s files or link your GitHub repo, and the Vern agent plans the whole job — the company, sources, templates, knowledge, writers and any scheduled sync — then builds it across Vern once you approve. Or do each step yourself: define your templates, create a company for the customer, import their files with the migration agent, check the result, and send it to your app.

​
How it fits together

Home

Ask the Vern agent to build, run or fix any part of a migration. You approve the plan; it does the work.

Templates

Your target schema — columns, rules, links, structured values, and columns Vern calculates or extracts from free text.

Onboard a customer

Create a company and its workbook, then import the customer’s export.

Clean customer data

The migration agent maps their data to your templates, asks what it needs to, and previews everything before it writes.

Sources

The systems customers move off. What Vern learns about each one — and its import recipes — is reused on every migration from it.

Scouts, Lists & Workflows

Browser agents for portals with no API or export (US-hosted accounts), and workflows that keep data in sync on a schedule.

Send data to your app

Download the cleaned data as CSV, or write it straight into your API with a writer.

Integrations

Connect GitHub so the agent can read your mapping docs, rules and sample data — or talk to it from Slack.

Migration API

Create migrations, run the agent and pull cleaned data from your own backend.

MCP server

Use Vern from Claude Code, Cursor or any MCP client.

​
Next steps

  • Home — describe your first migration and let the agent build it.
  • Quickstart — onboard your first customer end to end, step by step.