Real Estate · Propertybase · Salesforce

Propertybase Salesforce Customization for Real Estate: What to Configure, Extend and Build

Propertybase is a managed package, so you can't edit it, but you can build almost anything on top of it. This guide covers what is locked, what you can change, which layer fits each need, how MLS and portal data should flow in, and how to keep every customization working through Propertybase's frequent upgrades.

New builds Custom objects · commissions · leasing Extensions Apex · Lightning Web Components · APIs Configuration Fields · layouts · Flow · sharing Propertybase managed package Locked code · upgraded by Lone Wolf

Key Takeaways

  • Propertybase is a managed package on Salesforce. Its code and API names are locked, but you can add fields, layouts, record types, flows, sharing, code and whole new objects around it.
  • Choose the lightest layer that does the job: configuration first, then extensions in Apex or Lightning Web Components, then new custom objects for things the package doesn't model, such as commission plans.
  • The customizations that pay off first are lead escalation, listing data-quality gates, record types per business line, richer inquiry matching, agent workspaces and commission logic on the closing.
  • Bring MLS, portal and website data in through Salesforce's APIs: upsert on an external ID, authenticate with named credentials, and use the RESO Web API rather than RETS.
  • Lone Wolf says the package updates every three to six weeks, so build in a sandbox, keep changes in source control, and retest against each release.

Propertybase customization is how a brokerage turns a packaged real estate CRM into one that matches the way it actually lists, sells, rents and pays agents. Propertybase runs natively inside Salesforce, so almost every customization tool Salesforce offers applies to it. One rule governs everything: you build around the package, never inside it.

This guide is for broker-owners, operations leaders and Salesforce admins at growing and mid-market companies in real estate, from single-office teams to multi-office and enterprise brokerages. It replaces our 2025 version of this article. Product facts now link to Propertybase's and Salesforce's own documentation, statistics we couldn't source are gone, and the example comes from a published Twopir case study.

Section 01 · Short Answer

What Is Propertybase Customization?

It is any change you make to a Propertybase org beyond the package defaults: new fields, page layouts, record types, automation, code, integrations or objects. Propertybase ships as a Salesforce managed package from Lone Wolf, so its own code stays locked. Customization works in three layers on top of it, and each layer carries more power and more maintenance.

LayerWhat it coversTypical toolsWho maintains it
ConfigurationChanging how packaged objects look and behave, without codeCustom fields, validation rules, record types, page layouts, Dynamic Forms, Flow, sharing, Propertybase settingsA Salesforce admin
ExtensionsCode that runs on packaged objects or reads them from outsideApex triggers and classes, Lightning Web Components, Salesforce APIs, Platform EventsA Salesforce developer
New buildsData and processes the package doesn't model at allCustom objects, relationships and roll-ups, plus Flow or Apex on themAn admin and developer together, with a data model owner

Propertybase's own building blocks are the Salesforce Contact and Company records plus custom objects for Requests (inquiries), Listings, Properties, Offers and Closings. Every customization in this guide hangs off those records. For how they connect, see our guide to Propertybase Salesforce CRM architecture.

Section 02 · Package Rules

What Can You Change in Propertybase, and What Is Locked?

You can add almost anything and adjust how packaged records look, but you can't edit the package's code or rename what it ships. Salesforce defines who may edit each part of an installed managed package. Some properties only the vendor can change, some both sides can change, and some, such as API names, nobody can change after release.

Salesforce's packaging guide sets out three categories of editable properties. Vendor-only properties, such as Apex code, are locked in your org and replaced at each upgrade. Shared properties, such as a packaged object's page layout or a field's help text, can be changed by you, and upgrades don't overwrite your changes. API names are locked for everyone. The component reference lists the rules for each component type.

You want to…Can you?How to do it safely
Add fields to Listings, Inquiries, Offers or ClosingsYesCreate your own custom fields on the packaged objects. Propertybase itself suggests closing fields for commissions and desk fee deductions.
Rearrange record pages for each roleYesEdit page layouts and Lightning record pages, or build your own. Your changes survive package upgrades.
Add validation rules, record types and flowsYesThey are your own metadata on the packaged objects, so the package doesn't touch them.
Tune Propertybase featuresYesUse the Control Center and Propertybase's custom settings before writing anything new.
Write Apex on packaged objectsYes, carefullyYour triggers run alongside the package's own logic. Keep one entry point per object and test after every upgrade.
Edit the package's Apex, flows or componentsNoPackaged code is locked and may be hidden. Wrap or extend it with your own automation instead.
Rename a packaged field's API nameNoChange the label instead. The API name, such as pba__Request__c for inquiries, stays fixed.

Why it matters: every customization you add is yours to maintain through each Propertybase release. Lone Wolf says on its product page that the package is updated every three to six weeks.

Section 03 · Decision Framework

Should You Configure, Extend or Build New in Propertybase?

Use the lightest layer that fully solves the problem. Configuration is cheapest to run and safest through upgrades, so try it first. Move to code only when configuration can't express the logic or can't handle the volume. Build new objects only when the package has no record for the thing you need to track.

Configure

Start here

Custom fields, validation rules, record types with their own picklists and layouts, Dynamic Forms on objects that support them, duplicate rules, sharing settings and record-triggered flows. Lone Wolf says Propertybase's own workflow automation is built on Salesforce Flow, so your flows sit naturally beside it.

Best for: routing rules, required data at each stage, role-based pages, alerts, deadlines and access control.

Extend with code

When clicks run out

Apex triggers and classes for logic Flow can't express cleanly or at volume, Lightning Web Components for agent workspaces and custom screens, and Salesforce's APIs for integrations. Salesforce's record-triggered automation guide suggests Flow for low automation density, Flow plus invocable Apex for medium, and Apex triggers for high.

Best for: matching and scoring beyond the standard algorithm, high-volume data processing, complex calculations and custom user interfaces.

Build new objects

Only when missing

Custom objects, relationships and roll-ups for processes the package doesn't model: commission plans with splits, tiers and caps, referral and co-broke agreements, leasing and rent roll, or investment analysis. Link them to the packaged records rather than duplicating them.

Best for: data that has its own life cycle and its own reports, which a few fields on an existing object can't hold.

A quick test before any build: if a field or a flow will do, don't write code, and if a field on the closing will do, don't build a new object. Each step up adds testing work at every Propertybase release.

Section 04 · Sales Cycle

Where Does Customization Fit in the Real Estate Sales Cycle?

At every stage, because each stage has its own Propertybase record. The sales cycle runs from lead generation to post-closing follow-up, and Propertybase stores each step as a contact, inquiry, showing, offer or closing. Map your customizations to these stages, so each change fixes a named step rather than adding fields nobody uses.

Real estate sales cycle in ten stages: lead generation, lead capture, lead qualification, contact creation, property search, showing scheduled, offer submission, transaction management, closing and client follow-up
The ten stages of the real estate sales cycle. The table below maps each stage to the Propertybase record that holds it and a typical customization.
StagePropertybase recordTypical customization
1–2 · Lead generation and captureContact and inquiry, via Front DeskSource and campaign fields, extra webform fields, duplicate rules
3–4 · Qualification and contact creationContact path, Lead RouterQualification fields required by stage, an escalation flow for untouched leads
5 · Property searchInquiry (pba__Request__c) and matchingCustom matching criteria, such as school zone or view
6 · ShowingsShowing activity, linked listingFeedback fields, follow-up tasks after each showing
7 · Offer submissionOfferOffer path with required fields, manager approval above a threshold
8–9 · Transaction management and closingClosing and its checklistCompliance gates, deadline reminders on scheduled paths, commission fields
10 · Client follow-upContactAnniversary and review reminders, referral tracking, re-engagement of old leads
Section 05 · Priorities

Which Propertybase Customizations Pay Off First for a Brokerage?

The ones that fix lost leads, bad listing data and spreadsheet work. Six customizations come up in most brokerages: escalating leads nobody contacts, gating listings on complete data, separating business lines with record types, sharpening inquiry matching, giving agents one workspace, and calculating commission on the closing. Start with whichever costs your brokerage most today.

Lead escalation

Lead Router assigns the lead. Add a record-triggered flow with a scheduled path that reassigns it or alerts a manager if nobody has logged contact within your agreed time.

Listing quality gates

Validation rules stop a listing moving to Active without a price, a full address or the required disclosures. They apply even when data arrives through the API, so a feed can't bypass them.

Record types per business line

Residential sales, rentals, commercial and new developments each get their own record type, picklist values, stages and page layout, so agents see only the fields that apply.

Richer inquiry matching

Add the criteria your buyers actually ask for to the inquiry and listing, then extend matching to use them. Propertybase documents how custom inquiry fields feed its matching.

Agent and coordinator workspaces

Lightning record pages, Dynamic Forms and, where needed, Lightning Web Components put today's leads, showings, offers and overdue tasks on one screen per role.

Commission on the closing

Split, cap and desk-fee fields on the closing, with a flow or Apex that calculates the payout when the closing reaches its final stage. Complex plans with tiers move to their own custom object.

Our posts on Propertybase workflows from lead to close and Salesforce features Propertybase can use go deeper into the automation behind several of these.

Section 06 · Integrations

How Should MLS, Portal and Website Data Reach Propertybase?

Through Salesforce's own APIs, because Propertybase records are Salesforce records. Pick the API by volume and timing: Bulk API for large feeds, REST upserts for steady updates, and events for near-real-time alerts. Match every record on an external ID, keep credentials in named credentials, and read MLS data through the RESO Web API.

JobSalesforce toolWhy
Initial load or nightly MLS feedBulk API 2.0Salesforce recommends it for operations over 2,000 records. It runs asynchronously, so big feeds don't block users.
Frequent listing updatessObject Collections upsertUp to 200 records of one type per request, matched on an external ID, so a resent record updates instead of duplicating.
Related records in one goCompositeChains requests, such as a contact then its inquiry, and counts as one call toward API limits.
Alert agents when a listing changesPlatform Events or Change Data CaptureFlows, Apex and external subscribers react to the change without polling.
Web and portal leadsFront Desk webforms or the WebToProspect REST APIPropertybase's own capture route, so leads arrive as contacts and inquiries ready for Lead Router.
Portal syndication outPortal Mapping in the Control CenterConfigure the packaged feed before building a custom one.

Three rules keep integrations sound. First, read MLS data through the RESO Web API, which RESO describes as replacing the deprecated RETS standard, and map fields using the RESO Data Dictionary. Second, store each endpoint and its login in a named credential, not in code or a settings record. Third, keep field mappings, thresholds and territory rules in custom metadata types, which deploy between sandbox and production with the rest of your changes.

Our Propertybase API integrations page covers the failure modes that only appear at volume, such as replays and retry storms.

Section 07 · Limits and Security

What Limits and Security Rules Shape a Propertybase Build?

Salesforce's per-transaction governor limits and its sharing and encryption model. Every trigger, flow and integration runs inside limits on queries, saves and processing time, so code must handle records in bulk. Who sees which listing or contact is set by roles, sharing defaults and sharing rules, and sensitive fields may need encryption on top.

Per-transaction limitSynchronousAsynchronous
SOQL queries issued100200
Records retrieved by SOQL50,00050,000
DML statements issued150150
Records processed by DML10,00010,000
Callouts100100
CPU time10,000 ms60,000 ms

Source: Salesforce's Execution Governors and Limits. Two points matter for a packaged org. Going over a limit throws an exception that can't be caught, so a trigger that queries inside a loop will fail on the first large import. And certified managed packages get their own set of most limits, while non-certified packages share the org's limits with your code. CPU time is always shared, so heavy custom logic can slow the package's own processing too.

Access · Sharing model

Decide who sees which records

Propertybase sets visibility per object by role, with organization-wide defaults of Public Read/Write, Public Read Only or Private. Sharing rules then open access by group, role or field criteria, but they can only open access, never restrict it. Multi-office brokerages usually set listings or contacts to Private and share by office.

Permissions

Grant access with permission sets

Salesforce recommends permission sets and permission set groups rather than a profile per job, so new roles such as transaction coordinators don't multiply profiles.

Encryption

Encrypt only what needs it

Shield Platform Encryption encrypts data at rest, such as ID or bank details held for a closing. It needs a Salesforce Shield or Shield Platform Encryption licence, and Salesforce notes that encryption is not the same as field-level or object-level security. On its own it doesn't make an org compliant with any regulation, so pair it with sharing, permissions and your own legal review.

Section 08 · Delivery

How Do You Customize Propertybase Without Breaking Upgrades?

Build in a sandbox, keep every change in source control, and retest your customizations against each Propertybase release before it reaches agents. The package changes often and your own code runs beside it, so treat customization as an ongoing release process, not a one-off project. These seven steps cover the work from idea to production.

1 · Check the package first.
→ Look for a Propertybase setting, Control Center option or packaged feature that already does the job before building anything.
2 · Write the requirement against a stage.
→ Name the sales-cycle stage, the record, the user and the measure it should improve, such as time to first contact.
3 · Build in a sandbox.
→ Sandboxes keep development away from production and let you test against a copy of real data and users.
4 · Keep one automation entry point per object.
→ Don't mix Flow and Apex triggers as entry points on the same object, and order flows with Flow Trigger Explorer.
5 · Handle failures.
→ Add fault paths to flows and error handling to integrations, so a failed sync or save is logged and reported, not lost.
6 · Release through source control.
→ Track changes and deploy them together with Salesforce's Lifecycle Center (formerly DevOps Center) or your own pipeline, then train agents on what changed.
7 · Retest after each package upgrade.
→ Keep a short regression list (lead capture, routing, matching, offer to closing, commission, integrations) and run it in a sandbox whenever Propertybase releases a new version.

One cleanup belongs in every plan: Salesforce ended support for Workflow Rules and Process Builder on 31 December 2025. Some older Propertybase instructions, such as its drip campaign automation, use Process Builder, so rebuild those in Flow.

Section 09 · Pitfalls

What Are the Most Common Propertybase Customization Mistakes?

Most problems come from building beside the package instead of on it, and from customizations nobody owns. The result is duplicate records, automation that fires twice, integrations that silently fail, and an org that is afraid of the next upgrade. Each item below is cheap to avoid at design time and expensive to fix later.

1. Parallel objects. A custom "Property" or "Deal" object built next to the packaged ones, so the same deal lives in two places.
2. Inserts instead of upserts. Feeds that create records rather than matching on an external ID, so every resend makes duplicates.
3. Credentials in code or settings. MLS and portal logins hard-coded or stored in plain settings rather than named credentials.
4. Stacked automation. A flow, a Process Builder and an Apex trigger all updating the same listing, in an order nobody controls.
5. Code that isn't bulk-safe. Queries or saves inside loops that pass a one-record test and fail on the first 500-row import.
6. Field sprawl. Dozens of fields added on request, half unused, which slows pages and confuses agents.
7. No regression test. Customizations that are never retested, so a package release breaks something before anyone notices.
Section 10 · Example

What Does a Well-Scoped Propertybase Customization Look Like?

One that targets a measured bottleneck and builds on the packaged records. A multi-office residential brokerage with more than 120 agents had leads triaged by hand and MLS data exported and re-uploaded. Twopir Consulting added Flow routing by geography, property type and agent capacity, then automated the MLS data handling and the transaction steps.

According to the published case study:

  • Lead response time went from 4–6 hours to under 15 minutes.
  • About 90% of the manual MLS export work was eliminated.
  • New-agent onboarding dropped from 14 days to 3.

These are one brokerage's results against its own starting point. Yours depend on your current gaps, which is why each customization should start from a baseline for the stage it targets.

Section 11 · Decision

Should You Customize Propertybase In-House or With a Partner?

In-house works for configuration when you have a Salesforce admin with time. A partner pays off once the work needs Apex, Lightning Web Components, integrations, commission models or a cleanup of tangled automation. Many brokerages combine both: a partner designs and builds the harder layers, and the in-house admin runs the configuration afterwards.

Do it in-house if the changes are fields, layouts, record types, validation rules and simple flows, your automation is already on Flow, and you have a sandbox and a habit of testing in it.

Bring in a partner if you need code on packaged objects, MLS or portal integrations, commission or compliance models, or if past customizations make every upgrade risky.

Twopir Consulting offers Propertybase customization services across all three layers, plus Propertybase automation in Flow. We have worked with 500+ clients since 2014. We implement, rescue, optimize, and integrate complex CRM and revenue systems.

Ready to Start

Plan Your Next Propertybase Customization

On a 30-minute discovery call, a Twopir Salesforce architect will review what you want Propertybase to do, tell you which layer each change belongs in, and flag any existing customization that puts your next upgrade at risk.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Yes. Propertybase is a managed package on Salesforce, so you can't edit its code, but you can add custom fields, validation rules, record types, page layouts, flows, sharing rules, Apex, Lightning Web Components, integrations and new custom objects around its contacts, inquiries, listings, offers and closings.

Upgrades don't overwrite your own fields, flows or code, or changes you make to shared properties such as page layouts. They do replace the package's own code, which can change how your customizations behave. Retest a short regression list in a sandbox after each Propertybase release.

Start with Flow, which Propertybase's own automation is built on. Use Apex when the logic is complex, the data volume is high or Flow can't express it cleanly. Salesforce's guidance is Flow for low automation density, Flow plus invocable Apex for medium, and Apex triggers for high, with one entry point per object.

Read listings from the MLS through the RESO Web API, then write them into Salesforce with Bulk API 2.0 for large feeds or REST upserts for frequent updates, matching every record on an external ID. Store the MLS login in a named credential and keep field mappings in custom metadata.

Closings carry a commission overview, and Propertybase says custom fields can be added to closings to calculate commissions and desk fee deductions. Simple splits fit in fields and a flow on the closing. Plans with tiers, caps or co-broke agreements usually need their own custom object linked to the closing.

Yes. Your triggers, flows and integrations run within Salesforce's per-transaction limits, such as 100 synchronous SOQL queries and 150 DML statements. Certified managed packages get their own set of most limits, but CPU time is shared, so build every customization to process records in bulk.

It depends on the layer. Configuration changes such as fields, layouts and simple flows can ship in days. Code, integrations and new objects such as commission models take longer because they need design, testing and an upgrade regression plan. Scope the work after a short review of your current org.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

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 customization, automation and integrations for real estate brokerages.