One schedule across two portfolios, without merging the data underneath.
A property management firm ran roughly 740 units across two separate management platforms: one for owned properties and one managing third-party client properties. The two-platform split existed for a legitimate reason: third-party client data legally could not commingle with the firm's own book. The cost of that separation was that maintenance dispatch had no unified view. The coordinator toggled between two dashboards all day, coordinated the team by phone and text, and had no real schedule at all, just a running list in her head and a lot of "who is at which property right now?" calls.
Integration-first, not replacement-first
The obvious answer was to buy a field-service scheduling product and roll the whole team onto it. That would have cost thousands a month in licensing, forced technicians to learn a second app, and either required merging the two portfolios into one account (breaking client confidentiality) or paying for two separate licenses that still would not talk to each other. Building a thin layer on top of the two existing platforms was cheaper, faster, and (most importantly) kept the account separation that protected third-party client data.
What I built
A dashboard that sits above both management platforms and reads from each without merging anything. The coordinator gets one unified view of every work order that needs scheduling across both portfolios, plus a drag-and-drop day timeline for every technician. Assigning a job to a person and time takes seconds instead of a phone call.
When the coordinator drops a work order onto a technician's timeline, the scheduled time syncs back to the correct source platform so nothing lives in two places. Technicians see their day in one app (property, unit, time, and any notes) regardless of which portfolio the work belongs to. If a job runs over, downstream appointments on that technician's timeline auto-shift so the schedule stays truthful. Approved time off grays out the day; nothing can get dropped onto someone who is not available.
Built to respect the business
- Two portfolios unified in one view without merging the underlying accounts (third-party client data stayed cleanly separated)
- Chose an integration path over a new field-service product, saving thousands per month in licensing
- Coordinator went from switching between two dashboards all day to working from one
- Team went from no shared schedule to a live dashboard visible to everyone in real time
- Technicians use a single app for their day regardless of which portfolio the job belongs to
What this means for multi-portfolio operators
If your business runs on multiple management platforms (for confidentiality, ownership structure, or historical reasons) the instinct to consolidate onto a single vendor is usually the wrong call. The separation exists for a reason, and losing it costs more than the coordination overhead saves. The better move is a thin unifying layer that respects the boundary and gives the humans a single place to work. That is a smaller, cheaper build than a rip-and-replace, and the constraint that made replacement impossible turns into the thing that made this project ship.