Connecting fragmented systems: the integration problem in property operations

Ask a property management team which systems they use, and the list is often long: an accounting package, a leasing tool, a maintenance system or just a spreadsheet, a tenant portal, email, WhatsApp. Each tool does its own job. The trouble starts at the edges, where information has to move from one to the next.

What fragmentation costs

• Retyping. The same tenant detail is entered three times, with three chances for a typo.
• Delay. A request is stuck until somebody copies it across.
• Conflicting numbers. Each system gives a slightly different answer, so meetings are spent reconciling.
• No single view. Nobody can see the full story of a unit, an owner or a request.

Start with the handovers

Before comparing products, draw the journey of one thing, such as a maintenance request or a new lease. Mark every handover: from tenant to call centre, from call centre to supervisor, from supervisor to contractor, from contractor to finance. These are the points where integration matters. List what information has to cross each one.

Decide who owns what

For each type of data, pick one owning system. The tenant record lives here, the lease lives there, the invoice lives somewhere else. Other systems read it, they do not keep their own copy and edit it. This single rule prevents most of the conflicts.

Options for connecting

Built-in integrations. Many products offer ready connections to others. Check how deep they go: do they sync one field or the whole record, and in which direction?

Integration tools. Middleware can pass data between systems without custom code. Good for common cases, limited for unusual ones.

Custom connections. When you need something specific, a small custom link using the systems' APIs can work well. It needs someone to maintain it.

Replacing a system. Sometimes the honest answer is that one system is the problem and should go.

Do it in order

Choose the handover that causes the most pain or delay and fix that first. Measure the result, for example the time from request to assignment. Then move to the next. Trying to connect everything at once usually stalls.

Two cautions

First, do not connect dirty data. Clean the records that will flow across, or you will spread errors faster. Second, plan for change. Systems get replaced. Keep the logic of the connection documented, so it can be rebuilt without starting from zero.