Migrate from Property Shell to Freshsales

Property Shell leads map directly to Freshsales leads. Any property-specific fields on leads (e.g., preferred development, budget range) migrate as Freshsales custom fields. Owner resolution runs by email match against Freshsales users. Leads without an email route to Freshsales with a null email address and a custom source field for manual review.

Direct map. Property Shell contacts migrate to Freshsales contacts preserving first name, last name, email, phone, mobile, job title, address, and lifecycle stage. Contact ownership resolves by email match to Freshsales users. The primary company association becomes the AccountId; secondary associations surface as Account Contact Relationships in Freshsales.

Direct map with structural nuance. Property Shell allows N:N contact-to-company relationships. Freshsales accounts have a one-to-many relationship with contacts. We migrate the primary company per contact as AccountId and surface secondary company associations as Account Contact Relationships or a custom multi-company field — your team chooses the preferred approach before migration runs.

Direct map for deal name, amount, stage, close date, owner, and notes. Property Shell deal properties like stage name, release, lot number, and development project become Freshsales custom fields on the deal. Deals link to the primary AccountId and to associated contacts via Freshsales Contact Roles. The pipeline-to-pipeline mapping runs before deals to ensure stage pick-lists are active in Freshsales.

Property Shell deal pipelines map 1:1 to Freshsales deal pipelines. Each pipeline is created in Freshsales before migration so stage pick-list values are live and ready for deal records to reference. If Property Shell pipelines have custom stage names, those names are preserved verbatim as Freshsales stage values during migration.

Freshsales has no native property object. We migrate Property Shell development and property records as a Freshsales custom object (on Enterprise plans) or as a set of custom fields on the deal record. The mapping plan determines which approach fits your data structure — custom object preserves the lot/release hierarchy better, while custom fields are faster to implement.

Property Shell automations do not migrate. They must be rebuilt in Freshsales using the Automation tool. FlitStack exports your Property Shell workflow definitions as a structured rebuild reference document so your Freshsales admin can recreate each automation step-by-step. This is a manual step that adds to your internal project timeline but is handled entirely by your team.

Property Shell calls and emails map to Freshsales Sales Activities with Type = Call or Email and original timestamps preserved. Meetings map to Freshsales Appointments with start/end times and owners preserved. Notes migrate as Freshsales Notes with body text and timestamps. Attachments re-upload to Freshsales Files with parent-record links intact.

Property Shell contracts and attached documents migrate as Freshsales files linked to the relevant account or deal record. File metadata (original filename, upload date, file type) is preserved. If Property Shell stores contract fields as structured data rather than just files, those fields map to Freshsales custom fields on the account or a custom Contract object.

Property Shell custom properties and custom objects map to Freshsales custom fields on the matching standard object or to Freshsales custom objects (Enterprise plan). Nested pick-list values require value-by-value mapping if the destination field type is a dropdown. Multi-select values in Property Shell map to Freshsales multi-select custom fields with each selected value preserved.