Migrate from Propertybase to Freshsales

Propertybase Company maps directly to Freshsales Account. Company name becomes Account Name. Parent/child company hierarchy maps via Freshsales Parent Account field if enabled. Ghost accounts created solely for Individual Contacts are excluded from this mapping — only real Propertybase Companies become Freshsales Accounts.

Propertybase Company Contact (SystemIsIndividual=FALSE) maps to Freshsales Contact with AccountId set to the corresponding Freshsales Account derived from the Propertybase Company. All standard contact fields (name, email, phone, title, address) transfer directly. Owner resolved by email match to Freshsales users. Unmatched owners flagged before insertion.

Propertybase Individual Contact (SystemIsIndividual=TRUE) uses a ghost Account in Salesforce — a system placeholder with no real business data. During migration, we identify the real company affiliation from source data or flag for manual assignment. Individual Contacts land in Freshsales as Contacts without a mandatory AccountId link, preserving all original fields and timestamps.

Propertybase Enquiries/Requests split by status: new or open enquiries route to Freshsales Lead; qualified or converted enquiries route to Freshsales Deal. The split logic follows your specified rule — typically based on the Enquiry status field or a Stage pick-list if configured. Each Enquiry is assigned to the corresponding contact and account after ghost-account resolution.

Propertybase Individual Listings (standalone properties not linked to a Master Project) migrate as a Freshsales custom module named Listing__c. Fields including address, price, bedrooms, bathrooms, property type, status, and MLS number map to custom fields on the Listing__c module. The module is created by your Freshsales admin (or our team) before migration using the schema plan we deliver.

Propertybase Listings linked to a Master Project/Building/Stage require three Freshsales custom modules: Master_Project__c, Building__c, and Stage__c, with lookup fields linking Stage to Building and Building to Master_Project. Each listing record receives a lookup to its parent Stage. This preserves the full three-level hierarchy — no flattening of the listing structure.

Propertybase Offers/Contracts map directly to Freshsales Deals. Offer amount becomes Deal amount, close date maps to Close Date, and offer stage (Active, Won, Lost, Withdrawn) maps to Freshsales Deal stage values via value mapping. The Propertybase Listing lookup is preserved as a custom Source_Listing__c lookup field on the Freshsales Deal — this field must be created in Freshsales before migration runs.

Propertybase owner IDs resolve by email match against Freshsales users. Unmatched owners are flagged before migration — your team either provisions Freshsales user accounts or assigns records to a fallback owner specified in the migration plan. No record lands in Freshsales without an owner assignment confirmed.

Propertybase file attachments on contacts, companies, listings, and offers are downloaded and re-uploaded to Freshsales Files. Freshsales file size limits apply (default 25MB per file). Inline images in notes are extracted and rehosted. Original file names and attachment dates are preserved as metadata on each Freshsales File record.

Propertybase logged calls and emails map to Freshsales Tasks with Type field set to Call or Email. Meetings map to Freshsales Appointments with original start time, end time, and related contact preserved. Original timestamps and activity owners transfer as custom fields if Freshsales does not expose them natively on the Task or Appointment object.

Propertybase notes map to Freshsales Notes attached to the corresponding record. Rich-text formatting is preserved where the target field supports it. If Propertybase notes contain inline images, these are downloaded and re-uploaded as Freshsales file attachments linked to the same parent record.

Propertybase workflows built in Salesforce Workflow Rules or Process Builder do not migrate to Freshsales. We export the workflow definitions (trigger object, criteria, actions, time-based triggers) as a structured reference document. Your Freshsales admin rebuilds them in Freshsales's workflow builder using this reference. Budget 1–3 days per complex Process Builder flow for the rebuild effort.

Propertybase validation rules enforced at the Salesforce level cannot transfer to Freshsales. We provide a list of active validation rules with their conditions and error messages for your Freshsales admin to recreate in Freshsales Field Settings. Required field validation and pick-list dependency rules are the most common rebuild targets.