Kompas uses Deck to migrate new customers off legacy property management systems with one landlord login, moving every tenant and signed lease file in under an hour for a 300-tenant portfolio. Kompas is accounting-first property management software, built in Montreal by CPAs and operators with three generations in the business. It runs operations and accounting as one system for Canadian landlords with up to 1,000 units.
Kompas is building the AI-native system of record for property management, the way Rillet is for accounting and Ramp was for spend management. Challengers like that grow by winning customers away from incumbents, and every win starts with a migration. Every legacy PMS was built to keep data in.
“We’re software and a service. Onboarding makes or breaks a customer. Deck helped us cut our onboarding time by a third and made it better, because the migration runs itself and our people get to do what no software should: build the relationship.”
Cory Friedman, Kompas
Data locked in the legacy PMS
A landlord switching to Kompas needs their tenants and every signed lease on day one. Their old system was never designed to let that happen. Rows might export; documents don’t. Logins sit behind strict 2FA and anti-bot defenses. Getting a full history out has meant a person clicking through a portal.
The typical case: tenant rows export. Lease files don’t, and a single lease can hold anywhere from zero to 10 files. Most legacy property management systems have no bulk export for lease files, so for a 300-tenant portfolio, that’s hours of downloading, and onboarding stops while everyone waits.
“The raw data itself is very easy to extract and map. It’s really the file downloads, because there’s no way to do a mass export of the files.”
Cory Friedman, Kompas
Kompas had three bad options: hire onboarding staff to click through portals, build and maintain scrapers for every legacy system, or let the migration drag and risk the deal. Staff work one landlord at a time, scrapers break on 2FA and anti-bot defenses, and RPA tools like UiPath break when a page layout changes. Deck’s agent operates each system’s own interface and clears 2FA through the connector, so Kompas needed none of them.
An agent that runs the migration end to end
Kompas embeds a Deck connector in its own onboarding, so the landlord signs into their old system there, once. From that point on, a Deck agent takes over the work an onboarding analyst would normally do, going through each tenant and downloading every file. Because Deck’s agent infrastructure operates any web interface directly, the legacy system never needs an API or a bulk export for the migration to work.
-
Connect
The landlord signs into their legacy PMS through the Deck connector. Kompas never sees or stores the credentials.
-
Verify
Legacy PMS logins are strict. Some ask for 2FA through an emailed secure link, even with saved cookies. The Deck connector walks the landlord through it and confirms: you’re connected, we’re migrating your data now.
-
Extract
Deck’s agent pulls the landlord’s full tenant list in seconds. It uses the system’s own front-end calls where it can and the UI where it must.
-
Download
For each tenant, Deck’s agent opens the lease and saves every file, about 5 to 6 seconds a lease.
-
Deliver
Files land in Deck storage, available through Deck’s API. A webhook fires as each task completes, and Kompas posts every file to the matching lease by onboarding ID.
Migrations stop queuing behind people. Before, every migration waited for an onboarding specialist with time to click through a portal, one landlord at a time. Now each Kompas migration starts the moment a landlord logs in, with its own Deck agent, so landlords who sign up the same week no longer wait in line. Kompas’s team watches progress in the Deck console instead of doing the downloading.
No scraper code anywhere. Deck built the Kompas migration workflow by prompting in plain language. Kompas’s side is a webhook listener its own coding agent builds from a scoped API key.
Inside a migration, step by step
A Kompas migration under the microscope, from connector link to leases in storage.
| Elapsed | Step | Detail |
|---|---|---|
| Start | Landlord opens the Deck connector, logs in and clears 2FA | Embedded in Kompas onboarding; emailed secure link pasted into the connector |
| +10s | Tenant list extracted | 301 tenants · 2,400 rows |
| ~5–6s / lease | Leases downloaded, one task per tenant | 0–10 files per lease |
| ~53 min | Last lease in storage | Every lease file included |
| As each task completes | Files posted to Kompas API | Mapped by onboarding ID |
End to end, Deck moved all 301 tenants and every lease out of a legacy property management system in about 53 minutes, unattended. By hand, it’s hours of clicking, before counting the days spent waiting on the landlord.
Onboarding that scales with sales
Capacity, not just speed. For a challenger, onboarding speed is acquisition speed. A person can work one archive at a time, but Deck runs a separate agent for every migration, so agents don’t queue. With Deck, Kompas can take on as many landlords as sales can sign, without hiring onboarding staff to match.
20 days faster to activation. Kompas cut onboarding from 60 days to 40 with Deck. The time saved isn’t in the download. It’s in the days a landlord used to spend exporting, emailing and re-sending files, every one of them a day before the customer is live on Kompas.
The objection flipped. “How do we get our data out?” used to slow Kompas deals down. With Deck, the answer is: “Click this link, log into your old system once, we handle the rest.”
“Every AI-native challenger hits the same wall: the customer’s history is locked in the incumbent. Deck takes that wall down, and that’s leverage the rest of the industry doesn’t have.”
Cory Friedman, Kompas
No more back-and-forth. Migrations drag on for weeks because the data never arrives whole. A landlord exports part of it, files go missing, someone re-sends, and by the time it’s complete, new tenants have moved in and leases have changed, so the cycle starts again. Deck moves a landlord’s whole account in under an hour, so there’s no gap for the data to go stale. Kompas gets everything, current, in one pass.
| Before Deck | With Deck | |
|---|---|---|
| Files out of the legacy PMS | One PDF at a time, by hand | Deck’s agent pulls the full archive |
| Who does the work | Landlord or Kompas staff | Deck’s agent, after one login |
| Time to data in Kompas | Weeks | Under an hour, unattended |
| Data completeness | Partial exports, re-sent files, stale by go-live | Complete and current, in one pass |
| Engineering | Would own scrapers and anti-bot | Zero scraper maintenance |
Every system a landlord might leave
The same Deck agent pattern applies to every system Kompas wins customers from, whether that’s Buildium, Hopem, Building Stack or Yardi. Each new source is a new Deck workflow, set up in hours, not a new engineering project, and “we can’t get your data out” stops being an answer anyone has to give.
“Whatever system a landlord is on, the answer to ‘how do we get your data over’ is the same link.”
Cory Friedman, Kompas
Frequently asked questions
How do you migrate lease files out of a legacy property management system?
Kompas uses Deck. The landlord logs into their old system once through the Deck connector, and Deck’s agent opens each tenant’s lease and downloads every file, at about 5 to 6 seconds per lease.
Can an AI agent handle 2FA on a legacy property management system?
Yes, with one step from the landlord. Some legacy property management systems send a 2FA secure link by email, even with saved cookies. The Deck connector walks the landlord through pasting that link once, and Deck’s agent runs the full migration after that.
How long does it take Deck to migrate a 300-tenant portfolio?
Under an hour. In a sample Kompas migration, Deck moved 301 tenants and every lease file in about 53 minutes, unattended.
Are AI agents reliable enough for production data migrations?
Kompas has built Deck directly into its customer onboarding to run live migrations. In a sample run, Deck’s agent moved 301 tenants and every lease file in about 53 minutes, unattended, and Kompas’s team tracks migrations in the Deck console.
Does Kompas see the landlord’s login credentials?
No. The landlord signs into their old system through the Deck connector, and Kompas never sees or stores the credentials.
Losing deals to “how do we get our data out?”
Watch a migration agent run on the system your customers are leaving.
Watch a migration