If you run a legacy property ERP today
The question isn’t whether it works. It’s what it costs you to make it work.
Legacy systems are capable, and surrounded by workarounds: the spreadsheets, the consultants, the per-module invoices, the API you can’t call. Here is where we differ, stated so you can check each line against your own system.
What it costs
Not the licence. The whole bundle: modules, consultants, the people who reconcile what the software left behind.
Legacy property ERPAcreum
PricingLegacy ·Quote-only, licensed per moduleAcreum ·One price for the whole system. Every module, the agent and the API included.
ImplementationLegacy ·A project with a services team and a timeline in quartersAcreum ·A fixed-fee migration reconciled to your certified close; a rerun costs an afternoon.
Adding an entityLegacy ·Implementation workAcreum ·A form. Intercompany, ownership and consolidation follow from it.
Headcount the software assumesLegacy ·A back office that finishes what the system started, in spreadsheetsAcreum ·A controller who reviews a queue that is mostly already handled.
The close
The month-end is where the difference shows up on a calendar.
Legacy property ERPAcreum
Closing the monthLegacy ·AP, AR and GL closed separately, often per property; tie-outs in ExcelAcreum ·One close per period. Twelve checks re-run against the ledger until they pass.
Sub-ledger tie-outsLegacy ·A spreadsheet somebody maintainsAcreum ·A check. AP, AR, banking and fixed assets tie to the GL or the close says why not.
IntercompanyLegacy ·A month-end true-upAcreum ·Both sides post at once; due-to nets due-from to 0.00 continuously.
Reopening a periodLegacy ·Discouraged; documented by exceptionAcreum ·Reopen supersedes the close package; the re-close diffs it.
ConsolidationLegacy ·A reporting exercise, often outside the systemAcreum ·Consolidation groups with eliminations computed from the reciprocal postings.
Real estate itself
The parts a generic ERP cannot do at all, and a legacy one does with services.
Legacy property ERPAcreum
CAM reconciliationLegacy ·A season, a workbook, and a reviewAcreum ·Seconds. Every lease against the actual pool, showing its work, flagging what it could not allocate.
LeasesLegacy ·Terms keyed into billing; amendments re-keyedAcreum ·Typed terms and amendments resolved as of any date. The schedule, the rent roll and the recovery run read the same answer.
EscalationsLegacy ·A reminder and a manual bumpAcreum ·The index arrives from the BLS; the escalation is proposed the day it prints, floor and cap applied.
Debt and capitalLegacy ·Separate modules or separate systemsAcreum ·Loans, rate resets, covenants, capital accounts, waterfalls and distributions on the same ledger.
DealsLegacy ·A CRM and a closing binderAcreum ·Pipeline to a posted closing entry; entity, property, loan and leases created from the deal.
Your data and your tools
Whose system is it, once the invoices are paid?
Legacy property ERPAcreum
APILegacy ·Partner-gated interfaces, licensed separately, usually SOAPAcreum ·REST, self-serve keys, the same endpoints the UI uses. Read and write.
Connecting Claude or another AI toolLegacy ·Read-only connectors, where offeredAcreum ·Read and write, inside the same scopes and approval rules a person has.
Your data elsewhereLegacy ·Reports and exportsAcreum ·Your ledger, over your API, into your warehouse. No per-interface licence.
AILegacy ·Assistants recommend; a person keys the changeAcreum ·Agents match, remind, draft and post under your approval rules, on an immutable ledger.
Audit trailLegacy ·Change logs of varying depthAcreum ·Every journal immutable and period-gated; every action attributed to a person, a key or the agent.
What switching looks like
A fixed fee, a mapping you approve, and a rerun that costs an afternoon.
Acreum proposes the account mapping; your controller approves it account by account. We load through the product API, reconcile to your last certified close, throw it away, and run it again until it ties. The last one tied to 0.00 across several hundred entities.