A practitioner's guide to migration — the good, the ugly, and what actually works. Ask ten property managers why they haven't switched platforms, and nine will give you some version of the same answer: “Because switching sounds like a nightmare.”
They're not wrong. They're also not right in the way they think they are.
Migrating property management software is genuinely hard. But most of the horror stories you've heard come from two things: bad migrations that didn't have to be bad, and bad decisions before migration even started. The actual mechanics — moving units, residents, ledgers, vendors, and compliance records from one system to another — are well-understood work. The difference between a migration that takes days and one that drags on for a year is mostly about what you know going in. Learn more about how to switch your property management software in just 3 days.
This is that field guide.
Why most migration stories sound apocalyptic
The property managers loudest about their bad migrations usually share one of three experiences:
- They switched to an enterprise platform that required months of “implementation,” during which nothing moved except the invoice date.
- They tried to DIY a migration with a spreadsheet and four Red Bulls.
- They picked a vendor whose “support” was a ticket queue and a 48-hour SLA.
Joe Gieringer at Hocking View Apartments lived the first one. When he acquired the 44-unit affordable housing property in Athens, Ohio, in 2022, he signed with RealPage to handle HAP voucher processing. Four to five months later, his team was still waiting to be onboarded — and still couldn't accept online applications. They eventually switched to another platform and started processing vouchers within days. His first attempt cost him most of a year. Explore case studies to see how property managers streamline operations.
None of those are inherent to migration. They're inherent to those specific choices. A well-scoped migration with the right partner is a days-to-weeks project, not a year. But you have to know what you're getting into.What actually moves during a migration
Here's an honest breakdown of the data involved. Some of it moves cleanly. Some of it doesn't move at all. Both categories are fine as long as you know which is which before you sign anything.
Cleanly migratable
Properties, buildings, units, floor plans. This is the cleanest part of any migration. Standard bulk import via CSV or Excel. If your new vendor doesn't have a bulk import tool for this, walk away.
Resident and lease records. Current residents, past residents, lease terms, move-in dates, and household composition. Clean if the source system lets you export, messy if it doesn't.
Chart of accounts and GL balances. Moves clean when you're starting a new fiscal period. Moves messy when you're mid-month. Don't migrate mid-month.
Vendor records. Names, W-9s, insurance certificates, contact info. Clean import — but insurance expiration tracking resets unless your new system supports importing expiration dates.
HUD data. If you're on a HUD property and your new platform supports MAT file import, your entire HUD dataset loads in one operation. If it doesn't, you're typing. Ask about MAT support specifically.
Migrates with care
Ledger history. Charges, payments, and balances going back years. This is where things get interesting. You have three choices: bring everything over (slow, expensive, messy); bring opening balances only (clean, but you lose visibility into payment history); or bring opening balances plus the last 12–24 months (the sweet spot for most operators). Pick one, document it, stick to it.
TIC and certification history. For affordable housing operators, this is the migration anxiety trigger. Your new system needs to hold historical certifications, recertification dates, and compliance timestamps — because HUD will ask. The question to ask your new vendor: “Can I import my historical TICs as PDFs with searchable metadata?” If the answer is vague, push harder.
Work order history. Open work orders must move. Closed work order history is a nice-to-have. Don't burn a week of migration time on 2019 work orders.
Documents. Signed leases, executed TICs, correspondence, and inspection reports. This is the most commonly forgotten migration item. Most systems store these as attachments to resident records, and most migrations skip them. Make sure document migration is in writing.
Usually doesn't migrate
Payment method tokens. Auto-pay enrollments almost never transfer. Residents will need to re-enroll in the new system. Plan a 30-day resident communication plan for this—it's the number-one source of resident complaints during migration.
Third-party integrations. Your screening vendor, payment processor, e-signature tool, and TRACS submission integrations all need to be reconnected. Some of this is straightforward. Some of it isn't. Get a written integration plan from your new vendor before go-live.
User sessions and portal accounts. Residents and owners will need to reset passwords. Staff will need new accounts. This is normal. Schedule it for a Friday so the weekend absorbs the confusion.
Custom reports. Any custom reports you built on the old system need to be rebuilt. This is usually fine — most platforms have better reporting than the one you're leaving.
Realistic timelines
“Live in days” means different things to different vendors. Here's what the phrases you'll hear actually translate to:
Days (1–5 business days). Realistic when: your portfolio uses clean bulk imports, your new vendor has a dedicated onboarding CSM, and you're starting a new fiscal period. This is what ExactEstate's implementation looks like for most affordable housing operators — MAT file import for HUD data, Excel-based bulk import for chart of accounts and units, CSV bulk import for residents, and configuration of program rules done in parallel. Requires your data to be in reasonable shape coming in.
Two concrete examples of what “days” actually look like. NuRock Companies migrated across 24 affordable and multifamily communities in Florida, Georgia, and Texas by uploading a single CSV file with their account information. “Switching to the new software was a snap,” said NuRock President Becky Lively. Alpha Management, a 362-unit portfolio in southern Maine that had been on the same property management software since 2004, described onboarding as “excellent” — so smooth their Director of Leasing could “scarcely recall much beyond how well it went.” That's what “days” should feel like on your side of the project.
Weeks (2–6 weeks). Realistic when: your portfolio spans multiple states with state-specific compliance forms, you're bringing three or more years of ledger history, or you have non-standard integrations. Most mid-market migrations land here.
Months (3–6 months). Common when: you picked an enterprise platform that requires a full implementation cycle, your portfolio needs data cleansing before it can move, or the vendor requires every workflow to be redesigned before go-live.
Years. Yes, this happens. It usually means your implementation scope grew past the original contract, the vendor's professional services team is bottlenecked, or nobody on your side owns the project end-to-end.
What drives your actual timeline, in order of impact:
- Data quality going in. Clean exports from your current system shave weeks off every migration.
- Portfolio complexity. Mixed-program properties with layered compliance take longer than single-program portfolios.
- How many properties are live at once. Staggered go-lives are slower but safer.
- Integration count. Every third-party connection is a conversation.
- Staff availability for training. Unlimited training doesn't help if your staff can't attend.
The five things that most commonly go wrong
After dozens of migrations, the same problems come up. Here they are in order of damage.
1. Historical compliance data gets stranded
The scenario: you switch platforms. Your old vendor's contract ends. Six months later, HUD shows up for a MOR and wants to see the TIC records from 2022. You log into the old system to pull them — except your read-only access expired.
This is the single most expensive mistake in property management migrations. Before you sign a cancellation notice, confirm in writing exactly how long you have access to historical records, and download everything relevant the day before that access ends. Every TIC, every 50059, every HAP reconciliation. Store them in your new system or in a secure cloud archive. Assume you'll need them.
If you're switching in the run-up to the January 2027 HOTMA compliance deadline, take inventory of what you have before you move it. Our free HOTMA Readiness Assessment scores eight compliance domains and flags gaps to close pre-migration, not post.
2. Payment migration breaks residents
Auto-pay enrollments don't transfer between payment processors. If residents don't re-enroll on the new system, rent doesn't get paid, and you're the bad guy. Residents blame the software. The software isn't what failed — communication did.
The fix: 30 days before go-live, email every auto-pay resident. 14 days before, email again. 7 days before, call. On the day of go-live, a resident portal banner explaining what to do. If your new platform can't handle resident portal messaging at scale, that's a problem.
3. Opening balances don't tie
You migrate. Your trial balance doesn't match the last report from your old system. You spend the next 45 days chasing a $2,400 variance that turns out to be due to security deposits being recorded differently in the two systems.
Fix it at migration, not after. The pre-migration data validation step — comparing your closing balances in the old system with your opening balances in the new system — is the most important step in the entire project. If your vendor doesn't run this check with you, run it yourself.
4. Mid-month migrations create accounting chaos
You go live on the 17th. Rent was posted on the 1st on the old system. Payments after the 17th post to the new system. Now you're reconciling across two systems for the entire month, your late fee calculations are split, and your month-end close takes three times longer than normal.
Don't migrate mid-month. Pick a fiscal period boundary — the first of the month, the first of the fiscal year, the first of the quarter. Live with the wait. Your accounting team will buy you dinner.
5. Staff adoption stalls at month two
Implementation goes fine. Training happens. Month one, everyone's fine. Month two: the old habits come back — staff workarounds, data entered into the wrong fields, compliance tasks skipped. Adoption fails quietly.
The fix is that your vendor's support has to still be accessible at month two, month three, and month six. If support is a first-line ticket queue that forgets your portfolio's program mix every time you call, adoption will stall. If support is a U.S.-based team that knows your properties, it won't.
What a well-supported migration actually looks like
These are the things to look for — in writing, in the SOW, not in the sales deck:
- A named Customer Success Manager is assigned to your account. Not a pool. A person with a name and a phone number.
- Bulk import tools for your data types. Excel import for the chart of accounts and units. CSV import for residents, vendors, and designations. MAT file import for HUD properties.
- A staging or test environment. You should be able to load your data, look at it, and catch problems before go-live.
- Program-specific configuration. LIHTC income limits, HOME set-asides, Section 8 HAP tracking, USDA MINC — configured and tested before you go live, not after.
- Compliance data validation. Someone on the vendor side physically checks that your TIC history, certification dates, and HUD limits are imported correctly.
- A parallel period. Not always necessary, but offered if you want it. The first full month on the new system is when you find out what didn't quite import right.
- U.S.-based support that answers the phone. Not chat only. Not a ticket queue. A phone that gets picked up by someone who can see your portfolio.
- Unlimited training — for as long as you're a customer. New hires join. Your 2022 training sessions don't help them. Ongoing access to live training matters.
If the vendor can't commit to these in writing, that tells you what the migration will actually feel like.
Your pre-switch checklist
Do these before you sign anything. Whether you pick us or someone else, this list makes your next migration better.
- Export everything you can from your current system, now. Don't wait for the migration. You want to know what you have before you negotiate against the clock.
- Document your integrations. Payment processor, screening vendor, e-signature tool, TRACS submission vendor, and accounting sync. Get the account numbers and admin contacts in one document.
- Identify your fiscal cycle and plan migration around a period boundary. First of the month at minimum. The first quarter is better.
- Get historical data retention commitments in writing. From your old vendor: How long do you have read-only access after cancellation? From your new vendor: what historical data will be imported, and in what format?
- Assign an internal migration owner. One person on your team whose job is to make the migration happen. Without this, things fall between chairs.
- Clean up your chart of accounts before migration. Every stale account you carry over is an account somebody has to maintain forever.
- Write a resident communication plan. At least three touches over 30 days, explaining what's changing and what they need to do.
- Budget for 60 days of parallel access. Even if you don't use it, having it reduces the panic when something doesn't look right on day 12.
The vendor makes the difference
Migration is hard, but it's hard in predictable ways. The property managers who have bad migrations almost always picked the wrong partner or skipped the pre-work. Those with smooth migrations made good decisions before the project started.
The reason you haven't switched isn't that your current system is acceptable. It's that the idea of migrating is scary. The reality is that staying on software you hate has a compounding cost — in wasted staff time, in compliance anxiety, in lost residents who leave because your portal barely works. Every month you delay a migration you know you need, you pay a tax.
If switching is on your mind, the honest version of the conversation starts here: export your data, clean up your chart of accounts, pick a fiscal boundary, and ask every prospective vendor the specific questions above. You'll know very quickly who's serious and who isn't.
We built ExactEstate because this industry deserves better — a platform that actually loads your HUD data on day one, configures your program rules before go-live, and has a phone number that connects to a human who knows what a 50059 is. If that's the conversation you're ready to have, we'd love to have it.
One illustration of what that actually means in practice. When a Hocking View property manager needed bulk rent changes on voucher-side transactions in the middle of leases — a capability that didn't yet exist on the platform — they called. CEO Matt Hoskins said, “No problem. I can build that capability out for you by the end of the day.” That's the kind of conversation you should expect from a migration partner. If you're not getting it, you're talking to the wrong vendor.
Life is too short to hate your property management software.
To talk through your migration specifically, book a demo at exactestate.com.
Matt Hoskins is CEO of ExactEstate, a property management platform built by property managers for property managers. With a background in both property management and engineering, he focuses on intuitive software that simplifies workflows and supports the future of affordable housing.
.jpg)