How to Switch Property Management Software Without Losing Resident Data
The safest way to switch property management software is a staged migration of two to four weeks. You set up the new system, move current data first, run both systems side by side while you check balances and certifications, and only then cut over. Done that way, every active lease, balance, and compliance record arrives intact, and residents barely notice the change.
If you’re reading this, you’ve probably already decided your current software isn’t working. What’s holding you back is the switch itself. Will it take months? Will something important get lost? Will residents get confused about rent? Will it land in the middle of recertification season?
Those are fair concerns. We’re a software vendor, so we have a stake in this, but the steps below hold no matter which platform you move to: what to migrate, what to expect, what goes wrong, and how to avoid it.
When it’s time to switch
Switching software takes real effort, so it’s worth being sure. These are the signs that staying is costing you more than moving would:
- Your true cost has crept up. Add your base subscription, every add-on module, payment processing fees and the staff hours lost to workarounds, then divide by your unit count. That’s your real per-unit cost, and it’s usually higher than the number on the contract. Our Software Cost Comparison does the math for you.
- Your compliance workflows leave gaps. If the platform doesn’t fully support the affordable housing programs you run, or makes certifications harder than they should be, every month you wait adds audit exposure. The Audit Readiness Checker is a quick way to see where you stand.
- Your staff fight the software. Long training times, confusing screens and too many clicks for routine work are real costs, even if they never show up on an invoice.
- Your vendor is heading somewhere else. Price increases without improvements, features being retired, or a shift toward a market that isn’t yours are all warning signs.
If two or more of these apply, the disruption of switching is likely smaller than the cost of staying. For a full checklist of what to look for in a replacement, see how to evaluate property management software for affordable housing.
Comparing options? See how ExactEstate stacks up against Yardi, RealPage, AppFolio, Entrata, MRI, ResMan and Buildium.
Before you switch
Most migration problems start before the first file is exported. This is the prep work that’s easiest to skip and most regretted later.
1. Inventory your data
List everything you have, by category:
- Residents: current and former residents, household members, emergency contacts
- Leases: current leases, lease history, renewal dates, rent and deposit amounts
- Financials: chart of accounts, current balances, transaction history, security deposits, prepaid balances, open charges, AP invoices, vendors
- Compliance: current TICs and HUD-50059s, recertification schedules, certification history, TRACS data, unit designations
- Documents: signed leases, compliance forms, inspection reports
- Work orders: open work orders, history, vendor assignments
For each category, decide whether you need to migrate it or just be able to look it up. For older history, keeping the old system available read-only is often better than moving every record.
2. Decide what has to be ready on day one
Sort your data into three groups:
- Needed on day one: current residents, active leases, current balances, chart of accounts, property and unit structure, active certifications, upcoming recertification dates, open work orders
- Can follow within 30 days: transaction history, vendor records, document archives, former residents, work order history
- Nice to have: multi-year financial history, old prospect data, documents from properties you no longer manage
This step is what turns a three-month migration into a three-week one. Most delays come from trying to move everything at once.
3. Export your data
Every platform lets you export data, but the quality varies a lot.
- Export: resident and household data, leases, chart of accounts, balances, transaction history, property and unit structure, certification data, vendors and any custom fields you rely on.
- Format: CSV or Excel. Use bulk export tools if your vendor has them. If not, export report by report.
- Watch for: data that only lives inside reports, custom fields that don’t appear in standard exports, compliance history that needs a special request, and payment data held by a separate processor.
Tip: Export twice, a week apart, and compare the files. That catches records that were mid-change the first time.
4. Tell the people who need to know
- Your team: Share the timeline, what’s changing and what the learning curve will look like. Pick two or three strong users to train first. They become your in-house help during rollout.
- Residents: Send a short, calm notice covering when the change happens, the new resident portal and payment link, whether they need to re-enroll in autopay, and who to call with questions.
- Owners and investors: Let them know reporting will continue without a gap, and avoid cutting over in the middle of a quarterly reporting cycle.
- Contract Administrator and state agency: On HUD-assisted properties, make sure TRACS submissions are set up from the new system before cutover, so no monthly voucher is missed. Our practical guide to HUD TRACS integration covers what that setup involves. Check whether your state agency needs to know about the change for LIHTC reporting.
- Vendors: If vendors invoice or receive work orders through a portal, give them the new access details.
Pick your cutover date carefully
The timing of the switch matters as much as the plan. Avoid cutting over:
- During a heavy recertification month. Look at your recertification calendar and pick a quieter stretch.
- At month-end or during rent collection. A mid-month cutover gives you time to fix payment issues before rent is due.
- Around January 1, 2027. That’s when HUD’s mandatory compliance date for HOTMA Sections 102 and 104 arrives, along with new inflation-adjusted figures. Either finish the switch well before then, so the new system handles the change, or wait until after your first round of January certifications is done. Not sure how ready you are? Take the HOTMA Compliance Assessment, and see our post on TRACS 203A and the certification bottleneck.
The migration, week by week
Week 1: Set up the structure
This is setup, not data migration. It builds the structure your data will land in.
Week 2: Move current data
- Import current residents and households.
- Import active leases and current balances.
- Load your recertification schedule and active certifications.
- Enter open work orders.
This is where most of the hands-on work happens. On a platform built for bulk imports, it takes days rather than weeks.
Week 3: Check everything and run both systems
Run the old and new systems side by side. The old one stays available for reference, and new work happens in the new one.
- Reconcile resident balances. This is the most important check. If balances don’t match, find out why before going further.
- Run a trial rent charge in the new system and compare the results with what you expect.
- Test payments with a few transactions before moving every resident to the new portal.
- Compare compliance reports for any certifications processed during the overlap. Our guide on how software simplifies HUD and LIHTC compliance reporting explains what those reports should show.
Week 4: Cut over
- Switch residents to the new portal and send payment instructions.
- Point listing feeds and your property website to the new system.
- Process all new transactions in the new system only.
- Keep the old system available read-only for at least 90 days. Six to twelve months is safer if you may need it for an audit lookback.
What goes wrong, and how to handle it
Balances don’t match
This is the most common issue. It usually happens for one of three reasons:
- Transactions were posted after the export. Set a firm cutoff, freeze posting in the old system, then export.
- Deposits are handled differently. Reconcile deposits separately and check the mapping before import.
- Credits, prepayments or concessions were recorded differently. Run an AR aging report from both systems on the same date and reconcile line by line. A platform with built-in accounting makes this much easier, since charges and payments post to the same ledger.
Compliance data doesn’t come across cleanly
Recertification schedules may not transfer neatly, older certification history may need manual entry, and TRACS data may need to be remapped to the new unit structure.
Prioritize anything due in the next 120 days, since that’s when HUD’s first recertification notice goes out. Older certification history matters for audits, but it doesn’t need to be in the new system on day one as long as the old system stays available. For smaller HUD properties, our post on what manual TRACS submissions actually cost shows why getting this right matters.
Autopay stops
Autopay enrollments don’t carry over between systems, so residents have to re-enroll. Tell them at least two weeks before cutover, keep re-enrollment simple, and have staff ready to help. Track enrollment daily after the switch and follow up with anyone who hasn’t signed up.
Staff slow down at first
Your team knows the old system by heart, so expect a short productivity dip even if the new one is better. Train your two or three strongest users first, and choose a system your team can learn in days. If a new platform needs weeks of training, you’re trading one problem for another.
What to expect from ExactEstate
Here’s how our implementation works.
- We load your data for you. Send us your setup workbook and exports, and the onboarding wizard matches your old report columns automatically, using more than 1,000 column-name variations.
-
Fast setup once the data is in. Each property loads in about 15 to 30 seconds, and most customers are live in three to seven days once we have their data. The rest of the four weeks focuses on parallel running, data validation, and resident re-enrollment.
-
Compliance is set up property by property. Each property gets its own program rules, and certifications for TRACS, MINC, and state TIC forms are built from the household record. This approach helps property management teams streamline certification workflows, reduce manual processes, and manage compliance requirements more efficiently.
- Live training from our team at launch. After go-live, the EEva assistant answers how-to questions inside the screen you’re on, and support tickets go to people who understand property operations, Monday through Friday, 9 AM to 5 PM ET.
- Routine work takes about three clicks. Your team reaches daily lists like open work orders and the recertification queue in a few clicks from the home screen. With EEva Compliance Intelligence, they can also ask program questions and get answers grounded in the property’s own compliance profile.
- You own your data. Export any report as CSV, Excel, PDF or JSON at any time. If you ever leave, you get a full export in open formats, and deletion is confirmed in writing.
More detail is on our Implementation & Security page.
Is the switch worth it?
Here’s a quick way to check.
- Work out your real per-unit monthly cost today: base subscription, add-ons, transaction fees, training and the staff time spent on workarounds.
- Compare it with ExactEstate’s published price: $3 per unit per month for Core, or 5foraffordablehousingproperties(3 Core plus $2 for the Affordable Housing line, which covers every program a property carries). There’s a $300 monthly minimum.
- Multiply the difference by your unit count, then by 12. That’s your yearly savings, before counting the staff time you get back.
The Savings Calculator estimates fee, payment and compliance savings together, and Pricing has the full price list.
Frequently asked questions
How long does it take to switch property management software?
Plan for two to four weeks from setup to cutover. The system setup itself can take as little as three to seven days once your data is ready. Most of the remaining time goes to running both systems in parallel, checking balances and helping residents re-enroll in payments.
Do residents have to re-enroll in autopay?
Usually, yes. Autopay enrollments don’t transfer between platforms. Give residents at least two weeks’ notice, make re-enrollment simple, and follow up with anyone who hasn’t signed up after cutover.
What happens to TRACS submissions during the switch?
Make sure the new system is set up to submit through your Contract Administrator before you cut over, and time the switch so a monthly voucher isn’t caught between systems. Process the month’s certifications in one system or the other, not split between both. See our TRACS software page for how ExactEstate handles submissions.
Do we need to migrate all of our historical data?
No. Move current residents, leases, balances, active certifications and open work orders first. Older history can follow within 30 days, or stay in the old system read-only for audit lookback.
Should we switch before or after January 1, 2027?
If you can, finish well before. HUD’s mandatory compliance date for HOTMA Sections 102 and 104 and the new 2027 figures both take effect January 1, 2027. Switching in December or early January means handling two big changes at once. HUD’s Multifamily HOTMA page has the latest guidance.
How do we make sure compliance figures are right in the new system?
Check that it uses HUD’s current-year amounts, not the base figures in the regulation text. For example, the asset self-certification threshold under 24 CFR 5.618 is $52,787 for 2026 and $54,898 from January 1, 2027, per HUD’s published table. Run a few test certifications in the new system and compare them against the old one before cutover.
Is this different for smaller portfolios?
The steps are the same, but smaller operators often have less staff time to spare during a switch, which makes a short setup and hands-on data loading more important. Our post on why small-to-mid portfolio operators get left behind by property management software covers this in more depth.
What happens to our data if we leave ExactEstate later?
It’s yours. You can export reports in CSV, Excel, PDF or JSON at any time, and at contract end you get a full export of your data and documents in open formats, with deletion confirmed in writing.
See what a migration would look like for your portfolio. Book a demo and we’ll walk through your properties, programs and timeline.
Sources
- 24 CFR 5.618 — the regulation text — Electronic Code of Federal Regulations
What changed
- — 2 cited figure(s) match the current regulation text
- — 1 cited figure(s) match the current regulation text
- — 1 cited figure(s) match the current regulation text
About the author
Matt Hoskins is the CEO of ExactEstate. He grew up in his family’s affordable housing management company and has spent his career on the operator side of LIHTC, HUD and Section 8 properties. ExactEstate is the result: compliance-first property management software for affordable housing, with TRACS submission built in.
