CRM migration

Migrate from Propertybase to Nutshell

Field-level mapping, validation, and rollback between Propertybase and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Propertybase logo

Propertybase

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Propertybase and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Propertybase logo

Propertybase

What's pushing teams away

  • 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.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Propertybase objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Propertybase 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

maps to

Nutshell

Person

1:1
Fully supported

Propertybase 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

maps to

Nutshell

Company

1:1
Fully supported

Propertybase 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)

maps to

Nutshell

Listing (custom object)

1:1
Fully supported

Propertybase 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)

maps to

Nutshell

Listing (custom object)

1:1
Fully supported

Rent 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

maps to

Nutshell

Deal

1:1
Fully supported

Propertybase 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

maps to

Nutshell

Lead

1:1
Fully supported

Propertybase 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)

maps to

Nutshell

Task / Event / Note

1:1
Fully supported

Propertybase 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)

maps to

Nutshell

Custom Field

1:1
Fully supported

All 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

maps to

Nutshell

Custom Field / File Attachment

1:1
Fully supported

Propertybase 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.

Gotchas + challenges

What specifically takes care here

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 logo

Propertybase gotchas

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Individual Contact ghost Company creates duplicate noise in Nutshell

    Propertybase Individual Contacts are stored with a Salesforce ghost Company record to satisfy the Contact-Account lookup requirement — the ghost Company is not a real business entity. Migrating the ghost Company alongside Individual Contacts creates duplicate placeholder records in Nutshell that represent no real company. We filter ghost Companies during migration (identified by the SystemIsIndividual flag) and only migrate the Person record, marking it with a custom 'PB_Is_Individual__c' flag so your team retains the distinction without phantom company records cluttering Nutshell's database.

  • pba__ Listing custom object requires Nutshell custom object setup before data lands

    Propertybase Listings are stored as a Salesforce custom object (pba__Listing__c) with 15–30 custom fields per listing type. Nutshell has no native real estate listing object — every listing field (price, bedrooms, type, status, agent assignment, address) must first be created as a custom field on a new Nutshell custom object. If this setup is not completed before the migration run, those fields cannot receive data and listing records land with empty values. We deliver a Nutshell custom object setup plan as part of the migration package, and create all fields before any data is loaded.

  • Propertybase workflows, Process Builder, and Flow do not migrate to Nutshell

    Propertybase runs on Salesforce's automation stack — Workflow Rules, Process Builder, and Flow. Nutshell has its own automation rules and email sequences with a completely different trigger model. Nothing migrates automatically. Teams that rely on Propertybase workflows to assign listings, trigger status changes, or send notifications must rebuild these manually in Nutshell. We export your Propertybase workflow definitions as a structured reference document before the migration so your Nutshell admin can use them as a rebuild checklist. This is disclosed upfront — automation migration is out of scope for the data migration engagement.

  • Media files and attachments require re-upload after migration

    Propertybase stores listing images, floor plans, and area maps either as Salesforce Files attached to the listing record or as Media Loader assets. Nutshell attachments work differently — files are uploaded directly to Nutshell's file storage. Large media files (property photography packages can exceed 50MB) may need compression before upload to comply with Nutshell's file size limits. We download all Propertybase media, validate file sizes, compress where necessary, and re-upload to the corresponding Nutshell Listing record. If a file exceeds Nutshell's limit, we store the original URL reference as a custom field.

  • Offer-to-listing lookup requires post-migration re-link

    Propertybase Offer records carry a pba__Listing__c lookup that points to the associated listing. Nutshell Deals do not have a native listing lookup — this relationship must be modeled as a custom lookup field on the custom Listing object pointing to Deals, or as a text field holding the Offer's source Propertybase ID. After migration, we run a reconciliation step that re-links each Nutshell Deal to its corresponding Listing custom object record using the preserved Source_System_ID__c values, ensuring the offer-listing relationship is intact in Nutshell.

Migration approach

Six steps for a successful Propertybase to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Propertybase logo

Propertybase

Source

Strengths

  • Salesforce-backed infrastructure provides enterprise-grade security, scalability, and a familiar interface for teams with Salesforce experience.
  • Comprehensive real estate feature set covering the full sales cycle from lead capture through transaction close without requiring multiple disconnected tools.
  • Native listing management with media handling allows teams to store and display property images, video links, and PDFs within a single system.
  • Per-unit pricing model scales with brokerage size, making entry affordable for small teams before requiring enterprise-level investment.

Weaknesses

  • Recurring billing disputes and perceived billing practices drive negative reviews that signal customer satisfaction risk during and after migration.
  • Basic onboarding experience forces teams to invest significant time configuring the platform before it delivers real value.
  • Formula and roll-up summary fields cannot be exported, requiring migration teams to reconstruct calculated values from underlying source data.
  • Enterprise pricing at $89/user/month makes the platform expensive for large teams compared to flat-rate real estate CRM alternatives.
  • Workflow rules and automation are not data-exportable and must be manually rebuilt on the destination platform, adding migration complexity.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Propertybase and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Propertybase: Salesforce API limits apply — not publicly documented per Propertybase tier.

  • Data volume sensitivity

    A

    Propertybase exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Propertybase to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Propertybase to Nutshell data migrations

Answers to the questions buyers ask most during Propertybase to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Propertybase to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Propertybase-to-Nutshell migrations complete in 48–72 hours of clock time for datasets under 10,000 records. Setups with custom pba__ listing objects, multiple record types on Listings or Offers, or 20+ custom fields per object extend the timeline to 5–10 days. The longest planning step is setting up the Nutshell custom object for Listings and recreating all listing-specific fields before the migration engine can run. Discovery and audit typically add 3–5 business days before migration begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Propertybase.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day