The IT Stack Behind a Real Estate Transaction
Real estate brokerages run on a collection of cloud platforms, local systems, and integrations that most generic IT providers have never seen in production. A transaction from listing to close touches:
- CRM — Follow Up Boss, LionDesk, BoomTown, Salesforce, or custom-built
- Transaction management — Dotloop, SkySlope, zipForms/TMS
- eSignature — DocuSign, Authentisign, or built into the TMS
- MLS access — Via web portal and often integrated into TMS or CRM
- Document storage — SharePoint, Google Drive, or TMS-native storage
- Back-office accounting — Brokermint, Lone Wolf, QuickBooks
- Communication — Email, text, sometimes dedicated transaction coordinator messaging tools
An IT provider for a real estate brokerage needs to understand how these systems connect and what happens when one of those connections breaks mid-transaction.
Dotloop: Infrastructure and Common Issues
Dotloop is a cloud-based platform — there's no local software to install or manage. The IT requirements are largely network and device-level:
- Browser compatibility — Dotloop is Chrome-optimized; IT should standardize on Chrome or Edge and manage extension conflicts
- Print driver conflicts — The most common Dotloop complaint is PDF generation failures, which are almost always caused by conflicting PDF/print drivers on agent devices
- Mobile device management — Agents access Dotloop on personal phones and tablets; MDM enrollment ensures company Dotloop data can be wiped if a device is lost
- SSO integration — For brokerages on Microsoft 365 or Google Workspace, SSO to Dotloop simplifies access management and improves security posture
- Brokerage admin access controls — Managing who has loop access, loop visibility, and admin rights is an IT governance function that many brokerages handle informally
SkySlope: Infrastructure and Common Issues
SkySlope is also cloud-based. IT considerations specific to SkySlope:
- SkySlope DigiSign — SkySlope's native eSignature has different browser requirements than the base platform; ensure compatibility testing before rollout
- Forms library management — SkySlope Forms requires current state forms library; IT should have a process for verifying forms are current when state associations update them
- API integrations — SkySlope integrates with Lone Wolf, QuickBooks, and various CRM platforms via API; these integrations require ongoing maintenance when vendor APIs change
- User provisioning at scale — Large brokerages adding agents in bulk need a provisioning process; IT should build this into the new agent onboarding workflow
MLS Integration: The Underestimated Complexity
MLS integrations are often the source of the most frustrating, hardest-to-diagnose IT issues in real estate. The reasons:
- MLS systems are heterogeneous — Different MLSs run on different platforms (Matrix, Flexmls, Paragon, Stellar MLS). Each has different data formats, API endpoints, and authentication methods.
- RESO Web API vs. RETS — Many MLS systems are still running RETS (Real Estate Transaction Standard), which is being phased out in favor of RESO Web API. The transition creates integration failures when MLS systems update.
- IDX feed dependencies — Brokerage websites with IDX feeds depend on MLS data feeds that can break when the MLS updates its infrastructure. This is a business-critical issue that most brokerages don't notice until their website stops showing listings.
Common MLS integration failure pattern: MLS upgrades its platform or changes API credentials. Your transaction management platform and IDX website both break simultaneously. Neither vendor has notified you in advance. Your IT provider needs to be monitoring for these changes proactively — not waiting for agents to report listing search failures.
Agent Offboarding: The Most Neglected IT Process in Real Estate
Agent turnover in real estate is high. Each departure creates IT obligations that most brokerages handle inconsistently:
- Revoke access to transaction management platform (Dotloop, SkySlope) within 24 hours
- Transfer open transaction files to active agent or broker admin
- Archive work email before disabling the account (state record retention requirements vary; 3 years is common)
- Remove from brokerage CRM and mark as inactive (do not delete records)
- Remote wipe company data from any enrolled personal devices via MDM
- Revoke MLS access credentials if the brokerage manages agent MLS membership
- Update back-office accounting system to reflect the departure date
- Document the offboarding steps for compliance records
An IT provider should give your brokerage a formal offboarding checklist and, ideally, the ability to execute most of these steps with a single workflow — not a manual process that depends on the managing broker remembering every step.
Document Retention: What You're Required to Keep
Real estate document retention requirements vary by state and transaction type. Common minimums:
| Document Type | Typical Retention Period | Format Requirements |
|---|---|---|
| Transaction files (purchase/sale) | 3–7 years (state-specific) | Must be legible; electronic OK in most states |
| Trust account records | 3–10 years (state-specific) | Usually must match bank statements; audit-ready |
| Agency disclosure forms | 3 years minimum in most states | Signed copies required |
| Advertising records | 1–3 years | Varies; digital archives acceptable |
Frequently Asked Questions
What transaction management software do real estate firms use?
The most common platforms are Dotloop, SkySlope, zipForms/zipTMS, DocuSign for real estate, and Brokermint for back-office. An IT provider supporting real estate should be familiar with at least Dotloop and SkySlope, as these are the dominant platforms.
How do transaction management platforms integrate with MLS systems?
Most platforms integrate via RESO Web API or RETS feeds, depending on the MLS. These are data feeds, not just software installs — they require network configuration and ongoing maintenance when MLS systems update their API endpoints.
What happens to transaction files if an agent leaves the brokerage?
Transaction files belong to the broker. When an agent departs, their TMS access should be revoked within 24 hours, files transferred to an active agent, and email archived before disabling. MDM should wipe company data from personal devices. A formal offboarding procedure prevents missing steps that create compliance exposure.