Migrate from Propertybase to HubSpot

Propertybase Company maps directly to HubSpot Company. Standard fields including company name, domain, industry, employee count, and annual revenue transfer as HubSpot properties without transformation. Parent-child company hierarchies in Propertybase map to HubSpot's parent company association, preserving the organizational structure across platforms. Address fields from Propertybase billing address map to HubSpot's company address properties.

Propertybase Company Contacts map to HubSpot Contacts with the company association pre-linked at import time. Standard fields including name, email, phone, and title transfer directly to HubSpot Contact properties. The Systemisindividual flag used in Propertybase to distinguish individual contacts from company contacts is dropped in HubSpot since HubSpot Contact objects are unified and do not require this distinction. Contact records land with their associated company already linked.

Propertybase Individual Contacts map to HubSpot Contacts without a primary company association. The 'ghost' Account that Propertybase creates behind the scenes for Salesforce compliance is not replicated in HubSpot — the Contact lands cleanly without a company link unless you specify one.

Propertybase Enquiries and Requests map to HubSpot Tickets as the closest equivalent for inbound inquiry tracking. Enquiry source, status, and description transfer as Ticket properties. If your team used Enquiries primarily as lead records rather than support tickets, HubSpot Deals or a custom object may be a better destination — FlitStack surfaces this choice before migration.

Propertybase Listings have no direct HubSpot equivalent. FlitStack creates a HubSpot Custom Object named 'Listing' with properties for address, price, listing status, square footage, MLS ID, zoning, and bedrooms/bathrooms. Alternatively, Listings can map to HubSpot Deals if your team prefers to track listings within the sales pipeline — this choice is made during planning.

Propertybase Offers and Contracts map to HubSpot Deals. Offer amount, status, contingencies, and close date transfer as Deal properties. The offer is associated with the Listing (via Custom Object association or Deal association) and the purchasing Contact. Offer status (pending, accepted, rejected) maps to Deal stage.

Propertybase Listing Agent and Owner fields store a user reference. FlitStack resolves these by email match to HubSpot users. Unmatched owners are flagged before migration so you can either invite them to HubSpot or reassign records to a fallback owner.

Propertybase activity history including calls, emails, meetings, and notes attached to contacts or listings migrates to HubSpot's engagement timeline. Original timestamps, owners, and body content are preserved exactly as they appear in Propertybase. Notes with rich-text formatting are re-imported as HubSpot engagement notes with formatting intact, and each engagement links to its associated contact or listing record.

Any Propertybase custom objects beyond the standard set of Listing, Offer, and Enquiry map 1:1 to HubSpot Custom Objects. FlitStack creates the destination custom object schema in HubSpot before importing records, mapping each custom field to the equivalent HubSpot property type including picklists, dates, numbers, and text. This ensures complex entities such as Buildings or Projects transfer completely with all attributes intact.

Propertybase file attachments (listing photos, contract PDFs) stored via Media Loader are downloaded and re-uploaded to HubSpot Files, then re-associated with the corresponding Listing or Offer record. HubSpot's 25MB per-file limit applies — larger files are flagged for manual handling.

Propertybase Workflow Rules and Process Builder automations do not migrate. FlitStack exports your workflow definitions as a structured rebuild reference (trigger, criteria, actions) that your HubSpot admin can use to recreate equivalent automations in HubSpot's workflow builder.

Propertybase reports and Salesforce dashboards do not transfer due to platform differences in reporting architecture. The underlying data including contacts, companies, deals, and listings migrates completely, but report configurations must be rebuilt in HubSpot's report builder. FlitStack validates that all source data is present and correctly associated in HubSpot before you begin rebuilding reports, giving you confidence in your data foundation when you start recreating your analytics suite.