CRM migration
Field-level mapping, validation, and rollback between Propertybase and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Propertybase
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Propertybase and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Propertybase is a Salesforce-built CRM for real estate brokerages that carries Salesforce's full object model — record types, custom objects with pba__ API prefixes, Company Contacts versus Individual Contacts, and Listings as a custom Salesforce object. Migrating to Nutshell collapses that model into a simpler structure: People (for both contacts), Companies, Deals, Leads, and a custom object for Listings. We begin by auditing every active Propertybase object — Companies, Company Contacts, Individual Contacts, Listings, Offers/Contracts, Enquiries, custom pba__ fields, and activities — and exporting them in dependency order via Propertybase's Data Export tool or Salesforce API. We then transform Individual Contacts into Nutshell People records with a custom flag preserving their original contact type, map Listings to a Nutshell custom object with all listing-specific fields recreated, and map Offers to Nutshell Deals with status preserved as a custom field. Custom pba__ fields on any object become Nutshell custom fields on the equivalent target object. Our migration runs as a sequenced, dependency-aware load: Companies first (since People require a CompanyId), then People split by contact type, then Leads from Enquiries, then Deals from Offers, then Activities. A 24–48 hour delta-pickup window captures in-flight changes during cutover. Workflows, Process Builder rules, and automations are not migrated — Propertybase runs on Salesforce Flow and these must be rebuilt in Nutshell's automation system, for which we provide an exported reference document.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Propertybase object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Propertybase
Company Contact
Nutshell
Person
1:1Propertybase Company Contacts map directly to Nutshell People records. The ContactType field set to 'Company Contact' distinguishes them from Individual Contacts after migration. The primary Company lookup in Propertybase becomes a CompanyId link to the mapped Nutshell Company record. All standard fields (name, email, phone, title, address) migrate as direct field mappings.
Propertybase
Individual Contact
Nutshell
Person
1:1Propertybase Individual Contacts use ghost Company records in Salesforce to satisfy the Contact-Account requirement. We migrate Individual Contacts as Nutshell People with a custom 'PB_Contact_Type__c' flag set to 'Individual', preserving the distinction without the ghost Company overhead. The ghost Company itself is not migrated — only the Person record with the flag.
Propertybase
Company
Nutshell
Company
1:1Propertybase Companies map 1:1 to Nutshell Companies. The Name, Website (from domain), Industry, NumberOfEmployees, and AnnualRevenue fields migrate directly. Parent-company hierarchies (where a Builder or Agency has a parent) map to Nutshell's parent Company lookup. Multi-address companies require address field consolidation into Nutshell's address block.
Propertybase
pba__Listing__c (Sale Listing)
Nutshell
Listing (custom object)
1:1Propertybase Sale Listings map to a Nutshell custom object called 'Listing' (type: Sale). We create the custom object and all listing-specific fields in Nutshell before the migration run. The listing's assigned agent links to the mapped Person record; the associated Company (agency or broker) links to the mapped Company record. Status values (Active, Pending, Sold) map value-by-value.
Propertybase
pba__Listing__c (Rent Listing)
Nutshell
Listing (custom object)
1:1Rent Listings use the same Nutshell Listing custom object with Listing_Type__c set to 'Rent'. Monthly rent, lease term, and availability date fields migrate as custom Number and Date fields on the custom object. Rent listings that are also linked to an Offer/Contract use the same Offer→Deal mapping as sale listings.
Propertybase
pba__Offer__c
Nutshell
Deal
1:1Propertybase Offers (Sale/Rent contracts and offers) map to Nutshell Deals. The Offer Name becomes the Deal name, Amount and Close Date migrate directly. Offer Status (Pending, Accepted, Counteroffered, etc.) is preserved as a custom pick-list field 'PB_Offer_Status__c' since Nutshell's native Deal Stage is used for pipeline progression. The Listing lookup becomes a custom lookup to the Nutshell Listing custom object.
Propertybase
pba__Inquiry__c
Nutshell
Lead
1:1Propertybase Enquiries and Requests (inbound property inquiries) map to Nutshell Leads. The Enquiry Name, Description, Lead Source, and Priority fields migrate as direct or custom-field mappings. If an Enquiry is linked to a Listing, the listing relationship is preserved via a custom text field holding the source Listing name for manual re-linking in Nutshell.
Propertybase
Activity (Call, Email, Meeting, Note)
Nutshell
Task / Event / Note
1:1Propertybase activities — calls and emails stored as Tasks, meetings as Events, and notes as Notes — migrate directly to the equivalent Nutshell objects. Original timestamps, owners (resolved by email match), and parent-record links (Contact, Company, or Listing) are preserved. Attachments on notes are downloaded and re-uploaded as Nutshell file attachments.
Propertybase
pba__CustomField__c (any object)
Nutshell
Custom Field
1:1All custom pba__ fields on any Propertybase object become Nutshell custom fields on the equivalent target object. Before migration, we audit every active custom field, recreate each in Nutshell (matching field type: text, number, date, pick-list, etc.), and then map the data. Custom fields that have no Nutshell equivalent (e.g., some Propertybase-specific pick-lists) are created as custom pick-list fields with the same values.
Propertybase
pba__AreaAttachment__c
Nutshell
Custom Field / File Attachment
1:1Propertybase Area attachments and media files associated with listings (floor plans, area maps) are exported from Propertybase Media, downloaded, and re-uploaded as Nutshell file attachments on the corresponding Listing record. File size limits in Nutshell are checked before upload — large files are compressed or linked by URL reference.
| Propertybase | Nutshell | Compatibility | |
|---|---|---|---|
| Company Contact | Person1:1 | Fully supported | |
| Individual Contact | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| pba__Listing__c (Sale Listing) | Listing (custom object)1:1 | Fully supported | |
| pba__Listing__c (Rent Listing) | Listing (custom object)1:1 | Fully supported | |
| pba__Offer__c | Deal1:1 | Fully supported | |
| pba__Inquiry__c | Lead1:1 | Fully supported | |
| Activity (Call, Email, Meeting, Note) | Task / Event / Note1:1 | Fully supported | |
| pba__CustomField__c (any object) | Custom Field1:1 | Fully supported | |
| pba__AreaAttachment__c | Custom Field / File Attachment1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Propertybase gotchas
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
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Audit Propertybase objects and export in dependency order
We audit every active Propertybase object — Companies, Company Contacts, Individual Contacts, Listings (pba__Listing__c), Offers (pba__Offer__c), Enquiries (pba__Inquiry__c), custom fields on each object, and all activity records — using Propertybase's Data Export tool (Setup / Data Management / Export Data) and Salesforce API queries. We identify record-type usage, custom field API names (pba__ prefix), active workflows, and any formula or roll-up summary fields that will be excluded. The export is sequenced in dependency order so that parent records exist before child records load into Nutshell.
Set up Nutshell custom objects and fields before migration
Before any data loads, we create the Nutshell custom object for Listings and all custom fields required by the mapping plan — on Person, Company, Lead, Deal, and the new Listing custom object. We configure the custom lookup from Deals to the Listing custom object, set up pick-list values matching Propertybase's status and type fields, and verify field types (number, date, text) align with the source data. This setup step is completed and validated before the migration engine runs.
Resolve owners and users by email match
Propertybase owner IDs are resolved against Nutshell users by email address. Any Propertybase owner whose email does not match an active Nutshell user is flagged before migration — your team either invites them to Nutshell first or assigns their records to a designated fallback user. No record lands in Nutshell without a valid Assigned To value. Ghost Companies are identified and filtered during this step to prevent phantom company records from being created.
Run a sample migration with field-level diff
A representative sample — typically 200–500 records covering each object type including a mix of Individual Contacts, Company Contacts, active Listings, Offers, and a few activities — migrates first. We generate a field-level diff comparing source values against the Nutshell records, verifying that contact type flags, listing status values, offer-to-listing lookups, and owner assignments all resolve correctly. You review the sample before we commit to the full run. Any mapping corrections are applied to the migration engine before the next step.
Execute full migration with delta-pickup window
The full migration runs in dependency order: Companies first, then People (both contact types in parallel), then Leads, then Deals, then Activities. A delta-pickup window of 24–48 hours after the initial load captures any records created or modified in Propertybase during the cutover period while your team continues working. Audit logs record every operation. If reconciliation identifies missing or mismatched records, one-click rollback is available to restore Nutshell to its pre-migration state while the issue is investigated and corrected.
Platform deep dives
Propertybase
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Propertybase and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Propertybase: Salesforce API limits apply — not publicly documented per Propertybase tier.
Data volume sensitivity
Propertybase exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Propertybase to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Propertybase to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Propertybase
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.