Propertybase Salesforce CRM Architecture: Data Model, Automation and Governance
How to design Propertybase on Salesforce so it still works at four offices and four hundred agents: the property lifecycle it has to carry, the real Propertybase data model, sharing for multi-office brokerages, an automation and integration strategy, and the governance that stops the org from fragmenting.
Key Takeaways
- Propertybase is a real estate data model installed on the Salesforce Platform. Its architecture is the set of decisions you make on top: how records connect, who sees what, what runs automatically, and how outside systems feed it.
- The core chain is Contact → Inquiry → Listing and Property → Offer → Closing. Build on it rather than beside it: no parallel lead, deal or transaction objects that duplicate the same sale.
- Multi-office brokerages need a deliberate access model: restrictive org-wide defaults, a role hierarchy built for data access, sharing rules for exceptions, and permission sets by job.
- Design the lifecycle before automating it. Then use Flow with one entry point per object, fault paths and sandbox testing. Process Builder is out of support.
- Most failures are architectural, not product failures. A short architecture review finds them before they cost an expansion or a replacement project.
Propertybase Salesforce CRM architecture decides whether a brokerage gets one system for its whole property lifecycle or another CRM that agents work around. Propertybase gives you the real estate records. Salesforce gives you sharing, automation, integration and reporting. The architecture is how you put them together for the way your business takes a listing to close.
This guide is for broker-owners, operations leaders, Salesforce admins and architects at growing and mid-market companies in real estate: residential brokerages, developers, franchises and investment firms, up to multi-office and enterprise organizations. It replaces the March 2026 version of this article. We corrected the data model to match Propertybase's own documentation, added the access, integration and governance detail an architect needs, and linked every product claim to its official source.
What Is Propertybase Salesforce CRM Architecture?
It is the design of a Propertybase org as a lifecycle system rather than a contact database. It covers five decisions: how the Propertybase records model each stage from first inquiry to closing, who can see and edit which records, which steps run automatically, how MLS feeds, portals and back-office tools connect, and how changes are governed. Get these right and the org scales with the brokerage.
| Architecture layer | The question it answers | Main tools | Warning sign |
|---|---|---|---|
| Data model | How does one sale move from inquiry to closing? | Contacts, Inquiries, Listings, Properties, Offers, Closings | The same deal lives in a CRM record, a spreadsheet and an inbox |
| Access | Who sees and edits which records? | Org-wide defaults, roles, sharing rules, permission sets | Everyone sees everything, or managers can't see their offices |
| Automation | What happens without anyone remembering? | Flow, Lead Router, Action Plans, validation rules | Several tools fire on the same record and nobody knows the order |
| Integration | How do outside systems read and write data? | Front Desk, APIs, Portal Mapping, e-signature apps | Listings and leads are re-keyed or arrive late |
| Governance | How does the org change safely? | Sandboxes, Lifecycle Center, documentation, release testing | Changes go straight into production |
What Is Propertybase on Salesforce Today?
Propertybase is a real estate CRM that runs natively inside Salesforce, sold by Lone Wolf Technologies. It installs real estate objects (inquiries, listings, properties, showings, offers and closings) in a Salesforce org, plus lead capture, routing and matching tools. Because it is native, it follows Salesforce's rules for sharing, automation, limits and upgrades, which is why architecture matters.
Lone Wolf acquired Propertybase in 2021 and now offers two products: Propertybase, the Salesforce-based CRM this guide covers, and Front Office (formerly Propertybase GO), a separate product. Lone Wolf's product page says the CRM's workflow automation is built on Salesforce Flow and that it is updated every three to six weeks. That release rhythm is an architecture input: anything you build must survive regular package upgrades.
Salesforce's own Help now notes that "Sales Cloud is now Agentforce Sales", so older Propertybase articles and newer Salesforce documentation can use different names for the same platform.

Why Do Propertybase Implementations Break at Scale?
Because the platform was installed but never designed around how the brokerage actually works. A single property sale involves marketing, qualification, agent assignment, listing work, showings, negotiation, legal documents, transaction coordination and after-sale contact. When those steps aren't modelled as one connected lifecycle, each office and team fills the gaps its own way, and the CRM fragments.
Our Propertybase practice sees the same thing in orgs we're asked to rescue: almost none of these are product failures. They come from architecture decisions that were never made.
What Are the Five Layers of the Property Lifecycle?
Demand generation, lead qualification, the listing lifecycle, transaction execution and the client lifecycle. We use these five layers to plan a Propertybase org because each maps to specific records and automation. Designing them in this order, before configuring anything, keeps every stage connected to the next and stops the after-sale relationship from being forgotten.
Standardize how demand enters
Portals, the brokerage website, developer campaigns, social ads, open houses and referrals all land the same way: as a contact and an inquiry, with the source recorded. In Propertybase this is Front Desk.
Get the right lead to the right agent
Buyer and seller qualification, assignment and nurture. Lead Router assigns by team and distributor; Flow adds response deadlines and escalation.
Model every listing stage
Preparation, marketing launch, active, showings, negotiation, under contract and closed, each a status on the listing with its own rules, matching and syndication.
Coordinate the deal to close
Offers, documents, compliance approvals, milestones and closing preparation, run on Offers and Closings with checklists and gates.
Keep the relationship after closing
Referrals, repeat buyers and sellers, investor relationships and portfolio growth. It is the layer most often skipped, and the closed deal record is where it should start.

How Should You Model Propertybase Data in Salesforce?
Use Propertybase's own record chain as the backbone and extend it, rather than adding parallel objects. The chain is Contact, Inquiry, Listing and Property, Offer and Closing, with showings, linked listings and activities around it. Generic CRM designs built on Leads, Opportunities and a custom transaction object duplicate what Propertybase already models, and split reporting.
| Generic CRM idea | Propertybase record | What it holds | Design note |
|---|---|---|---|
| Lead | Contact | Individuals or companies; a contact can be a lead, a customer or a partner, with a status path | Use record types and the contact path for stages, not a separate lead object |
| Opportunity (buyer demand) | Inquiry | What a buyer wants: type, bedrooms, baths, budget; API name pba__Request__c | Add custom criteria fields here to sharpen matching |
| Product / inventory | Listing and Property | Each listing creates and syncs a Property: physical facts on the property, sale or rent facts on the listing; buildings can hold units | Decide which fields sync and which are blocked before data migration |
| Activity | Showings, linked listings, activities | Showings with rating and feedback; linked listings with status and price; calls, tasks and meetings | These are your demand signals; keep them on records, not in notes |
| Opportunity (negotiation) | Offer | Listing, buyer and seller, counter-offers and addenda, with an offer path | The point where deal intent becomes a commitment |
| Custom "transaction" | Closing | Created from the offer, with commission overview, closing checklist and target and actual dates | Add commission, split and compliance fields here, not on a new object |
Three modelling rules that prevent most rework
- 1
Separate intent from execution. The inquiry and offer record what the buyer wants and agrees to; the closing records what actually happens. Keep deadlines, documents and commission on the closing.
- 2
Extend packaged objects with your own fields, not your own copies. Custom fields, record types and page layouts on Propertybase objects survive upgrades better than parallel objects that must be kept in sync.
- 3
Model the business lines that differ. Residential resale, new-development sales, rentals and commercial real estate often need different record types, each with its own picklist values, stages and layouts.
If a part of the business genuinely needs Salesforce Leads or Opportunities (a non-brokerage service line, for example), document exactly where those records hand over to the Propertybase chain, so one sale is never counted twice. For worked examples of extending the objects, see Propertybase Salesforce customization for real estate.
How Should a Multi-Office Brokerage Set Up Access and Sharing?
Start restrictive and open access deliberately. Set org-wide defaults to the tightest level each object needs, build a role hierarchy that reflects data access rather than the org chart, add sharing rules for the exceptions, and grant object and field permissions with permission sets by job. This keeps client data private between agents while letting managers see their offices.
Salesforce separates two questions. Profiles, permission sets and permission set groups decide what kinds of records and fields a user can touch. Org-wide sharing settings, roles and sharing rules decide which individual records they can see, as Salesforce's "Control Who Sees What" guide explains. Salesforce's tip there is a good first step: write a table of user types and the access each one needs, then build from it.
| User type | Typical record access | How to grant it |
|---|---|---|
| Agent | Own contacts, inquiries, offers and closings; active listings across the brokerage | Private defaults on client records; a sharing rule opening listings to all agents |
| Team lead or office manager | Everything owned by agents in their team or office | Role hierarchy: users see data owned by roles below them |
| Transaction coordinator | Offers and closings across an office, plus documents | A criteria-based sharing rule to a public group |
| Finance | Closings and commission fields across the brokerage, read-only elsewhere | A permission set with field-level access to commission fields |
| Franchise or partner office | Only its own region's records | Separate roles per office, and restriction rules where sharing alone is too wide |
Points architects miss: sharing rules and the role hierarchy can only widen access, never make it stricter than the org-wide default. Salesforce allows up to 300 sharing rules per object, including up to 50 criteria-based rules, so a rule per agent does not scale; use groups and roles. On custom objects, "Grant Access Using Hierarchies" can be switched off, which changes what managers see. And role changes trigger a sharing recalculation, so plan big restructures (a new office, a merger) for quiet hours. Salesforce calls permission sets the recommended way to manage permissions; keep profiles minimal.
What Is the Right Automation Strategy for Propertybase?
Automate the agreed lifecycle, on Flow, with one entry point per object. Use the tools Propertybase ships first (Lead Router, matching, Action Plans, drip campaigns), then Salesforce Flow for the rest, with Apex only where volume or complexity needs it. Every flow gets fault handling, sandbox testing and an owner. Process Builder and Workflow Rules are no longer supported.
One entry point per object
Salesforce's record-triggered automation guide advises against mixing Flow and Apex triggers on one object, and picks the tool by automation density. Flow Trigger Explorer shows what runs, in what order.
Deadlines on scheduled paths
Response deadlines, contingency dates and closing reminders belong on scheduled paths, which Salesforce reschedules automatically when the record's dates change.
Gates, not reminders
Path guides each stage, and validation rules stop a closing advancing without its required compliance steps, even when data comes in through the API.
Fault paths everywhere
By default a failed flow only emails the admin who last edited it. Add fault paths and follow Salesforce's Flow best practices: no hard-coded IDs, no database actions inside loops.
Retire Process Builder
Salesforce ended support for Workflow Rules and Process Builder on 31 December 2025. Propertybase's own drip-campaign instructions use Process Builder, so rebuild those triggers in Flow.
Package tools first
Use Lead Router for assignment and Action Plans for task templates before building custom equivalents. Note that Lead Router sends returning contacts to their previous owner, and that rule is not configurable.
For step-by-step builds of each layer, see advanced Salesforce workflows for Propertybase and our Propertybase automation services.
How Should Propertybase Integrate With MLS, Portals and Back-Office Systems?
Pick an integration pattern per system, give every feed an owner and a health check, and make every load idempotent. MLS and listing feeds are batch synchronization, website and portal leads are calls into Salesforce, and e-signature or accounting handoffs are calls out. Matching on external IDs prevents the duplicate records that make brokerage reporting untrustworthy.
Salesforce documents six integration patterns and stresses idempotent design, so that a repeated message never creates a duplicate record. Here is how they map to a typical brokerage:
| System | Salesforce pattern | Propertybase or platform tool | Design rule |
|---|---|---|---|
| Website and lead forms | Remote Call-In | Front Desk webforms, WebToProspect REST API, JSON- or XML-to-Email | Every source sets a lead source value; prefer structured formats over plain notification emails |
| MLS / IDX feed | Batch Data Synchronization | Your MLS integration provider, upserting on an external ID | Schedule a health check that alerts someone when the feed stops |
| Portals and the website | Outbound sync | Portal Mapping and Website Listings Sync | One listing record is the source; required fields enforced before publishing |
| E-signature | Remote Process Invocation | Your e-signature app's Salesforce package | Signed documents and status write back to the offer or closing |
| Accounting and commissions | Fire and Forget or batch | Middleware or Platform Events | Send only closed, approved closings; finance owns the payout record |
Volume matters for the build. Salesforce's REST API can upsert up to 200 records per request matched on an external ID, and recommends Bulk API 2.0 for operations over 2,000 records, such as a full listing reload. Change Data Capture and Platform Events need Enterprise, Performance, Unlimited or Developer Edition, so check your edition before designing around them.
If you use Docusign, note that the legacy Docusign eSignature for Salesforce app could last be used on 16 October 2026; any closing automation still built on it needs the current app. Tools sit beneath the architecture, not in place of it. For the systems brokerages connect most, see our Propertybase Salesforce integration guide and Propertybase integration services.
How Do You Keep Propertybase Fast as Data Grows?
Plan data volume, sharing and loads as the brokerage grows, not after it slows down. Listings, showings, activities and portal leads accumulate quickly. Archive what nobody works anymore, load big data sets with the bulk API outside working hours, sync only what changed, and test large changes in a sandbox with realistic data first.
Salesforce's large data volumes guide describes a large deployment as tens of thousands of users, tens of millions of records or hundreds of gigabytes of storage, and notes that design choices can change operation times "by several orders of magnitude". Most brokerages are far below that, but a national franchise or a brokerage syndicating every listing it has ever had can get close. The practical rules:
- Defer sharing and automation on big loads. The guide recommends deferring or bypassing business-rule and sharing processing during large data loads; Salesforce also lets you defer sharing calculations before large role or group changes.
- Archive closed history. Expired listings and years-old activity can move to an archive or to Salesforce Big Objects, which the guide points to for very large historical data.
- Make listing loads selective. Upsert only changed listings on each sync, keyed on the MLS identifier, instead of reloading the whole inventory.
What Governance Keeps a Propertybase Org From Fragmenting?
Four kinds: data, access, process and change governance, each with a named owner. Data governance keeps listings and clients clean, access governance keeps offices separate, process governance keeps stages and approvals consistent, and change governance makes sure nothing reaches production untested. Without them, a multi-office org slowly splits into local versions of itself.
| Area | What to standardize | Tools |
|---|---|---|
| Data | Listing fields, client records, deal information, lead sources and picklists | Duplicate and matching rules, validation rules, required fields |
| Access | Offices, franchise locations, independent agents, joiners and leavers | Roles, permission sets, Security Health Check |
| Process | Listing activation, transaction approval, compliance checkpoints | Path, validation gates, approval flows, Action Plan templates |
| Change | Who may change automation, fields and layouts; how changes are tested and released | Sandboxes, Lifecycle Center, a regression script |
Salesforce renamed DevOps Center to Lifecycle Center from October 2026. It keeps configuration and code changes in source control as a single source of truth and is an alternative to change sets, available in Professional, Enterprise, Performance, Unlimited and Developer editions. Pair it with a short regression script (routing, matching, offer to closing, commission) that you run after every Propertybase release, since the package updates every few weeks.
How Do You Measure Whether the Architecture Is Working?
Pick metrics the data model can calculate on its own, and baseline them before you change anything. If lead response, conversion by source, offer-to-close time and commission accuracy all come straight from Propertybase records, the architecture is doing its job. If someone has to assemble them in a spreadsheet, a link in the chain is missing.
| Outcome | Metric | Comes from |
|---|---|---|
| Revenue growth | Closings and value by lead source | Contact lead source linked through to the closing |
| Sales productivity | Time to first contact; inquiries per agent | Contact or inquiry creation time against the first activity |
| Pipeline visibility | Offers and closings by stage and age | Offer and closing paths, target and actual closing dates |
| Listing performance | Showings, ratings and offers per listing | Showings, linked listings and offers on each listing |
| Operational efficiency | Overdue checklist items; manual record edits by coordinators | Closing checklist, Action Plan tasks |
| Client lifetime value | Repeat and referral closings per client | Contacts with more than one closing, referral source |
Each dashboard component maps to one report, so design reports per question first. Our guide to Propertybase reports in Salesforce shows how to build them.
What Does a Well-Architected Propertybase Rollout Look Like?
Discovery and an architecture blueprint first, then phased delivery, each phase tested in a sandbox. A multi-office residential brokerage with more than 120 agents had been through two failed CRM implementations. Twopir Consulting mapped the real workflow before configuring anything, then rebuilt it on Propertybase in five phases over 12 weeks.
According to the published case study:
The case study reports lead response falling from 4–6 hours to under 15 minutes, compliance audit preparation from two days to under two hours, new-agent onboarding from 14 days to 3, and a 35% lift in lead-to-appointment conversion within 90 days of go-live. These are one brokerage's results against its own starting point.
How Do You Audit an Existing Propertybase Architecture?
Answer ten questions, one per architecture decision, and fix the "no" answers in order. Most orgs we review fail two or three of them, usually parallel objects, an undesigned sharing model or automation on retired tools. Each "no" is cheaper to fix now than when the brokerage adds its next office, team or transaction type.
| # | Question | Section |
|---|---|---|
| 1 | Can you follow one sale from lead source to commission on records alone? | Data model |
| 2 | Is there exactly one record type for each kind of deal, and no parallel deal objects? | Data model |
| 3 | Are org-wide defaults private where client data is sensitive, with access opened by roles and rules? | Access |
| 4 | Are permissions granted with permission sets by job rather than one profile per person? | Access |
| 5 | Does each object have one automation entry point, all on Flow or Apex, none on Process Builder? | Automation |
| 6 | Does every flow have fault handling and a named owner? | Automation |
| 7 | Does every inbound feed upsert on an external ID and alert someone when it fails? | Integration |
| 8 | Are duplicate rules on, and are lead sources and stages controlled picklists? | Governance |
| 9 | Do all changes go through a sandbox and a release process before production? | Governance |
| 10 | Do leadership dashboards run on live reports, with nobody rebuilding them in a spreadsheet? | Impact |
For the operational side (lead routing, matching, offers, commissions and a 90-day plan), see how to best use Propertybase and Salesforce.
Should You Design Propertybase Architecture In-House or With a Partner?
In-house works for a single-office brokerage with an experienced Salesforce admin and mostly configuration work. A partner pays off for multi-office sharing, MLS and back-office integrations, a migration from another CRM, or a rescue after a stalled implementation. Whichever you choose, settle which requirements are configuration and which need code before any build starts.
Do it in-house if you run one office or a few similar teams, your admin knows Propertybase and Flow, sharing can stay simple, and integrations are the packaged ones.
Bring in a partner if you run several offices or franchises, need MLS, portal, e-signature or accounting integrations, are migrating data from another CRM, or a previous implementation stalled.
On timing, our case-study page puts a full implementation for a brokerage of 50 to 200 agents at typically 8 to 14 weeks, delivered in phases. Larger organizations, several business lines or heavy data migration take longer, so scope after discovery.
Twopir Consulting is a Propertybase consulting partner that implements Propertybase rather than reselling it, and has worked with 500+ clients since 2014. We implement, rescue, optimize, and integrate complex CRM and revenue systems. See Propertybase implementation for new orgs and Propertybase customization for extending an existing one.
The Bottom Line
The platform is rarely the problem. Propertybase and Salesforce become a revenue system when the lifecycle is designed first and the org is built around it: one record chain, a deliberate access model, automation on supported tools, owned integrations and a change process. Without that, CRM systems fragment, automation breaks and agents go back to their inboxes.
- 1
Map the five lifecycle layers before configuring anything.
- 2
Run every sale on Contact, Inquiry, Listing, Offer and Closing, and extend those records.
- 3
Design access from a table of user types: restrictive defaults, roles, rules, permission sets.
- 4
Automate on Flow with one entry point per object, fault paths and sandbox testing.
- 5
Give every integration and every change an owner, a health check and a release process.
Get a Second Opinion on Your Propertybase Architecture
On a 30-minute discovery call, a Twopir Salesforce architect will walk through your data model, sharing and automation with you, point out the decisions that will limit your next stage of growth, and tell you which to fix first.
Schedule a Discovery CallFrequently Asked Questions
It is how a Propertybase org is designed on the Salesforce Platform: the data model from contact and inquiry to offer and closing, the access and sharing model, the automation strategy, the integrations with MLS feeds, portals and back-office tools, and the governance for changes. Together they decide whether the CRM scales with the brokerage.
Propertybase's documented lead-to-close process runs on its own records: a contact, which can itself be a lead, raises an inquiry, inquiries match listings, and an accepted offer becomes a closing. Build on that chain. If part of the business also uses Leads or Opportunities, define exactly where they hand over so no sale is counted twice.
Set restrictive org-wide defaults on client records, build a role hierarchy so managers see their own offices, add sharing rules for coordinators, finance and shared listings, and grant object and field access with permission sets by job. Sharing rules can only widen access, so start from the most restrictive setting each object needs.
Use Flow by default, and Flow with invocable Apex or Apex triggers only when volume and complexity call for it, as Salesforce's architects advise. Whatever you choose, keep one automation entry point per object, add fault paths, and test every change in a sandbox. Use Propertybase's own Lead Router and Action Plans before building custom versions.
For a brokerage of 50 to 200 agents, Twopir's published case-study page puts a full implementation at typically 8 to 14 weeks, delivered in phases with core functions first; the brokerage in that case study went live in five phases over 12 weeks. More offices, business lines, integrations or data migration extend the timeline.
Yes, because it runs on the Salesforce Platform, which supports multi-office sharing, large data volumes and enterprise integration. Scale depends on architecture, though: a designed sharing model, selective listing loads, archiving, one automation entry point per object and governed releases. Lone Wolf describes Propertybase as scaling from 10 agents to more than 200.
It keeps running, but Salesforce ended support for Process Builder and Workflow Rules on 31 December 2025, so it gets no fixes. Inventory every process on Propertybase objects, including drip-campaign triggers built from Propertybase's older instructions, rebuild them in Flow in a sandbox, and switch them over one object at a time.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Propertybase architecture, implementation and integration for real estate firms.