Propertybase Salesforce Integration Services: How To Connect Your Real Estate Systems Securely
Propertybase runs inside a Salesforce org, so every listing, inquiry and offer can reach your MLS feed, website, portals, transaction tools and accounting, if the sync is designed well. This guide explains what a Propertybase Salesforce integration covers, how the data moves, how to keep it secure, and how Twopir Consulting delivers it.
Key Takeaways
- Propertybase Salesforce Edition is a managed package that lives inside a Salesforce org. A Propertybase Salesforce integration therefore runs on Salesforce's own APIs, alongside Propertybase's lead-capture and portal-syndication tools.
- The systems most brokerages connect are the MLS feed, the website, listing portals, transaction and e-signature tools, accounting and commission, and marketing automation.
- Use the built-in tools first (Front Desk, Portal Syndication, Website Listings Sync), then a packaged connector or middleware, and custom code only when neither meets the requirement.
- Every field held in more than one system needs one owner, a sync direction, a frequency, a conflict rule and a failure alert. Without them, the data drifts.
- Secure integrations use a dedicated API-only integration user, the OAuth client credentials flow, named credentials and least-privilege permission sets, never a shared admin login.
- Propertybase does not support some standard Salesforce objects, including Lead, Opportunity and Campaign. Connectors that expect them have to be remapped.
Most real estate operations leaders don't wake up wanting an integration project. They want agents to stop calling buyers about homes already under contract, to stop someone re-keying MLS exports twice a day, and to see commission figures that match the accounting system. Each of those problems is a data-synchronization problem, and in a Propertybase brokerage the fix runs through Salesforce.
This guide is for owners and operations managers who are weighing Propertybase Salesforce integration services. It explains which systems to connect, how the data moves, what keeps it secure and accurate, and what to expect from a partner, so you can scope the work before you talk to anyone.
What Is A Propertybase Salesforce Integration?
A Propertybase Salesforce integration connects the real estate records in your Propertybase org (contacts, inquiries, listings, offers and closings) with the other systems your brokerage runs on. Because Propertybase Salesforce Edition is installed as a managed package in a Salesforce org, that connection uses Salesforce's APIs and automation plus Propertybase's own web services.
That point changes how you should think about the project. Propertybase is not a separate database sitting next to Salesforce. Its core records (contacts, inquiries, listings, offers and closings) are objects inside your Salesforce org. So the tools for moving data in and out are the ones Salesforce provides: the REST API, Bulk API 2.0, Change Data Capture, platform events and the integration platforms built on them. On top of those, Propertybase adds its own lead-capture and listing-publishing services.
The phrase covers three kinds of work in practice:
Inbound feeds
MLS listings, website and portal leads, and third-party data flowing into Propertybase records.
Outbound publishing
Listings syndicated to portals and websites, and deal data pushed to transaction, finance and marketing tools.
Two-way sync
Records kept consistent across systems that both edit them, such as a separate Sales Cloud org or an accounting ledger.
Monitoring and reporting
Alerts, logs and dashboards that show when a feed is late, failing or creating duplicates.
When Does A Brokerage Need Propertybase Integration Services?
You need integration services when data has to move between Propertybase and another system on a schedule or in real time, and someone is doing it by hand today. If Propertybase's built-in tools already cover your feeds and nobody re-keys data, configuration alone may be enough.
Integration services fit if staff export and re-upload MLS files, listing status differs between your CRM, website and portals, commission figures are rebuilt in spreadsheets before payroll, leads arrive in an inbox instead of a record, or a second system (a Sales Cloud org, an accounting package, a marketing platform) holds its own copy of your contacts.
You may not need custom integration if your website and portals are already served by Propertybase's own Front Desk and Portal Syndication, your transaction volume is low enough that a weekly import is fine, and no other system edits the same records. In that case, configuring what Propertybase already offers is faster and cheaper than building anything.
Which Real Estate Systems Should Connect To Propertybase?
Most brokerages connect six groups of systems to Propertybase: the MLS or IDX feed, the website and lead sources, listing portals, transaction and e-signature tools, accounting and commission, and marketing automation. Start with whichever one people currently re-key by hand most often, because that is where the errors and the lost hours are.
| System | What moves | Usual direction | Typical method |
|---|---|---|---|
| MLS / IDX feed | New listings, price changes, status updates, photos | Into Propertybase | RESO Web API or the board's feed, loaded by upsert on the MLS listing ID |
| Website and lead forms | Inquiries, contact details, search criteria | Into Propertybase | Front Desk webforms or the WebToProspect REST API |
| Listing portals | Listings out, portal leads back in | Both ways | Propertybase Portal Syndication and portal lead capture |
| Transaction and e-signature | Offers, documents, signed status, milestones | Both ways | Packaged connector or API integration (for example DocuSign, Dotloop) |
| Accounting and commission | Closed deals, commission splits, payouts | Out of Propertybase | Connector or middleware into Accounting Seed, QuickBooks or Xero |
| Marketing automation | Contacts, segments, engagement history | Both ways | Native connector for Marketing Cloud or Account Engagement, or middleware |
The MLS row deserves a note. RESO, the industry standards body, describes its Web API as a RESTful, OData-based standard that is replacing the deprecated RETS format. If your current MLS feed still runs on RETS, plan the move to the Web API as part of the integration rather than as a separate emergency later.
What Propertybase Does Natively, And Where Custom Integration Starts
Propertybase already includes tools for capturing leads, publishing listings to portals and syncing listings to a Propertybase website. Use them first. Add a packaged connector or middleware when a system isn't covered, and build custom integration only when neither option meets the requirement. That order keeps maintenance low and upgrades safe.
Front Desk
Lead captureBest for: getting website and form inquiries into Propertybase as records, not emails.
Propertybase documents four ways to capture website leads through Front Desk: Propertybase webforms, the WebToProspect REST API, JSON-to-email webforms and XML-to-email webforms. The webforms are the fastest to set up but can't modify incoming data. WebToProspect needs web development but lets you shape the data on its way in. Propertybase's webservices also cover lead capture from portals such as Zillow, Trulia and Realtor.com.
Portal Syndication
Listing publishingBest for: publishing listings to supported portals from the listing record.
Portal Syndication is configured in Control Center under Portal Mapping, with default field mappings you can adjust and an Auto Publish option that publishes listings matching your criteria. Propertybase lists Rightmove, Zoopla, LonRes, On the Market, Zillow and Idealista among the supported portals. You need your own account with each portal. A portal that isn't on the list is where custom work starts.
Custom and middleware integration
When native stopsBest for: MLS boards, accounting, transaction platforms, a second Salesforce org, or any system Propertybase doesn't cover.
Here the work moves to Salesforce's APIs, either through an integration platform such as MuleSoft, Celigo, Workato or Zapier, or through Apex and Flow inside the org. The choice depends on volume, latency and who will maintain it. A brokerage with one accounting sync rarely needs an enterprise integration platform. A multi-office brokerage with several MLS boards often does.
How Does Real Estate Data Synchronization Work With Propertybase?
Data moves between Propertybase and other systems through Salesforce's APIs. Small, frequent changes go through the REST API. Large loads such as an MLS backfill go through Bulk API 2.0. Change Data Capture or platform events push Propertybase changes out in near real time. Pick the method by volume and how fresh the data must be.
| Method | Use it for | What to know |
|---|---|---|
| REST API (upsert) | Single listings, leads, status changes | Upsert on an external ID creates a record when there is no match and updates it when there is one. If several records match, Salesforce rejects the call and changes nothing. |
| Bulk API 2.0 | MLS backfills, migrations, nightly reconciliation | Asynchronous and built for large data sets. Salesforce suggests it for jobs over about 2,000 records. |
| Change Data Capture | Telling other systems what changed in Propertybase | Publishes create, update, delete and undelete events so external stores stay in sync without repeated polling. |
| Platform events | Business events such as "offer accepted" or "deal closed" | Published from Flow, Apex or external apps, and consumed by Flow, Apex or the Pub/Sub API. |
| Salesforce Connect | Viewing large external data without copying it | Shows external tables as external objects on demand. It's an extra-cost feature, and external objects are read-only by default. |
| Integration platform | Several systems, transformations, retries | MuleSoft, Celigo, Workato or Zapier sit between systems and handle mapping, scheduling and error queues. |
Sources: Salesforce documentation for upsert, Bulk API 2.0, Change Data Capture and Salesforce Connect. Change Data Capture and platform events are available in Enterprise, Performance, Unlimited and Developer editions.
The single most important design decision is the external ID. Every listing needs a unique, permanent identifier from its source, usually the MLS listing number plus the board. If the integration matches on street address instead, a typo or a unit number creates a second listing, and agents end up working duplicates. The same rule applies to contacts coming from portals and to deals going to accounting.
Who Owns Each Field? The Rule That Keeps Synced Data Accurate
Every field that exists in more than one system needs a written rule: which system owns it, which way it syncs, how often, what happens when both sides change it, and who is alerted when the sync fails. Integrations without these rules work at go-live and drift within months.
| Field | Owner | Direction and frequency | Conflict rule |
|---|---|---|---|
| Listing price and status | MLS | MLS to Propertybase, near real time | MLS wins; manual edits are overwritten and logged |
| Listing marketing copy | Propertybase | Propertybase to website and portals | Propertybase wins |
| Contact details | Propertybase | Two-way with marketing, on change | Most recent verified change wins |
| Commission split | Propertybase deal record | Propertybase to accounting, at closing | Accounting changes go back as an approved correction, never a silent edit |
| Payment status | Accounting | Accounting to Propertybase, daily | Accounting wins |
An illustrative example. The right owner for each field depends on your MLS rules, your accounting process and how your agents work.
How Do You Keep A Propertybase Integration Secure?
A secure Propertybase integration authenticates as its own API-only integration user, uses the OAuth client credentials flow instead of a stored password, keeps endpoints and secrets in named credentials, and grants only the object and field access the integration needs through permission sets. Each integration gets its own user so every change is traceable.
A dedicated integration user per integration
Salesforce recommends one integration user per integration. The Salesforce Integration user licence provides an API-only profile with no access to the user interface. Salesforce includes five of these licences in each Enterprise, Unlimited and Performance Edition org. Confirm what your Propertybase org's underlying edition includes before you plan around them.
Client credentials flow and named credentials
For server-to-server connections, the OAuth client credentials flow runs as the assigned integration user without passing a username and password. Salesforce recommends avoiding the username-password flow, which some how-to guides still show. For calls out of Salesforce, named credentials hold the endpoint and its authentication in one place, so secrets never sit in code.
Least-privilege permission sets and API budgets
Grant the integration user only the Propertybase objects and fields it needs, through permission sets, which Salesforce calls the recommended way to manage permissions. Then size the integration against Salesforce API limits: production orgs allow 25 concurrent long-running requests, and the daily API allocation depends on your edition and the number of licences. A badly batched MLS feed can use up the allocation that your website forms also depend on.
Logs, alerts and a runbook
Log every failed record with the reason, alert a named person when a feed is late, and write down what to do when it fails. A sync nobody watches fails silently, and the first person to notice is usually an agent showing a sold home.
Where Propertybase Integrations Break (And How To Prevent It)
Most failed Propertybase integrations fail for the same few reasons: connectors that assume standard Salesforce objects Propertybase doesn't support, duplicate listings from weak matching, no field ownership, unmonitored feeds, and customizations that break after a package upgrade. Each one can be designed out before go-live.
How Twopir Consulting Delivers Propertybase Salesforce Integration Services
Twopir Consulting delivers Propertybase integrations in a fixed sequence: map every system and field, design the ownership rules and the sync method, build and test in a sandbox, rehearse with full data, go live with monitoring in place, and then govern the integration through Propertybase upgrades. The order matters more than any single tool.
Our Propertybase integration service covers this work across MLS and IDX sync, portal syndication and lead capture, transaction and document flow, finance and commission sync, marketing data, and monitoring. For engineering detail on APIs, event-driven sync and authentication, see our Propertybase API integration page. When records also have to move from an old system first, our Propertybase data migration approach uses the same external IDs, so migrated listings don't duplicate when the live MLS feed starts.
What Does A Well-Built Integration Change For A Brokerage?
A well-built integration replaces manual exports with automated feeds, so listing data stays current everywhere and agents respond to leads faster. In one of our published Propertybase projects, a brokerage replaced twice-daily MLS CSV uploads with an API sync and eliminated 90% of manual MLS exports.
Residential brokerage, 120+ agents
Propertybase Salesforce EditionBefore: an admin exported CSVs from the MLS portal twice a day and re-uploaded them by hand.
We deployed Propertybase Salesforce Edition and replaced the CSV routine with a REST API sync monitored by health-check Flows, so price changes, status updates and new listings arrive in Salesforce without manual exports. The published case study reports 90% of manual MLS exports eliminated, lead response cut from hours to under 15 minutes, and a 12-week, five-phase delivery.
Sotheby's International Realty (UAE)
Salesforce listing APIBefore: external platforms received project listings through manual data exports.
We built a secure Apex REST endpoint with Connected App authentication, query filtering, audit logging and rate limiting, so external systems pull filtered property data on demand. The case study reports API responses under five seconds and no manual exports. It shows the same pattern a Propertybase org uses to share listing data securely.
How To Choose A Propertybase Integration Partner
Choose a partner who can explain how Propertybase sits inside Salesforce, names the objects your org doesn't support, proposes field ownership rules before quoting a build, and ships monitoring with the integration. Ask the questions below on the first call. A partner who can't answer them will learn on your data.
- Which sync method would you use for our MLS feed, and why? Look for an answer based on volume and freshness, not a favourite tool.
- How will you stop duplicate listings? The answer should name an external ID from the source system.
- Which of our connectors depend on Lead, Opportunity or Campaign? A good partner checks this before quoting.
- What does the integration authenticate as? Expect a dedicated integration user, the client credentials flow and named credentials.
- How will we know when a sync fails? Expect alerts to a named person, per-record error logs and a runbook.
- What happens at the next Propertybase release? Expect sandbox regression testing, not "it should be fine".
We help growing and mid-market companies solve complex CRM, integration, and business system challenges, and real estate is one of the industries we serve most. Our Salesforce for real estate page shows the wider system landscape we work across.
Map Your Propertybase Integrations With A Salesforce Architect
On a 30-minute discovery call, a Twopir Salesforce architect will review the systems around your Propertybase org, find where data is re-keyed or drifting, and tell you honestly which integrations native tools can cover and which need a build.
Schedule a Discovery CallThe Bottom Line
Propertybase gives a brokerage a real estate CRM inside Salesforce. Integration is what turns it into the single source of truth for listings, leads and deals. The technology is well documented. What decides success is the design: native tools first, permanent IDs, a written owner for every shared field, secure API-only access, and monitoring that catches failures before agents do.
- 1
A Propertybase Salesforce integration runs on Salesforce's APIs plus Propertybase's Front Desk and Portal Syndication, because Propertybase lives inside the Salesforce org.
- 2
Connect the system people re-key most often first. For most brokerages that is the MLS feed.
- 3
Match REST, Bulk API 2.0, Change Data Capture or platform events to the volume and freshness each feed needs.
- 4
Give every shared field an owner, a direction, a frequency, a conflict rule and a failure alert.
- 5
Secure each integration with its own integration user, the client credentials flow, named credentials and least-privilege permission sets.
Frequently Asked Questions
Propertybase Salesforce Edition is built on Salesforce: it is installed as a managed package inside a Salesforce org. Its contacts, inquiries, listings, offers and closings are Salesforce records, so integrating Propertybase with other systems uses Salesforce's APIs and automation together with Propertybase's own lead-capture and portal-syndication tools.
Propertybase offers the WebToProspect REST API for capturing website leads, plus webservices for portals and website listings. For everything else, such as MLS feeds, accounting or a second org, you work with the standard Salesforce APIs, because Propertybase data lives in Salesforce objects.
It can sync close to real time when the MLS provides an API, such as one built on the RESO Web API standard. The integration upserts each change on the MLS listing ID. How current the data can be depends on how often the MLS board allows requests and on your Salesforce API allocation.
A common cause is a connector that writes to standard Salesforce objects Propertybase doesn't support, such as Lead, Opportunity or Campaign. The connector has to be remapped to Propertybase's contacts, inquiries and deals, or those objects licensed separately from Salesforce.
Store a permanent identifier from the source system, such as the MLS listing number, in an external ID field, and load every change by upsert on that field. Matching on street address creates duplicates whenever the address is typed differently.
It depends on how many systems you connect and how clean the data is. A single feed set up with native tools is the shortest project. In our published residential brokerage case study, a full Propertybase implementation including the MLS API sync was delivered in 12 weeks.
Twopir Consulting is a Salesforce Partner and HubSpot Partner that implements and integrates Propertybase Salesforce Edition. We don't resell Propertybase or Salesforce licences and hold no partner credential with Lone Wolf Technologies.
Twopir Consulting
We implement, rescue, optimize, and integrate complex CRM and revenue systems. Twopir Consulting works with growing, mid-market, and enterprise organizations, and our real estate practice covers Propertybase Salesforce Edition implementation, integration, data migration and automation.
