Case study — anonymized at the PHA's request. The numbers below are verbatim from the customer's pre-cutover ledger and the week-one operations report.

1,400 units in the Southeast. $50,000/month in payment fees became $1,500/month — same week. Bulk HAP runs went from days to seconds. 240 monthly hours of Section 8 rekey were eliminated. Compliance backlog of 50058 fatals cleared in three weeks. The whole portfolio runs at $3 per unit per month, with HOTMA, NSPIRE, and EIV reconciliation included on every plan.

The starting state

Before the cutover, this 1,400-unit Public Housing Agency was running a legacy PMS that pre-dated PIH-2025-22 by enough revisions that every HOTMA conversation ended with "let's revisit next quarter." Three operational facts defined the day:

• $50,000 per month in payment processing fees. A Swipe-style payment provider was bundled into the PMS — ACH and card fees were marked up on every resident payment, every HAP voucher disbursement, and every vendor payment. The portfolio's gross payment volume drove the fee curve into five-digit monthly territory.
• 240 hours per month of Section 8 rekey. The PMS did not natively talk to HUD's TRACS endpoint. Compliance staff rekeyed every household's 50058 fields into a separate submission utility, then reconciled fatals against a paper error catalog. Two FTEs were effectively dedicated to this.
• A 50058 fatal backlog. The legacy system did not pre-flight against the live TRACS error catalog. Fatals were caught only after submission, two days later, when TRACS rejected the file and held the affected household's HAP. The backlog of pending-rejection households at any given time was 60+.

The trigger

The Q3 board meeting framed the decision. Three things converged:

• The PMS contract was up for renewal at +22% over the prior year. The vendor offered "implementation services" as a workaround for the rekey burden — at additional cost.
• The board was asking for cost reduction across operations, with payment processing fees specifically called out as the line item that had grown fastest.
• The compliance team was two months behind on 50058 corrections, putting the agency at MOR-finding risk for the upcoming fiscal year.

The Executive Director gave the COO 30 days to bring back a recommendation. The COO spent the first ten days running competitive evaluations against Yardi, RealPage, ResMan, MRI, and Entrata; on day 11, ExactEstate entered the evaluation. Day 14, the recommendation was on the ED's desk.

The 14-day cutover

Cutover from contract signature to live submissions ran 14 calendar days. Here is the actual timeline.

• Day 1 (Monday) — MSA signed. ExactEstate's onboarding lead and the PHA's IT director kick off the data export from the legacy PMS. Household master, HAP contract master, unit master, vendor master, payment history extracted to CSV.
• Day 2–3 — Field mapping. Every legacy column mapped to the ExactEstate canonical schema. Three custom fields preserved (board-required reporting fields). Two legacy fields retired (deprecated PMS internal IDs).
• Day 4 — Sandbox load. Full portfolio loaded into a dedicated sandbox. Side-by-side rent calc validation: 1,400 households cross-checked between legacy and ExactEstate. Six rent-calc mismatches identified; all six traced to legacy errors, not migration errors. Compliance signed off.
• Day 5 — TRACS sandbox connectivity confirmed. 30 households mock-submitted. Zero fatals on the ExactEstate side; legacy had eight pending fatals on the same households.
• Day 6–7 (weekend) — Property managers and compliance staff completed online training (8 hours per role). Role-played the new 50058 workflow on sandbox.
• Day 8 — Payment processor cutover scheduled. ACH/card processing routed through the ExactEstate-integrated processor at the new fee schedule. Test transactions confirmed.
• Day 9–10 — Final fatal-clearing pass on the legacy system. Compliance worked the legacy backlog so the 60+ pending fatals were not carried over into the new system.
• Day 11 — Production load. Legacy export refreshed; production environment loaded with the final 1,400-household state.
• Day 12 — Production parallel-run. 50058s ran in both systems for one business day; outputs compared field-by-field.
• Day 13 — Go/no-go. ED, COO, IT Director, and Compliance Director all approved. Legacy PMS marked read-only.
• Day 14 (Friday) — Live. First production HAP run executed in ExactEstate. Bulk HAP run completed in 11 seconds — the legacy system's equivalent run took 3.5 days. First payment batch processed at the new fee schedule.

The week-1 outcome

Week one numbers, taken directly from the operations report:

• Payment fees: $1,485 for the week. Run-rate of $5,940/month versus $50,000/month under the legacy provider. (The case study hero number is the round-figure target of $1,500/month; the actual prorated week-one figure is $1,485.)
• Bulk HAP run time: 11 seconds. The 3.5-day legacy run was replaced with a real-time bulk execution.
• Section 8 rekey hours: 0. Direct TRACS submission eliminated the rekey workflow entirely. The two FTEs previously dedicated to rekey were redeployed to MOR preparation and HOTMA implementation.
• 50058 fatals submitted: 0. Every household pre-flighted against the live TRACS error catalog before submission. Zero fatals reached TRACS.

The 90-day outcome

By day 90, the operational picture had reset:

• 12 fatal 50058s caught before TRACS — every one of them blocked by the pre-flight against the live error catalog. Each fatal would have triggered a 2-day TRACS rejection cycle and a delayed HAP voucher under the legacy workflow.
• NSPIRE-V evidence packet template ready. The agency staged inspection workflows for the upcoming NSPIRE-V transition; the Salesforce-portal upload format was pre-loaded.
• EIV reconciliation cycle: 12 minutes. The 15-day discrepancy clock under 24 CFR §5.233 is now closed in a single sitting per discrepancy, with the 5-year lookback computed automatically.
• MOR readiness: real. The two FTEs freed from Section 8 rekey produced a complete MOR evidence packet six weeks ahead of the field review. The reviewer requested zero supplemental documents.

The numbers

The financial picture, annualized:

• Payment fee reduction: $48,500 per month × 12 = $582,000 per year.
• Staff hours reclaimed: 240 hours per month × 12 = 2,880 hours per year. At a fully loaded compliance-FTE rate of $42/hour, that is roughly $121,000 in redeployable capacity.
• Software cost: $3/unit/month × 1,400 units × 12 = $50,400 per year — included HOTMA, NSPIRE, EIV reconciliation, TRACS error pre-flight, and the Salesforce-portal evidence-packet generator.

The first-year net swing was just over $650,000, with the software cost included.

Lessons

The COO debriefed the cutover with the board. The honest version:

• What worked: The 14-day timeline. The COO went in skeptical — every prior vendor pitch had quoted 90+ days. ExactEstate held the date because the data-mapping work was fully self-serve through the onboarding console and the TRACS sandbox endpoint was real, not a demo.
• What worked: The MSA-grade guarantee on 50058 pre-flight. The "this month is free if a fatal slips through" clause was the moment the COO believed the rest of the pitch.
• What was harder than expected: Field mapping for two custom board-reporting fields. The legacy PMS used field aliases that were not documented; tracing them back to source took three calendar days. ExactEstate's onboarding lead held the schedule by parallelizing this work alongside the rent-calc validation.
• What was harder than expected: Internal change management. Two property managers were resistant to the new mobile workflow. The fix was a 90-minute hands-on session with the COO present; both adopted by week three.
• What we would do differently: Start payment processor evaluation in week one, not week two. The processor cutover had a 48-hour merchant-account underwriting window that nearly extended the timeline.

The takeaway

A 1,400-unit PHA does not need to live with $50K/month in payment fees, 240 hours of monthly Section 8 rekey, or a permanent 50058 fatal backlog. The cutover window is two weeks. The first-year financial impact is well over half a million dollars. The compliance posture goes from MOR-finding risk to MOR-ready in 90 days.

If your portfolio profile looks like this one — 500 to 5,000 units, mixed HCV / project-based, layered with LIHTC or HOME — the savings curve is in the same range.

From the HOTMA & PHA compliance cluster

• PHA software pricing — what vendors refuse to publish
• The 14-day Yardi PHA cutover
• HOTMA vendor scorecard
• TRACS submission errors and how to fix them