Migrate your Propertybase data
Salesforce-based real estate CRM built for brokerages and teams to manage leads, listings, and transactions end-to-end.
In its favor
Why people choose Propertybase
The signal that keeps Propertybase on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
All-in-one real estate platform covering CRM, websites, lead generation, and transaction management in a single Salesforce-based system that brokers and teams appreciate as comprehensive.
Native listing and media management lets real estate teams store property images, video links, and documents directly within Propertybase without relying on third-party document storage.
Integration with Lone Wolf ecosystem and BoldTrail suite provides access to additional real estate-specific tools and MLS data that standalone CRMs cannot match.
Tiered per-unit pricing starting at $60/month makes the platform accessible to small brokerages with fewer than 20 units before requiring an upgrade.
Workflow automation capabilities allow teams to build custom automation rules without writing code, reducing manual follow-up tasks for agents.
Customers report recurring billing issues where the company charges unexpectedly, with one reviewer stating the platform 'literally steals money' through billing disputes.
The onboarding experience is described as basic and unhelpful — teams report needing to build their own features to make the software usable, suggesting inadequate initial setup support.
A steep learning curve makes the platform difficult to adopt — reviews indicate 'you have to learn how to make it do it all' rather than it working out of the box.
Alternative platforms like BoomTown (4.7/5) and BoldTrail (4.5/5) score higher on G2, prompting teams to evaluate options with more modern UX and simpler configuration.
Enterprise pricing at $89/user/month is cost-prohibitive for larger teams compared to flat-rate alternatives in the real estate CRM market.
Reasons to switch
Why people leave Propertybase
The recurring reasons buyers give for replacing Propertybase. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Propertybase fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Propertybase pricing overview
Propertybase uses tiered per-unit pricing for Starter plans, scaling costs as brokerages manage more units. Enterprise tier is priced per user at $89/month (billed annually), making team size a significant cost driver at scale. The Professional tier pricing is not publicly documented, requiring a sales conversation for a quote.
Starter
Tier 1 of 4
$60/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Propertybase's schedule — see our quote-based pricing →
What gets migrated
Propertybase object support
Object-by-object support for Propertybase migrations. Per-pair details surface during scoping.
Companies
Fully supportedStandard business entities for builders, solicitors, agencies, and other organizations. We map Company records 1:1 and preserve all associated fields during migration.
Company Contacts
Fully supportedContacts where SystemIsIndividual=FALSE and linked to an actual Company record. These represent business contacts within organizations and migrate cleanly with their parent-company relationship intact.
Individual Contacts
Mapping requiredContacts where SystemIsIndividual=TRUE that are linked to a ghost Company record (a background placeholder required by Salesforce to satisfy the all-Contacts-must-link-to-a-Company rule). We identify and handle ghost company linkage during import so individual buyers and sellers land without creating orphan relationships in the destination.
Enquiries/Requests
Fully supportedProspect inquiries and requests linked to a Contact. Can be linked to a Listing via Favourite records. We preserve the Contact lookup and Favourite associations during migration.
Listings (Project or Individual)
Fully supportedIndividual property listings or Project listings (buildings/stages). Listings may be linked to a Master Project/Building/Stage. We preserve parent-child relationships and listing status. Media Loader assets (images, videos, documents) require separate handling via document migration.
Offers/Contracts
Fully supportedOffers and contracts linked to a Listing and Purchaser via Contact lookup fields. We preserve both lookups and map any offer status, price, and date fields to their destination equivalents.
Custom Objects
Mapping requiredPropertybase supports custom objects built on the Salesforce platform. Custom object schemas vary by org — we audit the target org's custom object metadata before migration and build field-level mappings for each one.
Workflow Rules
Mapping requiredAutomation rules that watch an object and trigger actions based on criteria. Workflow rules are metadata that must be rebuilt on the destination platform — they do not export via the standard data export tool.
Activities/Tasks
Fully supportedStandard Salesforce Activity and Task objects. We migrate completed activities and open tasks, preserving assignment, due dates, and status.
Attachments and Documents
Mapping requiredAttachments stored on record detail pages and Propertybase Media Loader assets require separate export paths. We extract attachments via the Salesforce API alongside record data and re-attach them in the destination system.
Tags/Labels
Mapping requiredPropertybase uses a tagging system for contacts and listings. Tags map to label or tag structures in the destination — we build a mapping table during the discovery phase for any custom tag taxonomy.
Report Types
Not in this platformPropertybase Report Types are configurations specific to the platform and cannot be exported. Reports and dashboards must be rebuilt manually on the destination CRM using the migrated data as a source.
| Object | Support | Notes |
|---|---|---|
| Companies | Fully supported | Standard business entities for builders, solicitors, agencies, and other organizations. We map Company records 1:1 and preserve all associated fields during migration. |
| Company Contacts | Fully supported | Contacts where SystemIsIndividual=FALSE and linked to an actual Company record. These represent business contacts within organizations and migrate cleanly with their parent-company relationship intact. |
| Individual Contacts | Mapping required | Contacts where SystemIsIndividual=TRUE that are linked to a ghost Company record (a background placeholder required by Salesforce to satisfy the all-Contacts-must-link-to-a-Company rule). We identify and handle ghost company linkage during import so individual buyers and sellers land without creating orphan relationships in the destination. |
| Enquiries/Requests | Fully supported | Prospect inquiries and requests linked to a Contact. Can be linked to a Listing via Favourite records. We preserve the Contact lookup and Favourite associations during migration. |
| Listings (Project or Individual) | Fully supported | Individual property listings or Project listings (buildings/stages). Listings may be linked to a Master Project/Building/Stage. We preserve parent-child relationships and listing status. Media Loader assets (images, videos, documents) require separate handling via document migration. |
| Offers/Contracts | Fully supported | Offers and contracts linked to a Listing and Purchaser via Contact lookup fields. We preserve both lookups and map any offer status, price, and date fields to their destination equivalents. |
| Custom Objects | Mapping required | Propertybase supports custom objects built on the Salesforce platform. Custom object schemas vary by org — we audit the target org's custom object metadata before migration and build field-level mappings for each one. |
| Workflow Rules | Mapping required | Automation rules that watch an object and trigger actions based on criteria. Workflow rules are metadata that must be rebuilt on the destination platform — they do not export via the standard data export tool. |
| Activities/Tasks | Fully supported | Standard Salesforce Activity and Task objects. We migrate completed activities and open tasks, preserving assignment, due dates, and status. |
| Attachments and Documents | Mapping required | Attachments stored on record detail pages and Propertybase Media Loader assets require separate export paths. We extract attachments via the Salesforce API alongside record data and re-attach them in the destination system. |
| Tags/Labels | Mapping required | Propertybase uses a tagging system for contacts and listings. Tags map to label or tag structures in the destination — we build a mapping table during the discovery phase for any custom tag taxonomy. |
| Report Types | Not in this platform | Propertybase Report Types are configurations specific to the platform and cannot be exported. Reports and dashboards must be rebuilt manually on the destination CRM using the migrated data as a source. |
Gotchas
What to watch for in Propertybase migrations
Issues we've hit on past Propertybase migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Formula and roll-up summary fields excluded from exports
Ghost company records for Individual Contacts
Workflow rules do not export — automations must be rebuilt
Media Loader assets require separate migration path
| Severity | Issue |
|---|---|
| High | Formula and roll-up summary fields excluded from exports |
| Medium | Ghost company records for Individual Contacts |
| Medium | Workflow rules do not export — automations must be rebuilt |
| Medium | Media Loader assets require separate migration path |
Leaving Propertybase?
Where Propertybase customers move next
12 destinations Propertybase can migrate to.
How a Propertybase migration works
Four steps, Propertybase-specific
Connect
OAuth 2.0 (Salesforce platform) into Propertybase. Scopes limited to read-only on the data we move.
Map
We translate Propertybase-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Propertybase quirks before production.
Migrate
Full migration with Propertybase rate-limit handling. Rollback available throughout.
FAQ
Propertybase migration FAQ
Answers to the questions buyers ask most during Propertybase migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Propertybase migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Propertybase.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Propertybase setup and destination — written quote back within a business day.